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(())