-
Notifications
You must be signed in to change notification settings - Fork 377
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
[Bug]: RNOneSignal.requestNotificationPermission Crash #1647
Comments
+1 |
Hi! We were having a similar problem, and our solution was to migrate the permissions request to react-native-permissions and initialize OneSignal once the user acepts them. I hope it helps! |
+1 |
Looks like we fixed this in RN SDK version 5.0.3 Please upgrade and if you still have issues, you can follow this guide to get a log and share it here or with [email protected] https://documentation.onesignal.com/docs/capturing-a-debug-log Thanks! |
Still have the error on RN SDK version 5.1.2 |
I faced a similar issue and was able to resolve it. The solution is to initialize the library first and then proceed to request access permissions. just change this :
To
|
What happened?
Hello,
On our project we are using OneSignal 5.0.2 and we are having many users (69% of users on Android 6 and 30% of users on Android 5, based on 2.3k~ users) are having crash on the function of title.
If needed I can try bringing more information, I'm available to help.
Steps to reproduce?
What did you expect to happen?
Should request permissions without causing an exception.
React Native OneSignal SDK version
Release 5.0.2
Which platform(s) are affected?
Relevant log output
The text was updated successfully, but these errors were encountered: