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 via OneSignal.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 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

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.

Release 150505

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

Release 150503

Includes:

• Fix for on_session/player update logic to correctly track last_active timestamp and minimize the number of requests to our backend #433
• Fix for missing appId in UploadManager #437

Release 150501

Includes the following improvements:

• Prompting for push notifications in Safari 12.1 will start requiring user interaction, making changes in SDK to work correctly #418
• Fix for resubscribe flow after user manually blocks and allows push notifications #428
• Bringing OneSignal.off back #427
• and a few other minor fixes

150500 Release

Reducing the size of the OneSignal service worker file by:

• removing unnecessary code #413
• introducing 2 separate configs for Service Worker file (now targeting ES6) and SDK file (still targeting ES5) #414

150404 Release

Includes the following bug fixes:

• Making sure localhost http is treated as secure if allowLocalhostAsSecureOrigin is set to true (#408)
• Improved on_session reporting (#400)
• Ensure getRegistration in Service Worker can handle throws (#393)
• Fix error caused by a user blocking localStorage (#379)

150403 Release

Fix for OneSignal init in Chrome 69 on http

• Fix for Issue #404

150402 Release

Init on HTTP "Secure origins" Error Fix

• Fixes DOMException: Only secure origins are allowed error during init on HTTP sites
  • Issue #391