You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once a user is sent to the WordPress login page, it's assumed that they will successfully login and authorise the app.
Currently if the user does not sign in, or does not authorise the app, there is no clear path for them to return to the appropriate page in the browser, or for an in-app browser to be closed and the failure handled.
Presently, there are a number of permutations, but most likely when they return a new authorisation request will be triggered with old credentials resulting in 401: Unauthorized.
The text was updated successfully, but these errors were encountered:
Once a user is sent to the WordPress login page, it's assumed that they will successfully login and authorise the app.
Currently if the user does not sign in, or does not authorise the app, there is no clear path for them to return to the appropriate page in the browser, or for an in-app browser to be closed and the failure handled.
Presently, there are a number of permutations, but most likely when they return a new authorisation request will be triggered with old credentials resulting in 401: Unauthorized.
The text was updated successfully, but these errors were encountered: