Release 5.2.7

🔧 Maintenance

• For our server only: Update a header value when the SDK fetches in-app messages #1509

Release 5.2.6

✨ Improvements

• Don't use cached in-app messages if the SDK encounters an error fetching them or when the server returns none (#1499)
• Improve segment membership calculation that allows for fetching more accurate and updated in-app messages for a user (#1486)
• Fixed typo in verbose logging from 'occured' to 'occurred' (#1500)

Release 3.12.10

⚠️ Please update to this release to ensure launch URLs continue to work on iOS 18 devices ⚠️

🔧 Maintenance

• [3.x.x] Replace deprecated openURL method preventing launch URLs #1493

✨ Improvements

• [3.x.x] Privacy manifests - User Defaults API reason to include app groups #1494

Release 5.3.0-beta-01

🎉 Identity Verification Support

This beta release introduces Identity Verification support for the iOS user model SDK.

To get started with using Identity Verification, please contact [email protected] to enable this feature for your app. Please see documentation on Identity Verification.

We appreciate your experience and feedback using this beta version!

🚧 Beta release. Please test thoroughly prior to production use 🚧

• It is recommended to test this beta version with a new iOS-only app, as Identity Verification is not yet supported on the OneSignal Android and Web SDKs.
• Enabling Identity Verification in the dashboard will affect all existing app installations using the OneSignal user model SDKs.
• Please test thoroughly prior to production use, and reach out with any questions, feedback, or concerns.

⛔️ Limitations and Known Issues

• While emails and sms numbers can be added using the SDK, removing them is not yet supported.
• Live Activities is not yet supported.

Release 5.2.5

✨ Improvements

• Pausing IAMs dismisses any currently showing IAM (#1480)

Release 5.2.4

✨ Improvements

• [Fix] Handle incorrect 404 by delaying making updates to new users or subscriptions (#1470)

Release 5.2.3

🐛 Bug Fixes

• The user executor needs to uncache first which fixes some cached requests being dropped for past users #1465

✨ Improvements

• Omit misleading fatal-level log for cross-platform SDKs #1468

🛠️ Maintenance

• [For our server] Use only OneSignal ID for requests #1464

Release 5.2.2

🐛 Bug Fixes

• Prevent In-App Message request crashes by making null values safe #1457
• Add Dispatch Queues to all executors to prevent concurrency crashes #1454
• Fix clearing notifications incorrectly such as when pulling down the notification center #1451

Release 5.2.1

🐛 Bug Fixes

• Fix warning about decoding a boolean (#1436)
• Fix a purchases bug for the amount spent (#1444)
• Fix a build issue for mac catalyst (#1446)
• Fix crash when IAM window fails to load by using the main thread (#1447)

🔧 Maintenance

• Network call optimizations: Combine user property updates for network call improvements (#1444)

Release 5.2.0

What's New

🎉 Push to Start Live Activities

Starting with iOS 17.2, Live Activities can now be started via push notification (Apple's documentation). This change enhances the OneSignal SDK to provide application's access to the full suite of Live Activity functionality.

To use Push To Start Live Activities, see documentation on How to start a Live Activity with a remote push notification.

NEW Preferred method to setup Live Activities with OneSignal
A new function OneSignal.LiveActivities.setup has been created which allows OneSignal to manage the lifecycle of a LiveActivity on behalf of the application. This includes listening for both pushToStart token updates and pushToUpdate token updates. When using this method, the application does not need to listen for pushToStart token updates, the starting of a live activity, nor update token updates. A typical usage looks like this:

OneSignal.LiveActivities.setup(MyWidgetAttributes.self)

Default Live Activity
The concept of a "Default" Live Activity has been established in the SDK, which eliminates the need for a customer app to define and manage their own ActivityAttributes. The primary use case of the "Default" Live Activity is to facilitate easier cross-platform SDK adoption.

Please see the PR description for more details.

• Push to start live activities added to the SDK (#1377)

Other Changes

✨ Privacy Manifest Improvements

• Add additional 6 privacy manifests to the 6 sub-targets that are included in the primary targets clients import (#1431)
• Update User Defaults API reason to include app groups for appropriate modules (#1429)

🐛 Bug Fixes

• [Bug] Fix rare scenario of dropping data when multiple logins are called (#1427)