Releases: OneSignal/OneSignal-iOS-SDK
Releases · OneSignal/OneSignal-iOS-SDK
1.11.1 Release
Added one more constructor to just take appId and launchOptions
- Xamarin does some strict enforcement for parameters at runtime.
It was agreed that there needs to be a constructor that just takes
the OneSignal application id and launch options, but not the notification
handler callback.
1.11.0 Release
New payload support, runtime warnings, and other misc fixes
- Added support for new os_data nested payload
- Fixed issue where OneSignal_APPID was not being read from the plist.
- Depercated setDefaultClient, set automaticly and should not be changed.
- Fixed iOS 9 warnings about cydia
1.10.6 Release
Log name conflict and defaultClient nil fix
1.10.5 Release
More dSYM Xcode 7 warning fixes
- Disabled GCC_PRECOMPILE_PREFIX_HEADER
1.10.4 Release
Disabled dSYM to fix Xcode7 warnings
- Disabled dSYM, no code changes to the SDK codebase itself.
1.10.3 Release
Enabled bitcode
- Enabled bitcode, no code changes to the SDK codebase itself.
NOTE: Requires Xcode 7.0+ for simulator builds
- Due to Xcode incompatibility issues from Xcode 6 to 7.
1.10.2 Release
Cocoapods update fix.
Fixed error on Resources when running pod install
a 2nd time after adding OneSignal.
- Only a cocoapods fix, no code changes to the SDK codebase itself.
1.10.1 Release
Fixed slow launch URL and Pollfish linker error
- Fixed issue where opening a notification with a launch URL would sometimes take to up 10 seconds before Safari would start.
- Fixed _VERSION link error when Xcode project contains both Pollfish and OneSignal.
1.10.0 Release
Title support, notification clearing & open count
- Added support for notification title on iOS 8.2+ devices.
- Fixed bug where notifications would clear when opening / resuming the app.
- Notifications will still be cleared in this way when a badge is set.
- This is due to an iOS limitation where clearing the badge count has a side effect of clearing all notifications from the app.
- iOS 6 & 7 - When a notification is opened all other notifications from the app will still be cleared.
- This logic remains otherwise notifications can be tapped on multiple times.
- Notifications will still be cleared in this way when a badge is set.
- Fixed bug where if content-available was set the notification would be marked opened when received and again when it was opened.
1.9.2 Release
Fixed issue with autoRegister
Fixed issue #1 where the iOS notification permission prompt would show on the 2nd cold start of the app when autoRegister is set to false.