Releases: OneSignal/OneSignal-DotNet-SDK
Release 5.2.1
🐛 Bug Fixes
- Fixed a startup crash for iOS 15 devices #116
🔧 Native SDK Updates
Updated included Android SDK to 5.1.20
- Optimized the initialization process by moving some service initialization to a background thread (OneSignal/OneSignal-Android-SDK#2151)
- Recover null onesignal ID crashes for Operations (OneSignal/OneSignal-Android-SDK#2157)
- Add option to default to HMS over FCM (OneSignal/OneSignal-Android-SDK#2163)
- Prevent retrying IAM display if 410 is received from backend (OneSignal/OneSignal-Android-SDK#2158)
For full changes, see the Android native release notes
Updated included iOS SDK to 5.2.3
- The user executor needs to uncache first which fixes some cached requests being dropped for past users OneSignal/OneSignal-iOS-SDK#1465
- Omit misleading fatal-level log for cross-platform SDKs OneSignal/OneSignal-iOS-SDK#1468
For full changes, see the iOS native release notes
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.
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 adoption.
- A new function
OneSignal.LiveActivities.SetupDefault()
which tells the OneSignal SDK to manage the LiveActivity lifecycle for theDefaultLiveActivityAttributes
type. When calling this method, a customer can use bothpush-to-start
andpush-to-update
notifications to start/update/end their Default Live Activity. - A new function
OneSignal.LiveActivities.StartDefault(activityId, activityAttributes, initialContentState)
which allows a customer app to start a live activity based on theDefaultLiveActivityAttributes
type "in app".
Four New APIs for Live Activities
OneSignal.LiveActivities.SetupDefault(LiveActivitySetupOptions options)
OneSignal.LiveActivities.StartDefault(string activityId, IDictionary<string, object> attributes, IDictionary<string, object> content)
OneSignal.LiveActivities.SetPushToStartToken(string activityType, string token)
OneSignal.LiveActivities.RemovePushToStartToken(string activityType)
Please see the PR description for more details.
- Push to start live activities added to the SDK (#107)
🔧 Native SDK Updates
Updated included Android SDK to 5.1.18
- Fixed Xiaomi notification click not foregrounding app
- Fixed FCM push token not being refreshed
- Poll for notification permission changes to detect permission change when prompting outside of OneSignal
- Cold start creates new session and refreshes the user from the server
- Immediately process pending operations when privacy consent goes from false to true
- Fixed OneSignal.Notifications.RequestPermissionAsync() not firing when permission was already granted
- Fixed Operation Model Store adding duplicate operations when the same ones that were previously added to the store and persisted, are re-read from cache
- Fixed a bug causing clicking an unexpanded group notification results in only registering the click result for the final notification in the group
For full changes, see the Android native release notes
Updated included iOS SDK to 5.2.2
- Prevent In-App Message request crashes by making null values safe
- Added Dispatch Queues to all executors to prevent concurrency crashes
- Fixed clearing notifications incorrectly such as when pulling down the notification center
- Fixed a purchases bug for the amount spent
- Fixed a build issue for mac catalyst
- Fixed crash when IAM window fails to load by using the main thread
- Network call optimizations: Combine user property updates for network call improvements
For full changes, see the iOS native release notes
Release 5.1.3
🎉 New Methods
See the migration guide for details on these new getters and the User observer
- Add OneSignalId and ExternalId getters as well as a user changed observer (#98)
🔧 Native SDK Updates
Update Android SDK from 5.1.8
to 5.1.10
- Fix for WorkManager not initialized crash (OneSignal/OneSignal-Android-SDK#2052)
- Various network call optimizations
- For full changes, see the native release notes
Update iOS SDK from 5.1.4
to 5.1.6
- Fix crashes when encoding user models (OneSignal/OneSignal-iOS-SDK#1412)
- Add back the dropshadow on In-App Messages and include a plist option to disable it (OneSignal/OneSignal-iOS-SDK#1395)
- For full changes, see the native release notes
Release 4.3.4
Native Dependency Updates
Update Native iOS SDK to version 3.12.9
-
🎉 New Features for Apple Privacy Requirements
- Added privacy manifests to all products
- The XCFrameworks in this release is signed to help keep your apps secure
Update Native Android SDK to version 4.8.8
-
✨ Enhancements
- Add setting to prefer HMS over FCM #1984
- Add
<meta-data android:name="com.onesignal.preferHMS" android:value="true"/>
under your<application>
tag if you like to use this setting. - See OneSignal's Prefer HMS over FCM documentation page for more details.
-
🐛 Bug Fixes
- Attempt retrying OutOfMemoryError errors when starting threads. #2027
- Make sure your app doesn't have any memory leaks and is handling onTrimMemory so the SDK can move on once memory is free
- Fix rare null crash with
taskQueueWaitingForInit.poll()
#2026- Addresses issue #1761
- Fix rare null crash with
timeFocusedAtMs
#2025
- Attempt retrying OutOfMemoryError errors when starting threads. #2027
Full Changelog: 4.3.3...4.3.4
Release 5.1.2
🔧 Native SDK Dependency Updates Only
Update Android SDK from 5.1.6
to 5.1.8
- Fix crash with EventProducer's fire events (OneSignal/OneSignal-Android-SDK#2034)
- Battery improvements
- Possibly resolves issue #1880 "Egregious levels of battery drain"
- Prevent OperationRepo from continuously pulling when empty (#2033)
- Add backoff to OperationRepo when retrying network calls (#2017)
- Limit refresh User and GET IAMs to foreground (#2036)
- Fixes network call batching not waiting the full 5 seconds in most cases to reduce the total number of REST API calls to OneSignal.
- external_id skipped and updates stop if something updates the User (such as addTag) shortly before login is called (OneSignal/OneSignal-Android-SDK#2046)
- For full changes, see the native release notes
Update iOS SDK from 5.1.3
to 5.1.4
- 5.1.4 Release Notes
- The XCFrameworks in this release is signed to help keep your apps secure
- Fix rare scenario where login requests are stuck and prevent the SDK from making updates (OneSignal/OneSignal-iOS-SDK#1398)
5.1.1
Release 5.1.0
What's Changed
⚠️ Behavior Changes ⚠️
⚠️ Xamarin is no longer supported⚠️ - Now uses .net7 SDK build tools instead of Xamarin legacy tools. #83
- Starting May 1, 2024 Microsoft will no longer maintain Xamarin either.
- Location sharing with OneSignal now defaults to false: You will need to explicitly enable location sharing with OneSignal with OneSignal.Location.setShared(true)
🎉 New Methods
- Added a
getTags
method to the user namespace #84
🐛 Bug Fixes
- Fix the types for values being sent on iOS when calling AddTriggers, AddAliases, and AddTags. #78
Native SDK Updates
Full Changelog: 5.0.2...5.1.0
Release 5.0.2
🐛 Bug Fixes
- Fix iOS Builds by updating Native Reference linking Fix Location and In App Message Modules to Native References
Full Changelog: 5.0.1...5.0.2
Release 5.0.1
🐛 Bug Fixes
- Fix iOS Builds by updating Native Reference linking Add Location and In App Message Modules to Native References
Native SDK Updates
Full Changelog: 5.0.0...5.0.1
Release 5.0.0
⚠️ This is a major release which contains breaking API changes.
In this major version release for the OneSignal React Native SDK, we are making a significant shift from a device-centered model to a user-centered model. A user-centered model allows for more powerful omni-channel integrations within the OneSignal platform.
For information please see the migration guide.
Note that Identity Verification has not yet been enabled in this version and will be released in a later version
What's Changed Since beta-03
API Updates
Notifications.RequestPermission
has been renamed toNotifications.RequestPermissionAsync
Location.RequestPermissionAsync
has been renamed toLocation.RequestPermission
and returns void
Native Updates
Updated included Android SDK to 5.0.0
Updated included iOS SDK to 5.0.1
Full Changelog: 5.0.0-beta03...5.0.0