Skip to content

Releases: OneSignal/OneSignal-Website-SDK

Release 150706

25 Sep 20:55
Compare
Choose a tag to compare

Compatibility fix for Akamai's ServiceWorker

  • Added specific checks for akam-sw.js and using their othersw flag

Release 150705

13 Jun 22:02
Compare
Choose a tag to compare

Fixes Custom Link on Safari 12.1

  • On Safari 12.1 and newer custom link prompts were not showing the native prompt.

Release 150704

30 May 00:02
Compare
Choose a tag to compare

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

21 Mar 18:51
6911da2
Compare
Choose a tag to compare

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

13 Mar 17:22
Compare
Choose a tag to compare

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

08 Mar 23:06
Compare
Choose a tag to compare

Includes fix for notify button / bell blocking OneSignal initialization when hideWhenSubscribed option is enabled.

Release 150700

08 Mar 00:27
Compare
Choose a tag to compare

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
  • Updated slidedown prompt
    • Not also has autoPrompt property to configure whether it will be shown automatically or programmatically using OneSignal.showSlidedownPrompt
    • Native prompt takes priority over slidedown if both selected and both have auto prompting enabled.
  • 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

06 Mar 01:07
Compare
Choose a tag to compare

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

28 Jan 22:58
7483858
Compare
Choose a tag to compare

Includes:

  • Added support for setting and removing external user id on a player record. Works similar to tags.

Release 150505

03 Dec 21:59
d20f6a6
Compare
Choose a tag to compare

Includes:

  • Fix for email on_session not having an app_id parameter #444
  • Fix for SDK not working in Firefox for HTTP sites #440
  • Fix for ServiceWorker to correctly report notification clicks in PWA #439