Skip to content

Releases: OneSignal/OneSignal-iOS-SDK

Release 3.12.1

17 Nov 23:24
ddc14cc
Compare
Choose a tag to compare

Adding device type to Live Activity API call + fixing internal version issue

PRs included in this release

#1155

Release 3.12.0

16 Nov 23:36
8c34107
Compare
Choose a tag to compare

Adding Live Activity Support

Added two public methods

  • enterLiveActivity
  • exitLiveActivity
    These public methods make API calls and associate an activityId with 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

#1150
#1152

Release 3.11.5

07 Nov 22:53
45fc864
Compare
Choose a tag to compare

Releasing 3.11.5 to fix checksum issues in 3.11.4

PRs included in this release

None

Release 3.11.4

28 Oct 21:42
4650809
Compare
Choose a tag to compare

Releasing the SDK using Xcode 13 build tools and re-including 32 bit architectures

  • PR #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

#1134

Release 3.11.3

17 Oct 20:03
d0c87a6
Compare
Choose a tag to compare

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. #1131

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. #1132

PRs included in this release

#1120
#1121
#1122
#1131
#1132

Release 3.11.2

16 Jun 17:11
9e27413
Compare
Choose a tag to compare

Swizzling fixes

Rework to OneSignal's swizzling which addresses:

  • Fixes compatibility with Swift projects that use UIApplicationDelegateAdaptor (fixes #1045 & #1069)
  • Fixes app startup issues:
  • Some instances of the “Apns Delegate Never Fired” error related to compatibility with other SDKs that use the AppDelegate:
    • Multiple classes that implement UIApplicationDelegate
    • Class that inherits from a class that implements UIApplicationDelegate but never calls super.
  • other potential compatibility issues

PRs included in this release

#1103
#1102
#1101
#1100
#1099
#1094
#1097
#1091
#1090
#1089

Release 3.11.1

12 May 17:36
8e4e32f
Compare
Choose a tag to compare

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

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"