Releases: OneSignal/OneSignal-Website-SDK
Releases · OneSignal/OneSignal-Website-SDK
Release 150706
Compatibility fix for Akamai's ServiceWorker
- Added specific checks for
akam-sw.js
and using theirothersw
flag
Release 150705
Fixes Custom Link on Safari 12.1
- On Safari 12.1 and newer custom link prompts were not showing the native prompt.
- PR #524
Release 150704
Changing appId uses correct key & removed sw unregister
- When switching OneSignal appIds the push subscription now re-registers with the new push keys
- This prevents errors when sending pushes on the new appId when browsers automatically migrate over
- We now no longer call unregister when replacing another existing ServiceWorker.
- Both issues fixed in PR #521
Release 150703
Includes:
- fix for on_session not being sent for some subscribed users
- fix for icon not showing up in slidedown prompt in Samsung web browser
Release 150702
Includes:
- Update for the
isPushNotificationsSupported
to remove browsers that don't support VAPID - Fix for
autoRegister=true
config generation when using custom code setup. Now always shows native on https and slidedown on http.
Release 150701
Includes fix for notify button / bell blocking OneSignal initialization when hideWhenSubscribed
option is enabled.
Release 150700
On the way to making typical site setup more powerful and to deprecating ambiguous autoRegister
flag, we are introducing the following changes:
- Adding a new
autoResubscribe
flag- Solely responsible for automatically subscribing users who have current notification permissions in the allowed state and have not opted out but miss their subscription data.
- Can be set in the dashboard for all types of integrations. Can be overwritten in custom setup but is not required as part of init options.
- Adding a native browser prompt as a prompt option
- Supported on sites not using the subscription workaround
- Can be set to do auto-prompting with the new
autoPrompt
flag or called manually viaOneSignal.showNativePrompt
. - More info in our documentation -> https://documentation.onesignal.com/docs/native-browser-prompt
- Updated slidedown prompt
- Not also has
autoPrompt
property to configure whether it will be shown automatically or programmatically usingOneSignal.showSlidedownPrompt
- Native prompt takes priority over slidedown if both selected and both have auto prompting enabled.
- Not also has
- All changes are backwards compatible and will map correctly for the
autoRegister
flag unless new flags are explicitly present.
This release also includes:
- Updated error message text if no matching app id found (thanks @rafaelncarvalho for pointing it out)
- Refactored initialization logic to be more straightforward.
registerForPushNotifications
no longer subscribes opted out users, rolled back to the previous implementation for consistency.- Fixed ES5 console errors with OneSignal.push(())
Release 150600
Reduced SDK Size
OneSignalSDK.js
is now a small shim that checks if the browser supports push before loading the full SDk.OneSignalPageSDKES6.js
will be dynamically added to the page- This also means less bandwidth as OneSignalPageSDKES6.js is a smaller size
- Even less bandwidth for browsers that do no support push, such as iOS.
Release 150506
Includes:
- Added support for setting and removing external user id on a player record. Works similar to tags.