Ok, some context. We are using React Native and the hosted page within a web view. In order to make use a users Facebook session in their normal browser, we catch the window.open and make sure we open this URL in the native browser. The redirectURL is set to our custom scheme for the app, so we get back into the app after the whole OAuth flow.
This idea works fine. But the very first time we use a Facebook login on an Android device (it’s essential that you remove the app from ‘Logged in with Facebook’ in Settings → Apps in your Facebook account) the browser shows this page:
You may have pressed the back button refreshed during login, opened too many login dialogs, or there is some issue with cookies, since we couldn’t find your session. Try logging in again from the application and if the problem persists please contact the administrator.
TRACKING ID: ef07f642f18f400e453e
Apart from this everything is successful. The redirects are ok, the user is logged in and our app opens. However, this Oops! error page is what is left in the browser. You can already see this page when Android prompts to open our app using our custom scheme. So this might throw off users, thinking their login was unsuccessful. Every subsequent login works as it should.
It looks like there is something going wrong that you normally don’t see if you keep the request inside the webview.