3.7.0 Release

Fixes upload error due to OneSignal being built with Beta Xcode version

• Apps should no longer get error #986 which was a result of building the OneSignal framework with Xcode 13 build tools.

In App Messaging Lifecycle Events

• Apps can now observe the display lifecycle for In App Messages through a OSInAppMessageLifecycleHandler. Documentation for the new handler is here! #977

Release 3.6.2

Register user will be run on the main thread

• This change will help fix various memory related crashes by increasing thread safety when registering the user #981

Transparent Background images In App Messaging

• In App Messages will now render in a way that allows for transparent background images in In App Messages. #982

Fix occasional In App Messaging related crash for SwiftUI Apps

• Fixing a crash caused by adding constraints to views that aren't in the same heirarchy #983

Release 2.16.6

Fixes

• Fixes rare crash with some apps due to a threading issue. PR #979

Release 3.6.1

Fixing occasionally setting badge number on background thread

• Setting the application badge count will now always occur on the main thread #970

Always validating that mallocs are successful

• OneSignal now always validates that manual memory allocation is successful. #969

Release 3.6.0

Added setLanguage

• Feature app defined setLanguage #948

Fixes

• Fix missing push notification capability error detection #962
• Fix/calling nil failure block #961

Release 3.5.3

Fixing occasional double display of IAMs

• Fixing IAMs being displayed twice on cold start for "on app open" IAM triggers with redisplay enabled.
  #949

Fixing send tags failure block not called on bad input

• The send tags failure block will now be called if the data is not a valid json Object
  #952

Release 3.5.2

Fixing Images not being added to notifications when passing in the contentHandler to didReceiveNotificationExtensionRequest

• When using the new version of didReceiveNotificationExtensionRequest images were are now properly attached to the notification. #943

Release 3.5.1

Fixing nullability of contentHandler parameter of didReceiveNotificationExtensionRequest

• The nullability has been changed from Nullable to Nonnull for the contentHandler parameter to fix Swift builds using the new version of didReceiveNotificationExtensionRequest #941

Release 3.5.0

New method for handling notification content from the Notification Service Extension

• OneSignal now calls the contentHandler block automatically when it is passed into didReceiveNotificationExtensionRequest. The version of this function that doesn't include the contentHandler parameter has been deprecated. See the change documentation here #934

Fixing Badge Counts not always clearing on App Reinstall

• On new iOS versions the App Badge Count would not always be cleared when the app was uninstalled and reinstalled. #939

Fixing Unit tests failing for hostless unit test target

• OneSignal will no longer cause unit tests to fail for hostless unit test targets. #936

Release 3.4.4

Fixing Impressions being sent after an IAM has been stopped

• In app messages could false receive impressions after an IAM has been stopped even though it wouldn't display to the user. #931

Fixing IAMs potentially not updating due to caching IAM content requests

• OneSignal will no longer cache IAM content requests so changes will reflect immediately. #930 #929
• Also fixes un-cached tags not always substituting when using Liquid Templating in IAMs.

Fixing a race condition for notification delegates in the Unity SDK

• This fixes an issue where OneSignal's notification open event would not fire if a UNUserNotificationCenterDelegate was assigned before the OneSignal was loaded into memory. #926