OneSignal / react-onesignal

React OneSignal Module: Make it easy to integrate OneSignal with your React App!
Other
74 stars 23 forks source link

[Bug]: Initilization on Firefox doesn't work. #87

Open sshanzel opened 1 year ago

sshanzel commented 1 year ago

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?

1. Install `react-onesignal`.
2. Run app initializing the SDK.
3. Test on Chrome (to verify it works, and it did - even sent messages from the dashboard).
4. Test on Firefox (doesn't work - not even registered on the Subscribed page in dashboard).

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 returns false. Firefox v108.0.1 MacOS v12.5.1

sshanzel commented 1 year ago

After checking on production, it seems to only happen on local development.

rgomezp commented 1 year ago

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.

sshanzel commented 1 year ago

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.

jkasten2 commented 10 months ago

@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?:

  1. Share a public URL reproducing the issue.
  2. Run OneSignal.Debug.setLogLevel("trace"); before attempt to subscribe and share the full log here.
sshanzel commented 8 months ago

@jkasten2 seems like there is an issue with migrating from v2 to v3.