Releases: OneSignal/OneSignal-iOS-SDK
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
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.
2.7.2 Release
2.7.1 Release
Fixes a small compiler warning in OneSignal.h for users that have 'Enable Nullability Annotation Checks' enabled in their project's build settings.
2.7.0 Release
• Fixes an issue where the Send Tags callback will never get called if executed within the first 30 seconds of the app being launched for the very first time
• Fixes an iOS specific issue with the OneSignal Unity SDK where "Fatal: Invalid AppId Format" error was printed to console and initialization didn't finish on the first init() call (OneSignal-Unity-SDK Error #77)
• Adds HTTP request re-attempt logic. If an HTTP request fails due to a server error (code ~500), the SDK will automatically reattempt the request soon after.
• Fixes a race condition issue described in #327 where the subscription observer should be delayed until OneSignal's server has received the updated notification permissions
• Adds exception handling logic to the extension to download attachments to prevent unnecessary crash reports.
2.6.2 Release
• Fixes an issue that caused a small memory leak every time the SDK made an HTTP request
• Fixes an issue that caused buttons not to appear in iOS 7 push notifications
• Fixes a small memory leak every time the device location was updated
2.6.1 Release
• Fixed a rare crash caused by client attempting to send invalid tags
• Added JSON validation to all requests to prevent similar crashes
• Refactored & improved REST model throughout the OneSignal SDK