-
Notifications
You must be signed in to change notification settings - Fork 453
NullPointerException in createConnectionBuilder (Android) #450
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
Comments
We're also experiencing a great amount of these exceptions:
It seems like the RNAppAuthModule state is lost when the result from login returns? In this case |
Hi - could you try upgrading to v5? It includes this PR which should prevent the native crashes. As for the other error - could you explain how you're using authentication in your app? Are you using |
Thanks. I will try to roll out with v.5.0.0 stable today. I am using this config:
Using authorize to log in (no prefetch):
|
Thanks for the clarification. Please let me know about if upgrading to v5 changes anything. I think the issue might occur when the app is backgrounded for a while, and not related to any particular IDP. That would explain why we don't see it on the emulator. I will try to recreate this with on a physical Android device. |
@kadikraman I am using v5 and see this crash on Crashlytics today.
|
@kadikraman We are using 5.0.2 and getting a lot of reports via Google Play Console:
Changing line 713 to
might help. |
Looks like this is fixed by 0b356a5, included in v5.1.2. Please close this issue :) |
We just release a new app based on React Native and react-native-app-auth and Azure AD as IDP.
react-native-app-auth: 5.0.0-rc3
react-native: 0.61.5
react: 16.9.0
We never saw this during testing with emulator and a Huawei P30(Android 9).
But now we have logged hundreds of these errors over the last couple of days, on a range of different phone models, and Android 8, 9 and 10. iOS seems fine.
Based on the exception, it seems like
dangerouslyAllowInsecureHttpRequests
. How could this be?This seems related to this issue: #95
The text was updated successfully, but these errors were encountered: