-
Notifications
You must be signed in to change notification settings - Fork 26
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]: migration issue from v2 to v3 #125
Comments
Also having the same issue |
@sshanzel I see your site is using HTTP instead of HTTPS. The major version of OneSignal SDK has dropped support for HTTP sites and your site must start with
@oreoluwa-bs let us know if they is also the same issue for you. We will provide a better SDK error message to improve the DX (developer experience) here. |
This does not work anymore with v3 using HTTP (for local development).
Unfortunately, our app running locally for dev environment is hosted with a different local named domain. This means the option to uncheck "Treat HTTP localhost as HTTPS for testing" is not shown. This option should be available whether it is under localhost or not so long as it is for local development/testing. |
We've migrated to v3, and it is easier to manage the subscriptions and everything so thanks for that. Just on Safari now, we are getting the error below:
We are not in a private session, and the config stayed the same since v2. Does it ring a bell? |
found any solution for that? |
What happened?
As recommended, we are migrating our existing implementation of v2 to v3.
I am receiving an error during initialization. Nothing was changed from my config so I am wondering why I'm getting this error.
I have also cleared the cache and deleted the service worker to start things clean.
Initialization config:
What browsers are you seeing the problem on?
Chrome (Chromium)
What operating system are you running?
macOS Ventura 13.1
Steps to reproduce?
What did you expect to happen?
Work as how it did before. Initialize as it used to be on v2.
Relevant log output
The text was updated successfully, but these errors were encountered: