Releases: OneSignal/OneSignal-iOS-SDK
Releases · OneSignal/OneSignal-iOS-SDK
2.1.8
2.1.6
2.1.5
2.1.4
2.1.3
2.1.2
- Fixed an issue where receiving two notifications with launchURLs would launch multiple webviews without dismissing currently open ones.
- Updated device registration login. OneSignal will now wait a few seconds to try to get a device token before registering with OneSignal's servers. This prevents some cases where devices could be duplicated on the dashboard when previous device data had been imported.
2.1.1
- iOS 10 fixes:
- In-app alerts will no longer show up alongside native notifications when InAppAlerts are enabled.
- Changed the way the OneSignal SDK extracts attachments from the notification payload.
- Added a mutableContent property to the OSNotificationPayload for iOS 10.
- Remote silent notifications will no longer show an alert in an app that is in focus when InAppAlerts are enabled.
- Dismiss the in-app webview when coming back to the app after receiving a deep linked URL and kOSSettingsInAppLaunchURL is true.
2.1.0
- didReceiveRemoteNotification will no longer be swizzled in cases where a developer has implemented it without also implementing the didReceiveRemoteNotification:fetchCompletionHandler when the app is cold started from a tap on a remote notification.
- Added helper methods to serialize OSNotification objects into JSON-parseable strings for easier integration with 3rd party frameworks like React Native.
- Modified the Run Script to create a module map after building.
2.0.11
- Crash Fix - This release fixes a crash on versions of our SDK 2.0.0 and newer on iOS 10 devices. This crash occurs when an iOS 10 user launches the app by tapping on a notification with a Launch URL if you have set kOSSettingsKeyInAppAlerts to
false
(default istrue
). Please update to this SDK release or newer to resolve this issue. - Fixed an issue where the notificationAction block would be called twice on iOS 10 devices when a user tapped on a notification.
2.0.10
- Resolves an issue where UIAppDelegate protocol methods are are not called when a developer has subclassed their App Delegate and overridden these methods. The OneSignal SDK will now check for all AppDelegate subclasses to find which proper class to inject to, and the SDK makes sure the subclass overrides the required method and does not simply inherit it from a superclass.
- When developers use background or foreground location features, the OneSignal SDK will now more frequently check the device's location for location-based notifications.