Releases: OneSignal/OneSignal-iOS-SDK
2.11.0 Release
In-App Messaging Added
- Added in In App Messaging feature
- Various minor clean up and bug fixes
2.10.2 Release
Updated Project to WKWebView and Removed -ObjC Flag
- Switched to WKWebView from deprecated/removed UIWebView
- Fixes issue #522
- Removed requirement of -ObjC flag
2.10.1 Release
2.10.0 Release
2.9.5 Release
• This update fixes a longstanding issue with buttons, where the SDK would always show the buttons of the most recently received notification.
• For example, if a notification is received with a "Like" button, and then another notification is received with an "Unlike" button, both notifications will now display the "Unlike" button since it was the more recently received.
• This update adds a cache of registered UNNotificationCategory
identifiers, allowing the SDK to assign unique categories for each push notification, letting each notification have their own unique buttons.
2.9.4 Release
• This update adds new methods (setExternalUserId(string)
and removeExternalUserId
) allowing you to target push notifications using your own custom user ID's instead of having to store OneSignal player ID's.
• Small update that includes a fix for an issue that would have caused rare crashes, due to invalid HTTP request bodies being serialized into JSON
2.9.3 Release
• Fixes an issue with provisional notifications (no git issue) where a user would receive a provisional notification, tap 'Keep', and then tap 'Deliver Prominently', which should cause notifications to be delivered like normal: however in previous releases notifications would have no sound/alert/badge until the app was next restarted.
• Fixes some DSYMUtil warnings developers would see in regards to our framework including debugging information.
2.9.2 Release
• This release fixes an iOS 12 issue where enabling "Deliver Quietly" and then opening the app would cause notifications to stop being delivered entirely.
2.9.1 Release
• This is a minor release that adds bitcode support for our dynamic framework.
2.9.0 Release
Introduces support for new iOS 12 features. To learn more about how iOS 12 changes push notifications, please read our blog post on the subject.
Provisional/Direct To History Notifications
• Provisional notifications are a new way to message users without requesting their permission to send push notifications. Unlike traditional notifications, a provisional notification is sent directly to the Notification Center and does not alert/disturb the user directly.
• To use Provisional notifications, set kOSSettingsKeyAutoPrompt
to false
in your initialization settings. Then, navigate to https://www.onesignal.com and in your iOS platform settings, enable Direct To History notifications. From now on, all users that open your app will be able to receive provisional notifications unless they explicitly disable notifications for your app
Manage App Notification Settings
• iOS 12 introduces support to let your app provide a deep link to manage settings from within your app.
• To enable this, please set our init setting kOSSettingsKeyProvidesAppNotificationSettings
to true
. You also need to implement a UNUserNotificationCenterDelegate
method to present your custom Notification Settings UI.
Thread-ID Support
• iOS 12 also introduces Notification Grouping which allows you to group related notifications together. To do this, set the thread-id
parameter in your push notifications. iOS will automatically group notifications with the same thread-id
together.
Bug Fixes & Improvements
• Fixes an issue with Xcode 10 that caused crashes to the IBDesignables agent and made users unable to use IBDesignable views in storyboards/xibs
• Adds a new reachable
parameter to the OSPermissionState
. This new parameter indicates if the user is reachable and can receive notifications, and will be true
if they've (A) accepted notification permission or (B) are registered to receive provisional/direct-to-history notifications.