Release 3.11.4

Releasing the SDK using Xcode 13 build tools and re-including 32 bit architectures

• PR #1132 Removed 32 bit architectures since they are not supported in Xcode 14, but this causes us to drop support for iOS 9 and 10. This release adds back the 32 bit architectures while still allowing us to develop in Xcode 14. #1134

PRs included in this release

#1134

Release 3.11.3

Fixing swizzling of non OneSignal notifications on notification open

• Fixing a swizzling issue where for non OneSignal notifications we were not forwarding notification opens to the app delegate's remoteNotificationReceived method. #1131

Fixing an Xcode 14 warning related to a CLLocationManager API being used on the main thread

• Running locationServicesEnabled on the main thread causes an Xcode warning in Xcode 14 about a potential UI holdup. This method will no longer be called on the main thread. #1132

PRs included in this release

#1120
#1121
#1122
#1131
#1132

Release 3.11.2

Swizzling fixes

Rework to OneSignal's swizzling which addresses:

• Fixes compatibility with Swift projects that use UIApplicationDelegateAdaptor (fixes #1045 & #1069)
• Fixes app startup issues:
  • Kotlin 1.6 (issue #1042)
  • Fixes rare crash on realizeClassMaybeSwiftMaybeRelock (#1042 (comment))
• Some instances of the “Apns Delegate Never Fired” error related to compatibility with other SDKs that use the AppDelegate:
  • Multiple classes that implement UIApplicationDelegate
  • Class that inherits from a class that implements UIApplicationDelegate but never calls super.
• other potential compatibility issues

PRs included in this release

#1103
#1102
#1101
#1100
#1099
#1094
#1097
#1091
#1090
#1089

Release 3.11.1

Fixing a crash when attempting to get location for the device

• Release 3.11.0 introduced a crash when attempting to use location services on the device. #1086

Release 3.11.0

This release modularizes the iOS SDK to resolve issue #396 regarding a warning when including OneSignal in your Notification Service Extension.

Resolving the issue will require changes to how the SDK is imported, but this release in general should be a non breaking change.

For Swift Package Manager

• Use product OneSignal for your app target, and product OneSignalExtension for your Notification Service Extension target.
• Then in your NotificationService class import OneSignalExtension instead of OneSignal and change references of OneSignal in method bodies to OneSignalExtension

For Cocoapods

• In your Podfile make sure that your Notification Service Extension target is nested in your App target.
• Use pod OneSignal or OneSignalXCFramework (they are now identical) for your app target, and subspec OneSignal/OneSignalExtension or OneSignalXCFramework/OneSignalExtension for your Notification Service Extension target.
• Then in your NotificationService class import OneSignalExtension instead of OneSignal
• Lastly from the Other Linker Flags build setting in your Notification Service Extension target remove $(inherited) and -framework "OneSignal"

Release 3.10.3

Fixing In App Messages being displayed on Mac Catalyst apps when running on an M1 Mac

• OneSignal was improperly detecting Mac Catalyst apps when running on an M1 Mac. In App Messages will no longer display in this case. #1076

Fixing the Duration Since Last Message Shown trigger when the app is quit and relaunched

• The timestamp for the last shown In App Message will now persist between restarts of the app. #1070

Improving the logging of various Errors

• Error logs will now include the entire NSError object incase the localized description is empty. #1068

3.11.0 Beta

This beta release modularizes the iOS SDK to resolve issue #396.

Resolving the issue will require changes to how the SDK is imported, but this release in general should be a non breaking change.

For Swift Package Manager

• Use product OneSignal for your app target, and product OneSignalExtension for your Notification Service Extension target.
• Then in your NotificationService class import OneSignalExtension instead of OneSignal

For Cocoapods

• In your Podfile make sure that your Notification Service Extension target is nested in your App target.
• Use pod OneSignal or OneSignalXCFramework (they are now identical) for your app target, and subspec OneSignal/OneSignalExtension or OneSignalXCFramework/OneSignalExtension for your Notification Service Extension target.
• Then in your NotificationService class import OneSignalExtension instead of OneSignal
• Lastly from the Other Linker Flags build setting in your Notification Service Extension target remove $(inherited) and -framework "OneSignal"

Release 3.10.2

Fixing occasional crash when using tag substitution in In App Messaging

• Fixes a crash when loading tags returned after loading IAM html content. #1060

Test In App Messages will now be displayed when In App Messages are set to be paused.

• In App Messages sent to test devices now ignore the pauseInAppMessages setting. #1050

Properly ending background task when using background location services

• OneSignal's location feature now properly ends the background task it starts when using background location services. #1049

Release 3.11.0-alpha-01

Alpha release for testing the modularization of the OneSignal iOS SDK.

Release 3.10.1

Properly setting external user id when using setEmail and setSms

• External User Id will now properly be set on email and sms records when they are created. #1044

Fixing setLauchUrlsInApp after calling OneSignal init

• setLaunchUrlsInApp was not taking effect if it was called after the OneSignal initializer. #1043

Fixing sendTags after rejecting the push permissions prompt

• Tags were not being sent when registering a user if the push permission prompt was denied. #1037