Releases: OneSignal/OneSignal-XCFramework
Release 3.12.5
🚀 Features
- Enable push notifications for iOS simulators (OneSignal/OneSignal-iOS-SDK#1244)
🐛 Bug Fixes
- Fix Crash for In App Message clicks with no id (OneSignal/OneSignal-iOS-SDK#1248)
- Fix tracking influenced opens in firebase (OneSignal/OneSignal-iOS-SDK#1241)
Release 3.12.4
🐛 Bug Fixes
- Fix In App Messages occasionally being displayed twice (OneSignal/OneSignal-iOS-SDK#1233)
- Fix a OneSignal log ignoring the "None" log level (OneSignal/OneSignal-iOS-SDK#1219)
Release 5.0.0-beta-02
🚧 Beta release. 🚧
In this major version beta release for the OneSignal 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.
🐛 Bug Fixes
- Fixes to detection native permission changes in OneSignal/OneSignal-iOS-SDK#1229
Release 5.0.0-beta-01
🚧 Beta release. 🚧
In this major version beta release for the OneSignal 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.
Release 5.0.0-alpha-02
🚧 Alpha release. It is not recommended to use in production. 🚧
🚀 Features
- Live Activity support on 5.0.0 in OneSignal/OneSignal-iOS-SDK#1189
🐛 Bug Fixes
- Fix a bug in identifying a user in OneSignal/OneSignal-iOS-SDK#1210
- Fix a bug in firing the push subscription observer in OneSignal/OneSignal-iOS-SDK#1211
Please see migration guide here.
Release 5.0.0-alpha-01
In this major version alpha release for the OneSignal 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.
Find our migration guide here
Test release 5.0.0
This is a test release
Release 3.12.3
Check if app_id is in url path
app_id must be included with each request. In order to reduce load on the server we fail requests early on the client that we know will fail on the server. Currently the check in OneSignalRequest looks for app_id in the body as a param. However there is another valid way to send the app_id that is after "/apps" in the path".
PRs included in this release
OneSignal/OneSignal-iOS-SDK#1163
OneSignal/OneSignal-iOS-SDK#1162
OneSignal/OneSignal-iOS-SDK#1161
Release 3.12.2
Encode activity_id
Since activity_id is customer generated and shows up in the path to enter or exit a live activity it must be encoded.