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
We're facing some problems when phone's default browser is set to any variation of Firefox.
Auth works flawlessly with every other available browser (even with Tor!), but with Firefox, on redirect, browser closes correctly but our application doesn't receive the token and it's treated like a canceled log in attempt.
It seems like Firefox and our application don't communicate or that the auth procedure isn't able to catch data Firefox sends back after redirect.
This only occurs when launchMode from AndroidManifest is set to 'singleTop'.
With 'singleTask', Firefox works, but having 'singleTop' for launchMode is important to us because one of the requirements for the app is to be able to continue the sign in process where you left of by clicking the icon on home screen (if the app hasn't been swiped from recent apps), and with 'singleTask' clicking the icon closes the browser.
Any idea on how we can approach this? Is this a known error that will be fixed in the future?
Thanks in advance!
Environment
Your Identity Provider: Azure
Platform that you're experiencing the issue on: Android
Your react-native Version: 0.74.2
Your react-native-app-auth Version: 8.0.1
Using Expo: No
The text was updated successfully, but these errors were encountered:
Issue
Hey there!
We're facing some problems when phone's default browser is set to any variation of Firefox.
Auth works flawlessly with every other available browser (even with Tor!), but with Firefox, on redirect, browser closes correctly but our application doesn't receive the token and it's treated like a canceled log in attempt.
It seems like Firefox and our application don't communicate or that the auth procedure isn't able to catch data Firefox sends back after redirect.
This only occurs when launchMode from AndroidManifest is set to 'singleTop'.
With 'singleTask', Firefox works, but having 'singleTop' for launchMode is important to us because one of the requirements for the app is to be able to continue the sign in process where you left of by clicking the icon on home screen (if the app hasn't been swiped from recent apps), and with 'singleTask' clicking the icon closes the browser.
Any idea on how we can approach this? Is this a known error that will be fixed in the future?
Thanks in advance!
Environment
Azure
Android
react-native
Version:0.74.2
react-native-app-auth
Version:8.0.1
No
The text was updated successfully, but these errors were encountered: