Error in checkSession not handled

Occasionally we get a 400 error from the call to <our-app> during checkSession. This can be due to a temporary bad state on the client (eg. when changing which auth0 tenant we are using), or some other issue which is not that important and is cleared by logging in/out.

However, when this 400 response is returned, the callback to checkSession is not fired. It seems there is some code missing to handle this kind of error and I’m not sure how we can detect it; since it’s an async operation we can’t simply try/catch the checkSession call.

As it has been more than a few months since this topic was opened, and there has been no reply or further information provided as to the existence of the issue, we are closing this topic. Please don’t hesitate to create a new topic if this issue is still present, we would be happy to work with you to help find a resolution.