Open sshanzel opened 1 year ago
After checking on production, it seems to only happen on local development.
Thanks for reporting @sshanzel ,
I wonder if it has to do with this. Can you check?
Thanks for your patience. We will attempt to resolve soon.
I wonder if it has to do with this. Can you check?
Thank you for your response. Unfortunately, it is not related to strict mode as we have it configured to false
and we didn't use any form of wrapper relating to strict mode.
@sshanzel Can you try the 3.0.0 release to see if you still have this issue?
If you still have this issue can you do the following?:
OneSignal.Debug.setLogLevel("trace");
before attempt to subscribe and share the full log here.@jkasten2 seems like there is an issue with migrating from v2 to v3.
What happened?
Works perfectly on Chrome, but on Firefox, the app using the package is not working. It doesn't give any errors/warnings so it is a bit difficult to know where the issue could be coming from.
One thing I noticed though is that, in Chrome, the indexedDb is automatically created once initialized, but on Firefox, you won't see any relevant database.
Not sure though if this only happens in local development.
Steps to reproduce?
What did you expect to happen?
Should work smoothly like on Chrome. Should have been initialized as intended.
Relevant log output
When you execute
OneSignal.isPushNotificationsSupported();
- it returnsfalse
. Firefox v108.0.1 MacOS v12.5.1