2.8.9 Release

• This release fixes an issue where the SDK was not properly handling HTTP request re-attempts. This would have resulted in an issue where calling sendTags() (for example) while a user had no network connection would, after 60 seconds, result in the onSuccess callback being executed.

• Removes some unnecessary log statements and other minor cleanup of the SDK

• Includes a fix for a merge mistake in the previous release that reverted a few minor/rare bugs.

2.8.8 Release

• 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 (#409)

• 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

2.8.7 Release

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

2.8.6 Release

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

2.8.5 Release

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

2.8.4 Release

• Fixes a private API issues preventing developers from uploading binaries to the App Store
• Any methods named valueForQueryParameter() are apparently flagged by Apple as private API usage......
• Changed the name of the method so it no longer triggers this issue.

2.8.3 Release

• The OneSignal iOS SDK now includes GDPR privacy consent methods which allow developers to postpone initialization of the SDK until the user provides privacy consent.
• This new GDPR privacy setting can be controlled by adding OneSignal_require_privacy_consent to your application's Info.plist and setting it to YES.
• Once the user accepts the GDPR privacy permissions, your application can call OneSignal.consentGranted(true)
• Your users can revoke privacy consent at any time by calling OneSignal.consentGranted(false)

• 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

2.8.2 Release

• Adds a new badge handling system in the OneSignalNotificationServiceExtension
• The SDK now handles badge count logic on the device itself instead of relying on the backend
• Adds support for the NSLocationAlwaysAndWhenInUseUsageDescription Info.plist location permissions key
• Added app_id present checks in unit tests
  • PR #357 and #353

2.8.1 Release

• Fixes a rare crash that would occur when an app immediately sends tags before the device is registered, while only providing one success/error callback and nil for the other callback.
• Fixes an issue that caused the OneSignal SDK to improperly handle non-OneSignal push notifications
• Fixes an issue that caused in-app purchases to not get reported to OneSignal

2.8.0 Release

• Adds a setting called kOSSettingsKeyPromptBeforeOpeningPushURL which allows developers to control what happens when a user taps a notification with a web URL. If this setting is set to true, the SDK will prompt the user with an alert asking if they want to open the website or not. By default, this setting is false.
• Adds ability for postNotification() to preprocess NSDate objects so that developers can add a delay without having to convert to strings first
• The SDK will now always convert email auth hash tokens to be lowercase for consistency
• syncHashedEmail() is now officially deprecated: added a deprecation notice.
• Removed use of private Apple API's which caused problems in (very) rare circumstances. This private API was implemented in order to call deprecated methods for developer convenience. However we have removed this functionality in order to avoid problems with the app review process. The SDK will now print an error to the console if a developer implements these methods.
• Fixes an issue that would have caused problems parsing notifications in a new payload format.
• Fixed some issues that caused crashes in iOS 7.