[Bug]: migration issue from v2 to v3

[sshanzel]

[Bug]: migration issue from v2 to v3

[oreoluwa-bs]

Also having the same issue

[jkasten2]

@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 https:// to use v3 of this react-onesignal SDK.

• In the OneSignal dashboard you must also uncheck "My site is not fully HTTPS".

@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.

[sshanzel]

In the OneSignal dashboard you must also uncheck "My site is not fully HTTPS".

This does not work anymore with v3 using HTTP (for local development).

@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 https:// to use v3 of this react-onesignal SDK.

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.

[sshanzel]

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:

Ct: The Safari site URL, icon size, or push certificate is invalid, or Safari is in a private session

We are not in a private session, and the config stayed the same since v2. Does it ring a bell?