Releases: OneSignal/OneSignal-XCFramework
Releases · OneSignal/OneSignal-XCFramework
Release 3.12.0
Adding Live Activity Support
Added two public methods
- enterLiveActivity
- exitLiveActivity
These public methods make API calls and associate anactivityIdwith a temporary push token on the OneSignal server
Adding Live Activity Support to the Example project
Users can now start a demo Live Activity from the example project.
Scroll down on the main screen and click "Start Live Activity"
PRs included in this release
OneSignal/OneSignal-iOS-SDK#1150
OneSignal/OneSignal-iOS-SDK#1152
Release 3.11.5
Releasing 3.11.5 to fix checksum issues in 3.11.4
PRs included in this release
None
Release 3.11.4
Releasing the SDK using Xcode 13 build tools and re-including 32 bit architectures
- PR OneSignal/OneSignal-iOS-SDK#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
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.
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.
PRs included in this release
OneSignal/OneSignal-iOS-SDK#1120
OneSignal/OneSignal-iOS-SDK#1121
OneSignal/OneSignal-iOS-SDK#1122
OneSignal/OneSignal-iOS-SDK#1131
OneSignal/OneSignal-iOS-SDK#1132
Release 3.11.2
Swizzling fixes
- This release includes a rework to OneSignal's swizzling that fixes a Kotlin issue and other potential compatibility issues
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 an issue with 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
OneSignalfor your app target, and productOneSignalExtensionfor your Notification Service Extension target. - Then in your NotificationService class import
OneSignalExtensioninstead ofOneSignal
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.
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.
Improving the logging of various Errors
- Error logs will now include the entire NSError object incase the localized description is empty.
This release corresponds to OneSignal-iOS-SDK release 3.10.3
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.
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
pauseInAppMessagessetting.
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.
This release corresponds to OneSignal-iOS-SDK Release 3.10.2
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.
Fixing setLauchUrlsInApp after calling OneSignal init
setLaunchUrlsInAppwas not taking effect if it was called after the OneSignal initializer.
Fixing sendTags after rejecting the push permissions prompt
- Tags were not being sent when registering a user if the push permission prompt was denied.
This release corresponds to OneSignal-iOS-SDK release 3.10.1