Releases: OneSignal/OneSignal-iOS-SDK
Releases · OneSignal/OneSignal-iOS-SDK
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.
2.0.9
- Added links to OneSignal's setup instructions in OneSignal.h.
- Fix: The idsAvailable callback will now be called with a device push token after the user has accepted notification permissions. This means it can now be called twice (as with the 1.x SDK versions) -- once before the user has granted permission (token will be blank) and once after the user grants push permission (token will not be blank).
- Fix: Not initializing the OneSignal SDK no longer blocks swizzled UIApplicationDelegate methods from getting called.
2.0.8
2.0.7
2.0.6
2.0.5
2.0.4: - Added option to override default in-app display of launch urls
- Added option to override default in-app display of launch urls
- Fixed iOS 7 crash on init
- Fixed handling notifications when app active and in-app alerts are
false - Fixed auto-prompt not calling issue
- Fixed Null ActionID when app in focus and InAppAlerts are ON.
- Fixed issue where swizzling would still run even if OneSignal SDK is
not setup in the project.
2.0.3
2.0.2 Release
- Enabled bitcode
- Fixed launch URL bug
2.0.1 Release
Launch url crash and auto prompt fixes.