PowerAuth upgrade

Cartfile

@@ -1 +1 @@
-github "wultra/networking-apple" "1.4.0"
+github "wultra/networking-apple" "release/1.5.x"

Cartfile.resolved

@@ -1,3 +1,3 @@
-binary "https://raw.githubusercontent.com/wultra/powerauth-mobile-sdk-spm/1.8.0/PowerAuth2.json" "1.8.0"
-binary "https://raw.githubusercontent.com/wultra/powerauth-mobile-sdk-spm/1.8.0/PowerAuthCore.json" "1.8.0"
-github "wultra/networking-apple" "1.4.0"
+binary "https://raw.githubusercontent.com/wultra/powerauth-mobile-sdk-spm/1.9.0/PowerAuth2.json" "1.9.0"
+binary "https://raw.githubusercontent.com/wultra/powerauth-mobile-sdk-spm/1.9.0/PowerAuthCore.json" "1.9.0"
+github "wultra/networking-apple" "b1f9c2f328c4857407499786c334ccd0f764d7d9"

Deploy/WultraMobileTokenSDK.podspec

@@ -18,8 +18,8 @@ Pod::Spec.new do |s|
  # 'Common' subspec
  s.subspec 'Common' do |sub|
  sub.source_files = 'WultraMobileTokenSDK/Common/**/*.swift'
- sub.dependency 'PowerAuth2', '~> 1.8.0'
- sub.dependency 'WultraPowerAuthNetworking', '~> 1.4.0'
+ sub.dependency 'PowerAuth2', '~> 1.9.0'
+ sub.dependency 'WultraPowerAuthNetworking', '~> 1.5.0'
  end
 
  # 'Operations' subspec

Package.swift

@@ -11,8 +11,8 @@ let package = Package(
  .library(name: "WultraMobileTokenSDK", targets: ["WultraMobileTokenSDK"])
  ],
  dependencies: [
- .package(url: "https:/wultra/powerauth-mobile-sdk-spm.git", .upToNextMinor(from: "1.8.0")),
- .package(url: "https:/wultra/networking-apple.git", .upToNextMinor(from: "1.4.0"))
+ .package(url: "https:/wultra/powerauth-mobile-sdk-spm.git", .upToNextMinor(from: "1.9.0")),
+ .package(url: "https:/wultra/networking-apple.git", .upToNextMinor(from: "1.5.0"))
  ],
  targets: [
  .target(

README.md

@@ -20,13 +20,13 @@ __Wultra Mobile Token SDK__ is a high-level SDK for operation approval.
 <img align="right" src="docs/images/il-mobile-token.svg" width="40%" />
 <!-- end -->
 
-With Wultra Mobile Token (WMT) SDK, you can integrate an out-of-band operation approval into an existing mobile app, instead of using a standalone mobile token application. WMT is built on top of [PowerAuth Mobile SDK](https:/wultra/powerauth-mobile-sdk). It communicates with the "Mobile Token REST API" and "Mobile Push Registration API". Individual endpoints are described in the [PowerAuth Webflow documentation](https://github.com/wultra/powerauth-webflow/).
+With Wultra Mobile Token (WMT) SDK, you can integrate an out-of-band operation approval into an existing mobile app, instead of using a standalone mobile token application. WMT is built on top of [PowerAuth Mobile SDK](https:/wultra/powerauth-mobile-sdk). It communicates with the [Mobile Token API](https://developers.wultra.com/components/enrollment-server/develop/documentation/Mobile-Token-API).
 
 To understand the Wultra Mobile Token SDK purpose on a business level better, you can visit our own [Mobile Token application](https://www.wultra.com/mobile-token). We use Wultra Mobile Token SDK in our mobile token application as well.
 
 WMT SDK library does precisely this:
 
-- Retrieves the list of operations that are pending for approval for a given user.
+- Retrieves the list of operations that are pending approval for a given user.
 - Approves or rejects operations with PowerAuth transaction signing.
 - Registers an existing PowerAuth activation to receive push notifications.
 

WultraMobileTokenSDK.podspec

@@ -18,8 +18,8 @@ Pod::Spec.new do |s|
  # 'Common' subspec
  s.subspec 'Common' do |sub|
  sub.source_files = 'WultraMobileTokenSDK/Common/**/*.swift'
- sub.dependency 'PowerAuth2', '~> 1.8.0'
- sub.dependency 'WultraPowerAuthNetworking', '~> 1.4.0'
+ sub.dependency 'PowerAuth2', '~> 1.9.0'
+ sub.dependency 'WultraPowerAuthNetworking', '~> 1.5.0'
  end
 
  # 'Operations' subspec

docs/Changelog.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## 1.12.0 (October 2024)
+
+- PowerAuth "server stack" `1.9+` is now required
+- Dependency `powerauth-mobile-sdk` is now required in version `1.9.x`
+- Dependency `networking-apple` is now required in version `1.5.x`
+
 ## 1.11.1 (July 2024)
 
 - Dependency `networking-apple` is now required in version `1.4.x`

docs/Readme.md

@@ -1,12 +1,12 @@
 # Wultra Mobile Token SDK for iOS
 
-With Wultra Mobile Token (WMT) SDK, you can integrate an out-of-band operation approval into an existing mobile app, instead of using a standalone mobile token application. WMT is built on top of [PowerAuth Mobile SDK](https:/wultra/powerauth-mobile-sdk). It communicates with the "Mobile Token REST API" and "Mobile Push Registration API". Individual endpoints are described in the [PowerAuth Webflow documentation](https://github.com/wultra/powerauth-webflow/).
+With Wultra Mobile Token (WMT) SDK, you can integrate an out-of-band operation approval into an existing mobile app, instead of using a standalone mobile token application. WMT is built on top of [PowerAuth Mobile SDK](https:/wultra/powerauth-mobile-sdk). It communicates with the [Mobile Token API](https://developers.wultra.com/components/enrollment-server/develop/documentation/Mobile-Token-API).
 
 To understand the Wultra Mobile Token SDK purpose on a business level better, you can visit our own [Mobile Token application](https://www.wultra.com/mobile-token). We use Wultra Mobile Token SDK in our mobile token application as well.
 
 WMT SDK library does precisely this:
 
-- Retrieves the list of operations that are pending for approval for a given user.
+- Retrieves the list of operations that are pending approval for a given user.
 - Approves or rejects operations with PowerAuth transaction signing.
 - Registers an existing PowerAuth activation to receive push notifications.
 

docs/Using-Inbox-Service.md

@@ -19,6 +19,8 @@ Inbox Service is responsible for managing messages in the Inbox. The inbox is a
 Note: Before using Inbox Service, you need to have a `PowerAuthSDK` object available and initialized with a valid activation. Without a valid PowerAuth activation, the service will return an error.
 <!-- end -->
 
+Inbox Service communicates with the [Mobile Token API](https://developers.wultra.com/components/enrollment-server/develop/documentation/Mobile-Token-API).
+
 ## Creating an Instance
 
 ### On Top of the `PowerAuthSDK` instance

docs/Using-Operations-Service.md

@@ -29,7 +29,7 @@ An operation can be anything you need to be approved or rejected by the user. It
 Note: Before using Operations Service, you need to have a `PowerAuthSDK` object available and initialized with a valid activation. Without a valid PowerAuth activation, all endpoints will return an error
 <!-- end -->
 
-Operations Service communicates with a backend via [Mobile Token API endpoints](https://github.com/wultra/powerauth-webflow/blob/develop/docs/Mobile-Token-API.md).
+Operations Service communicates with the [Mobile Token API](https://developers.wultra.com/components/enrollment-server/develop/documentation/Mobile-Token-API).
 
 ## Creating an Instance
 
@@ -745,10 +745,10 @@ public struct WMTPACData: Decodable {
 - two methods are provided:
  - `parseDeeplink(url: URL) -> WMTPACData?` - URI is expected to be in the format `scheme://code=$JWT` or `scheme://operation?oid=5b753d0d-d59a-49b7-bec4-eae258566dbb&potp=12345678`
  - `parseQRCode(code: String) -> WMTPACData?` - code is to be expected in the same format as deeplink formats or as a plain JWT
- - mentioned JWT should be in the format `{“typ”:”JWT”, “alg”:”none”}.{“oid”:”5b753d0d-d59a-49b7-bec4-eae258566dbb”, “potp”:”12345678”} `
+ - mentioned JWT should be in the format `{"type":"JWT", "alg":"none"}.{"oid":"5b753d0d-d59a-49b7-bec4-eae258566dbb", "potp":"12345678"} `
 
 - Accepted formats:
- - notice that totp key in JWT and in query shall be `potp`!
+ - notice that the totp key in JWT and query shall be `potp`!
 
 ## Error handling
 

docs/Using-Push-Service.md

@@ -17,7 +17,7 @@ Push Service is responsible for registering the device for the push notification
 Note: Before using Push Service, you need to have a `PowerAuthSDK` object available and initialized with a valid activation. Without a valid PowerAuth activation, the service will return an error
 <!-- end -->
 
-Push Service communicates with [Mobile Push Registration API](https://github.com/wultra/powerauth-webflow/blob/develop/docs/Mobile-Push-Registration-API.md).
+Push Service communicates with the [Mobile Token API](https://developers.wultra.com/components/enrollment-server/develop/documentation/Mobile-Token-API).
 
 ## Creating an Instance
 

scripts/cart-update.sh

@@ -5,5 +5,5 @@ set -e # stop sript when error occures
 SCRIPT_FOLDER=$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )
 
 pushd "${SCRIPT_FOLDER}/.."
-carthage bootstrap --use-xcframeworks --use-submodules --platform ios --configuration Debug
+carthage update --use-xcframeworks --use-submodules --platform ios --configuration Debug
 popd