Skip to content
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]: Initilization on Firefox doesn't work. #87

Open
sshanzel opened this issue Dec 27, 2022 · 5 comments
Open

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

sshanzel opened this issue Dec 27, 2022 · 5 comments

Comments

@sshanzel
Copy link

sshanzel commented Dec 27, 2022

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
Copy link
Author

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

@rgomezp
Copy link
Contributor

rgomezp commented Jan 3, 2023

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
Copy link
Author

sshanzel commented Jan 4, 2023

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
Copy link
Member

jkasten2 commented Aug 16, 2023

@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
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants