-
Notifications
You must be signed in to change notification settings - Fork 198
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]: Android device not registered on initialization (Android v12 and older) #931
Comments
@swebSi thanks for reaching out! Are you prompting your users at all? In your initialization code, we suggest either including our If you are still having issues, can you please send over your device logs so we can take a closer look? Thanks! |
Hi @jennantilla, yes, of course I am prompting the users after Onesignal. initialize. Also, we are testing on devices without Android 13 which have automatically subscribed notifications. Same codebase on iOS works as expected. Added verbose log with a clean angular project. |
Hi @jennantilla , update: Only physical device with angular < 13 have this issues. Emulator is correctly registered. We tested on devices with android 8, 10 & 12. |
On devices with android 12 or older, its was required to call OneSignal.User.setLanguage(); [DefaultDispatcher-worker-6] HttpClient: POST RECEIVED JSON: {"errors":[{"title":"The provided language value is not a supported ISO 639-1 value"}]} |
What happened?
We are using Angular + Capacitor v5 with OneSignal 5.0.2.
After calling OneSignal.initialize - Android devices are not visible under subscriptions.
With the same codebase iOS devices are correctly registered.
Reverting the library to v3.3.1 works as expected.
Steps to reproduce?
What did you expect to happen?
I expect to see my client registered in order to send push notifications.
OneSignal Cordova SDK version
5.0.2
Which platform(s) are affected?
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: