Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 40 million developers.Sign up
Outcomes for Android
Added support for Outcomes (Android only). Outcomes allow you to track various outcomes (events or actions) resulting from push notifications. This includes tracking things you care about like event counts (e.g. how many users purchased a product), sums (useful for tracking revenue and more), or unique events (counted only once).
Read more here
- FIxed undefined 'let' for older devices that do not support the ES6 keyword
- Mostly affected Android 4.4 and older devices.
- Bug was introduced in 2.5.0
iOS 13 Beta 2+ pushToken and Other Android Misc Fixes
Updates from OneSignal-iOS-SDK 2.10.1
- Fixed deviceToken format error with iOS 13 Beta 2+ which was preventing the device from subscribing to OneSignal.
Updates from OneSignal-Android-SDK 3.11.2
- On Android N (7.0)+ devices when 4 or more notifications are shown tapping on the group is now handled
- Issue was related to Android's auto grouping feature.
- Now counts the most recent notification in the group being opened when the summary notification is tapped.
- Android - Fix NPE errors when app is resumed when
- Android - Fixed "App may not schedule more than 100 distinct jobs" error, mostly affecting Samsung devices in rare cases
Android - In-App Messages & Changing AppId Fixes
- See the OneSignal In-App quickstart guide for more details.
- When re-initializing with a different AppId the device registers correctly without requiring an app cold start
- Dashboard parameters are now correctly refreshed as well from the new app id.
- Notification Channels / Categories, added invalid format handling to LED colors.
- PR #775
AndroidManifest.xmlcheck when using newest init method.
- PR #786
- Fixed location permission prompting and session count / time tracking after privacy consent is accepted.
- PR #772
• This update adds new methods (
removeExternalUserId) allowing you to target push notifications using your own custom user ID's instead of having to store OneSignal player ID's.
Android Fixes & Improvements
OneSignal Android 3.10.5 SDK
BOOT_COMPLETEDis the correct intent action
- Catches security exception from Job Intent Service
- Fixes issue #673
iOS SDK Fixes & Improvements
OneSignal iOS 2.9.4 SDK
- 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
• Updates to the latest iOS Native SDK
iOS SDK Improvements (2.8.8)
• This release fixes an issue (#410) where users that add buttons/functionality to a notification by directly using UNNotificationCategory instead of using our API would cause a crash
• Fixes a thread synchronization issue that would have deadlocked the main thread in very rare situations on initialization (#409)
• Fixes an issue where improperly formatted button JSON (from the create notification API) would cause the SDK to insert nil objects into an NSDictionary instance, causing an EXC_BAD_ACCESS (#402)
• Adds an additional dynamic framework/cocoapod for developers who previously encountered 'transitive dependency' errors using our SDK indirectly as a dependency of another cocoapod in Swift projects (#412)
• #403 Fixes a bug that only effected wrapper SDK's, such Cordova and React-Native, where calling setLocationShared(false) could still result in location data being sent to OneSignal if the app had location permission in iOS (Cordova SDK issue #406)
• #397 Fixes a bug that caused devices to never register with OneSignal if APNS did not respond with a token or failure.
• Fixes issues with the
setLocationShared() function by updating to iOS Native SDK 2.8.7
iOS SDK Improvements (2.8.7)
• Fixes an issue in wrapper SDK's where calling
setLocationShared(false) to disable location sharing would not work, the SDK would continue to send location data if the app had location permission enabled. (#406)
• Updates the iOS (2.8.6) and Android (3.10.1) native SDK's to the latest versions
• Fixes an issue that broke the
iOS SDK Improvements (2.8.5)
• Fixes an issue (#391) that would have caused rare crashes (
EXC_BAD_ACCESS) in our API client because it attempted to execute a completion block without ensuring it was non-nil, which it could be in rare circumstances.
• Fixes an issue that would occasionally cause the SDK to be unable to automatically retrieve the App Group name, which was used to enable communication between the Service Extension and the main app. The main side effect of this issue would have been inconsistent badge logic, where the SDK would not maintain a logically consistent badge count.
• Fixes other minor problems, such as a potential (but never reported) crash in
setEmail(), also fixed an issue where the method that downloads attachments such as images wasn't using a double pointer to set errors that may occur during the download (common pattern in ObjC).