-
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]: OSUtils.java:490 Could not invoke OneSignal.promptForPushNotificationsWithUserResponse #1449
Comments
@invyctus92 Thanks for reporting with the fullstack trace. Can you let us know what event you are calling What are the percentage of users are getting this crash? Are you able to reproduce the crash? If so, what is the step-by-step to reproduce it? |
same situation, see logs from Google crash details:
|
@jkasten2 Hi, |
Hello!
Dependencies:
|
It is only crashes in release mode. Should I tweak proguard rules or something? |
any update on this issue? |
Any update on this? Facing the same issue - only on the release build. @Dimous have you found a solution or we've been/gonna be fired? :))) |
Getting the same crash for my application too. And the app crashes only on Samsung devices. |
In the end, I fixed my issue by removing the code that was prompting programmatically the dialog to give notification permission, and I enabled that prompt using the in-app messages from OneSignal (the Push Permission Prompt one). |
@alex-yplabs Hi I have the same issue can you please provide a snippet example of your solution? |
Hey! It's not code per se. I just removed "OneSignal.promptForPushNotificationsWithUserResponse()" and I have used the In-App Message for notification prompt to actually prompt for push notifications (on the One Signal dashboard) |
Same issue here, with Android devices only |
same issue in my emulator. |
i solve this with PermissionsAndroid from RN core |
can you elaborate please? |
i dont use @alex-yplabs solution because In-App-Message is limited for free user.
|
Does anyone have an update on this ? We are experiencing the same issue with latest RN version (0.71.6) and target SDK set to 33. |
We are also having this issue. Target SDK is set to 33. |
in our case, there's no crash in the os logs, the permission dialog shows up but then the app gets stuck, it just hangs, buttons in the dialog do nothing |
Any solution? Android 13 "react-native": "0.72.4" android/build.gradle buildToolsVersion = "33.0.0" |
I am on Still happens for people with android version 13 and above.. Any solution? Will upgrading the react-native-onesignal to 5.0.3 help? |
Facing same issue on Android 13 for Samsung devices in release mode: package.json "react": "18.2.0", android/build.gradle buildToolsVersion = "33.0.0" |
Hi folks, Facing same issue on following versions: "react": "17.0.2", And I can't use PERMISSIONS.POST_NOTIFICATIONS because this POST_NOTIFICATION permission was not present react-native's versions below 0.70 Any suggestions in this case? |
update react native version to 0.70+ 🤣 and add: |
What happened?
I got this error report from my analytics bugsnag: here is the device info:
manufacturer
Google
model
Pixel 4a
osName
android
osVersion
13
runtimeVersions
{
"reactNativeJsEngine": "hermes",
"reactNative": "0.70.4",
"androidApiLevel": "33",
"osBuild": "TP1A.221005.002"
}
Steps to reproduce?
What did you expect to happen?
The popup should appear to ask for permissions for notifications
React Native OneSignal SDK version
4.4.1
Which platform(s) are affected?
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: