-
Notifications
You must be signed in to change notification settings - Fork 448
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
react-native-app-auth module getting crashed in Android #672
Comments
Here's the crash log from my app
|
Same issue: #600 |
This might be a different reason for crashing, but I was able to resolve my crash by adding in I don't know how to check android's native log so I am not sure if its the same error. But in my research to resolve my issue, I ended up here and issue #600 a couple times, so I hope this can help anyone suffering from the same error. |
This issue occurs on low-end Android devices that kill the Activity when your app is backgrounded during the authentication process. We persist values in private instance fields so we can read/use them during the code/token exchange in our
I've talked with the other maintainers and we are going to try to get around to a fix for this. I can't provide a timeline, but just a heads up that it's on our radar. There are a few issues in the repo where this is the root cause. |
Also investigating this issue presently. Can't help but notice that while Nirodha26#1 put in what may be a fix for this issue in January, the releases since then have not included this update. Edit: My mistake, I see that that is on a fork. Any chance of that getting merged into official? |
@Jay-A-McBee any chance this possible fix would resove the issue and can be merged here ? |
It would be great if this fix was merged into official and added in a next release. |
Hello @Jay-A-McBee |
Is there any update about this issue @Jay-A-McBee ? |
Are there any plans of including this change Nirodha26#1 in an official release to fix this issue? |
Will this issue be fixed soon or is the library not longer maintained? |
We are facing the same issue. Any updates? |
seeing similar errors in our App Center crash results: com.rnappauth.RNAppAuthModule.onActivityResult main thread:
From devices like:
We are using react-native-app-auth version 7.1.0, which is latest right now, but this has been happening for a while now. We are also seeing some iOS errors too, but can't see any relation to this for now. |
Same here, experiencing crashes on our production App. Mainly on HUAWEI P smart 2019, but others too, like Galaxy S21 5G and A52s 5G, Redmi Note 9 and 11 5G,... More than 3 years since this issue was filed and still no fix, is this library still maintained actively? |
Experiencing the same issue even on the latest devices like the Galaxy S24 Ultra, any help would be appreciated.
|
any update on this? This happens on multiple production device( samsung q4q,OnePlus OnePlusN200TMO,motorola berlna,motorola denver etc) Exception java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.Boolean.booleanValue()' on a null object reference |
Hi everyone, we don't currently have any resources able to take on this work, but are happy to accept PRs from the community. |
Thanks for all your work on this library, there are now a few PRs still open for a while. I have just submitted mine with the solution suggested by @yberstad which I can say it works on our end. |
@RubenPM-dev Thanks for the PR, we will review it as soon as possible. |
Issue
Firebase crashlytics report below crash issue in react-native app Android. There is no issues in iOS.
Caused by java.lang.NullPointerException
Attempt to invoke virtual method 'boolean java.lang.Boolean.booleanValue()' on a null object reference
com.rnappauth.RNAppAuthModule.onActivityResult (RNAppAuthModule.java:414)
Environment
Your Identity Provider:
e.g. IdentityServer 4 / Okta / Azure
Unable to identify because this is NPM module level crash
Platform that you're experiencing the issue on:
iOS / Android / both
Platform: Android
Are you using Expo?
No
Please provide suggestions to fix this issue.
The text was updated successfully, but these errors were encountered: