1.0.2 Release

Flutter SDK Updates

• Fixes an issue where an exception would be thrown when initializing the SDK if the optional iOSSettings parameter was not provided (#11)
• Fixes compiler warnings due to invalid type conversions in our SDK (#14)
• Fixes a null pointer exception that would occur in Android when calling getTags() if the user did not have any tags set (#15)
• This update fixes an issue where developers with Swift-Flutter projects in iOS were completely unable to install our SDK due to a transitive dependencies warning (#6)

• To fix this issue, we have changed our Flutter SDK to use a dynamic framework version of our native iOS SDK
• An important note is that our new dynamic framework is a fat framework, it includes support for the iOS simulator (x86_64) and real devices (arm64). Unfortunately Apple will not allow apps uploaded with fat frameworks, so we are adding instructions on how to add a buildscript that will strip unnecessary architectures from your app when uploading to the store.

iOS Native SDK Release Notes (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
• 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
• Fixes a bug that caused devices to never register with OneSignal if APNS did not respond with a token or failure.
• 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 Native SDK Release Notes (3.10.1) - Fix ANR's (Application Not Responding)

• 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

1.0.1 Release

• This release contains only minor internal stylistic improvements

1.0.0 Release

• This is the first official release of OneSignal's Flutter SDK
• It is compatible with both Android and iOS projects, and is a wrapper on top of OneSignal's native iOS and Android SDK's.