Skip to content

6.3.0

Latest
Latest

Choose a tag to compare

View all tags
@PushwooshCI PushwooshCI released this 28 Oct 11:50
6.3.0
5b89aef

Breaking Changes

  • iOS: projects that got the native SDK through CocoaPods or External Dependency Manager (EDM4U) switch to Swift Package Manager on update, and Xcode needs access to github.com to resolve the package. To keep the previous setup, select CocoaPods in Window > Pushwoosh SDK Setup

New Features

  • iOS: the native SDK comes from the Swift package Pushwoosh-XCFramework by default, without CocoaPods and without EDM4U. It needs Unity 2021.3.15 or later and Target minimum iOS Version 15.0 or later
  • iOS: Window > Pushwoosh SDK Setup chooses where the iOS SDK comes from (Swift Package Manager or CocoaPods) and adds optional modules with Swift Package Manager: PushwooshLiveActivities, PushwooshInboxKit, PushwooshInApp, PushwooshVoIP, PushwooshForegroundPush, PushwooshKeychain, PushwooshGRPC and PushwooshGeozones

Improvements

  • iOS: the export stays on CocoaPods and the console says why when the project already has a PushwooshXCFramework pod (in a *Dependencies.xml read by EDM4U or in the Podfile), when the Unity version has no Swift package API, or when Target minimum iOS Version is below 15.0
  • iOS: the Swift Package Manager export keeps Unity-iPhone.xcworkspace, so build scripts that use the workspace keep working without CocoaPods
  • iOS: an export with Swift Package Manager into the folder of a previous CocoaPods export takes PushwooshXCFramework out of the Podfile and Pods, with EDM4U too, so the app does not get the iOS SDK twice

Bug Fixes

  • iOS: an empty Application Code no longer crashes the app: the SDK logs an error and stays uninitialized
  • iOS: an Append build reapplies the push entitlements instead of stopping with an IOException on Entitlements.plist
Assets 4
Loading