-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
signInWithBrowser() do not open browser on Android #427
Comments
Experiencing the same |
Any updates here on this? |
Hi @DanSytnikov and @Justicea83, appAuthRedirectScheme is not necessarily the application ID. It should be similar to the redirectUri that you're passing into createConfig. For example, if your redirectUri is com.example.redirect:/something, the appAuthRedirectScheme should be com.example.redirect in this case. Let me know if that helps |
Solution which works for me : In Android folder built and build.gradle from app folder :
Then in createConfig use Important point : Be careful with useEffects, which can also hinder the opening of the Okta page. |
UPDATE : Sometimes in Android, redirection does not work and after deleting app data then it works. Maybe it's related to requireHardwareBackedKeyStore but i dont know. In Android Emulator it works always. |
Describe the bug?
When the signInWithBrowser() method is called using Android nothing happens, however, it works well on iOS.
I try the following code:
Nor "then()" neither "catch()" methods are called in this case. There are no errors or warnings.
According to the docs, I added this line to the
android/build.gradle
file:and these properties to the android/app/build.gradle file:
Also, I tried setting the "requireHardwareBackedKeyStore" option in createConfig() to "true" and "false" but neither case works.
I tried using devices with Android 11 and Android 14
What is expected to happen?
A browser window should open for okta-login.
What is the actual behavior?
Nothing's happening. No errors, no expected behavior.
SDK Version
51
The text was updated successfully, but these errors were encountered: