-
Notifications
You must be signed in to change notification settings - Fork 371
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]: In v5, the Subscription Status does not change to 'Subscribed'. #1947
Comments
@kishibata Thank you for reaching out I have not been able to reproduce this. If possible could you share verbose logs when permission is granted so that we can try to debug this behavior? |
@emawby https://docs.google.com/document/d/11Z1-UFyvUOGAmuZhiXKFPDdsFSc7TJKahRRue3-C9Q8/edit?usp=sharing |
@emawby |
Hello @kishibata thank you for the reminder. We believe we know the root cause of the issue and are working on a fix, but unfortunately it has not been resolved yet. To confirm our investigations have you noticed this happening if you don't call "Login" for the device? You may need to logout/reinstall to remove the cached user. |
@emawby |
Hi everyone. I am using v5 and had the very same issue as @kishibata. As soon as the prompt button is clicked, the Android notification prompt is visualized, but the Subscription status remains as "not granted". |
Hi everyone. I am using v5 and had the very same issue as @kishibata @gabriserra . the subscription remains as not granted |
Hello @emawby |
Same here. I thought maybe 6 months after version 5.x release I can finally migrate, but nope. Back to version 4.x. |
Experiencing the same issue after migration using version 5.1.7. We ask for the notification permission without using the OneSignal SDK (i.e. without calling Calling This happens after deleting data & cache or with a fresh install. |
Unfortunately this did not work for me. :'( |
This is what i did to work it for me. |
|
Same issue here :( |
@jkasten2 FWIW, this is still happening on 5.1.8. However, force closing and launching the app again seems to do the trick. Unfortunately I'm unsure whether this is a new behavior or existed prior to 5.1.8. So what I'm seeing on my end is:
|
@sebastinto Thanks for the details, I have some follow up questions to narrow down the issue further.
Are you prompting with OneSignal? If you are not, then your issue is most likely due to #1854.
If you don't call login do you still see the same issue? Another thing to try is keep calling login(), but wait 30 or seconds then prompt and accept the prompt.
Lastly, can you share a logcat with OneSignal VERBOSE logging of reproducing the issue? |
We are not so you're right it's likely related to #1854.
Yes.
Is there a non public way I can share this with you? Email maybe? |
If your issue was #1854 then you can omit sending us the log, as that is a know issue. If you are still seeing this problem afterwards then you can send the logcat to support@onesignal.com, and sharing with them a link to this thread. |
@jkasten2 i just came across the same problem. Removing the login seems to solve it, but oc is not really a solution. Any fix for this planned already? Edit: I request the permission via OneSignal |
Here are some logs, hope this helps. I removed my package name and replaced the appId with See logs
User logs in into the app, i call the sdk's login method. After that i request the permission. As mentioned above the removal of login works. I use the latest cordova version. Same works on ios. Let me know if you need additional information. |
We also were facing this issue on Android 13, after updating to the latest OneSignal Flutter SDK v5.2.0 from a pre-5.X.X version. iOS was working fine. The native permission prompt was being triggered by Following other threads, we noticed that the status would change and the notifications would be delivered if we did the following:
After the second open, notifications were being delivered. Still, this was not acceptable for production. The workaround seemed to be requesting permissions directly with |
This issue the same as this #2106 (comment) There was a backend issue that was released today to address this. To any avoid possibilities of a client side event being skipped (mostly prompting for notification permission outside of the OneSignal SDK) I also recommend you use the OneSignal-Android-SDK 5.1.15 or newer. |
Thank you @jkasten2 for the update ✌🏼 Thank you 😊 |
What happened?
In v5, even if permission is granted on the OS notification permission dialog, the Subscription Status does not change to 'Subscribed.'
Steps to reproduce?
What did you expect to happen?
At the moment when permission is granted on the OS notification permission dialog, the Subscription Status changes to 'Subscribed.'
OneSignal Android SDK version
5.0.5
Android version
13
Specific Android models
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: