Open EinfachHans opened 6 months ago
Hello @EinfachHans thanks for reaching out! Yes, if you could please provide reproduction steps we'll dig into this deeper.
Appreciate it!
Hey @jennantilla,
created a repo for this issue: https://github.com/EinfachHans/onesignal-issue
Steps to reproduce:
onesignal.service.ts
: Add your correct app idionic capacitor build android
[OneSignal]: No token exists, adding listener...
will be printed, but the listener will never be resolved and o token is available frontend side. On the other hand there is a new subscription created in the dashboard. On most cases a restart does not solve the problem, only a re-install does.Let me know if this works for you to reproduce the problem 😊
This problem still occurs, is there any solution? @EinfachHans @jennantilla
What happened?
Hey there,
i have the following logic in my app on startup:
await OneSignal.User.pushSubscription.getIdAsync();
If the token is not existent ( i understand why this is possible - read here) i add a listener via
OneSignal.User.pushSubscription.addEventListener('change', listener);
This works well on ios, but on android it seems to never resolve when the previous subscription was deleted. In this case the listener never gets resolved. But i can see the new created subscription id on the onesignal dashboard. Even an app restart does not work. I have to delete and reinstall the app. Then a new id is created and the listener resolves.
Steps to reproduce?
What did you expect to happen?
Even after the subscription is deleted, the listener should resolve when the new id is existent.
OneSignal Cordova SDK version
5.1.3
Which platform(s) are affected?
Relevant log output
No response
Code of Conduct