Skip to content

Releases: OneSignal/OneSignal-iOS-SDK

Release 3.11.0

06 May 19:02
f23db94
Compare
Choose a tag to compare

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

18 Apr 18:51
ade86d7
Compare
Choose a tag to compare

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

12 Apr 21:14
Compare
Choose a tag to compare
3.11.0 Beta Pre-release
Pre-release

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

22 Mar 21:42
0348dd1
Compare
Choose a tag to compare

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

10 Mar 16:50
Compare
Choose a tag to compare
Pre-release

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

Release 3.10.1

08 Feb 23:42
30e2622
Compare
Choose a tag to compare

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

3.10.0 Release

14 Dec 23:56
0be72c7
Compare
Choose a tag to compare

Fixing crash when failing to download notification images

  • This PR prevents crashes due to failures when writing downloaded notification attachments (images) to a temporary file location. #1029 and #1030

Adding CollapseId to the OSNotification object

  • OneSignal's CollapseId which is shared with Android corresponds to the identifier property of iOS notifications. If the collapseId field is present on your notifications it can now be read in the corresponding OSNotification object. #1024

3.9.1 Release

16 Nov 20:02
85920cd
Compare
Choose a tag to compare

This fix release adds back arm64 simulator and maccatalyst architectures the OneSignalXCFramework

3.9.0 Release

12 Nov 19:32
2df1960
Compare
Choose a tag to compare

Fullbleed In App Messaging

  • Fullscreen In App Messages can now be set to not use a margin allowing them to fill the entire phone screen. Content is adjusted for the phones safe area insets. #1018

Allow slashes in externalUserIds

  • Slashes were previously incorrectly escaped from setExternalUserID calls. #1015

Fixing drag behavior of In App Message Carousels

  • Fixing carousels having drag to dismiss enabled which made the swipe behavior inconsistent. #1019

2.16.7 Release

06 Oct 20:33
d53c1ee
Compare
Choose a tag to compare

Fixes

  • In App Messaging now respects device orientation locks for Unity Applications #1000