3.7.1 Release

Updated Native Android (3.12.5), Updated Native iOS (2.12.5), Minor Bug Fixes

• Native Android SDK Updates:
  • Release Notes 3.12.4
  • Release Notes 3.12.5
• Native iOS SDK Updates:
  • Release Notes 2.12.3
  • Release Notes 2.12.4
  • Release Notes 2.12.5

3.7.0 Release

iOS - Outcomes & Received Receipts

• New Outcomes feature
• New Received Receipts
• iOS SDK native updates
  • OneSignal-iOS-SDK 2.12.0
  • OneSignal-iOS-SDK 2.12.1
  • OneSignal-iOS-SDK 2.12.2
• Android SDK native updates
  • OneSignal-Android-SDK 3.12.3

3.6.0 Release

Outcome Events Implemented for Android

• Updated OneSignal-Android-SDK 3.12.2
• Updated OneSignal-iOS-SDK 2.11.2

3.5.0 Release

In-App Messaging Implemented for iOS

• Added In-App Messaging to iOS

Updates from OneSignal-iOS-SDK 2.11.0

• Added in In App Messaging feature
• Various minor bug fixes

Updates from OneSignal-Android-SDK 3.11.4

• Fixed getActiveNotifications() crash related to NotificationManager class
  • Similar to issue #422, but for Android 8.0.0 Samsung devices
• Fixed an issue with In App Messaging where a drag would sometimes trigger an action

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

3.4.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.
• Replaced GCM dependency with Firebase Messaging dependency
• Added Xamarin.GooglePlayServices.Ads.Identifier to fix missing AdvertisingIdClient when upgrading to version 70+ of Xamarin.GooglePlayServices.Basement.
• Added UnsubscribeWhenNotificationsDisabled builder method for Android.
• 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

3.3.0 Release

Updated Native OneSignal SDKs & Android Dependencies

• Updated to Android OneSignal SDK 3.10.8
• Updated to iOS SDK 2.10.0
• Removed upper bounds for Android dependencies to Google Play services and the Android Support Library

3.3.0 Beta Release

Updated Dependencies for MonoAndroid9.0

• Updated GooglePlayServices and Android.Support dependencies

3.2.2 Release

External User ID Support

• 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

3.2.1 Release

• Updates the native Android and iOS SDK's

iOS 2.8.8 Improvements & Fixes

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

Android 3.10.1 Improvements and Fixes

• 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. #587
• Updated fix for error with startWakefulService on Oreo when sending high priority with remote urls.
• Fixed NPE with flushBufferToDisk #513
• Fixed idsAvailable not being called a 2nd time when registrationId was null. PR #563