2.5.2 Release

Fixed let javascript error for older devices

• 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

2.5.1 Release

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 setRequiresUserPrivacyConsent(true) is set
• Android - Fixed "App may not schedule more than 100 distinct jobs" error, mostly affecting Samsung devices in rare cases

2.5.0 Release

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
• Fixed com.onesignal.PrivacyConsent AndroidManifest.xml check when using newest init method.
  • PR #786
• Fixed location permission prompting and session count / time tracking after privacy consent is accepted.
  • PR #772

2.4.7 Release

Updated native Android & iOS SDKs

• Updated to Android OneSignal SDK 3.10.8
• Updated to iOS SDK 2.10.0

2.4.6 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.

Android Fixes & Improvements

OneSignal Android 3.10.5 SDK

• Removed ACTION_BOOT_COMPLETED for BOOT_COMPLETED
  • ACTION_BOOT_COMPLETED is invalid, BOOT_COMPLETED is 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

2.4.4 Release

• 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.

2.4.3 Release

• 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)

2.4.2 Release

• Updates the iOS (2.8.6) and Android (3.10.1) native SDK's to the latest versions
• Fixes an issue that broke the setLocationShared() function

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).

Android SDK Improvements (3.10.1)

• Fixes a thread synchronization bug that in some situations could cause the main thread to lock up while waiting for a network request to finish.
  • Resolves Issues #589, #590, #599, and react-native #587

2.4.1 Release

• Updates the iOS (2.8.5) and Android (3.9.1) native SDK's to the latest versions
• Automatically adds OneSignal-Gradle-Plugin, replaces forcing of gms, android.support, and firebase to exact versions

iOS SDK Improvements (2.8.5)

• Fixes a rare concurrency issue with the SDK's HTTP client.
• This issue would have caused exceptions when GDPR consent was revoked, or in some wrapper SDK's, early in the app lifecycle before the app ID was provided.

Android SDK Improvements (3.9.1)

• Fixed issue with latest Proguard causing FCM and Android Support library report as not found.
  • Issue #533
• FCM init error when the Firebase Auth library was added to the project. PR #530
• Fixed GoogleAPIClient not connected yet errors. Issue #509
• Android 7.0 Bad Notification: Couldn't expand RemoteViews for: StatusBarNotification
  • Restore on app update disabled to fix issue #263
• NPE on flushBufferToDisk. Issue #513

2.4.0 Release

GDPR Support

• Adds new methods for Android and iOS that allow developers to require user consent before the SDK is fully initialized.
• Developers can call OneSignal.setRequiresUserPrivacyConsent(true) to require a user's consent before the SDK collects any information.
• Until this point, any calls to the SDK are ignored. Once OneSignal.provideUserConsent(true) is called, the SDK will fully initialize. By default, this behavior is turned off.

Native Updates

Android SDK - 3.9.0

• Now supports FCM (Firebase Cloud Messaging) library
  • This upgrade is automatic as long as you followed the OneSignal standard setup guide.
  • After April 11, 2019 Google will drop the GCM from new versions their Play Services library
  • GCM (Google Cloud Messaging) is still supported in the OneSignal SDK until then
  • Issue #507
• Fixed NPE on UserState.dependValues. Issue #503

iOS SDK - 2.8.4

• The SDK will now work with media attachment URL's that don't end in file extension (ie. .jpg). If a URL is missing a file extension, it will instead use the MIME type of the asset.
• Resolves an incompatibility issue with the HelpShift iOS SDK
• Fixes an issue that caused incorrect "notification opened" events to be sent to OneSignal's backend server