Merge pull request #662 from wultra/feature/650-remove-recovery-codes

* Core: Remove support for recovery codes. Fix #650 Fix #640
* iOS: Remove recovery codes support
* Android: Remove recovery codes support
* Android: Fixed various lint warnings
* docs: Added 1.10 and 2.0 migration guides
* build: Fixed not-supported macOS platform in build pipeline
* docs: Activation data sharing in one place. Fix #628
* docs: Remove iOS App Extensions documentation. Fix #632
* Deprecate unsafeChangePassword() methods. Fix #530

.github/workflows/build.yml

@@ -13,7 +13,7 @@ on:
 jobs:
   build:
     name: Build
-    runs-on: macos-12
+    runs-on: macos-15
     steps:
       - name: Checkout the repo
         uses: actions/checkout@v3

README.md

@@ -5,7 +5,6 @@ In order to connect to the [PowerAuth](https://www.wultra.com/product/powerauth-
 ## Integration Tutorials
 
 - [PowerAuth SDK for iOS and tvOS Apps](./docs/PowerAuth-SDK-for-iOS.md)
-- [PowerAuth SDK for iOS and tvOS Extensions](./docs/PowerAuth-SDK-for-iOS-Extensions.md)
 - [PowerAuth SDK for watchOS](./docs/PowerAuth-SDK-for-watchOS.md)
 - [PowerAuth SDK for Android Apps](./docs/PowerAuth-SDK-for-Android.md)
 

docs/Migration-from-1.10-to-2.0.md

@@ -0,0 +1,43 @@
+# Migration from 1.10.x to 2.0.x
+
+PowerAuth Mobile SDK in version `2.0.0` provides the following improvements:
+
+- TBA
+
+### Compatibility with PowerAuth Server
+
+- This release is fully compatible with PowerAuth Server version `2.0.0` and newer.
+
+## Android
+
+### API changes
+
+- Removed all interfaces deprecated in release `1.10.x`
+
+### Other changes
+
+- TBA
+
+## iOS & tvOS
+
+### API changes
+
+- Removed all interfaces deprecated in release `1.10.x`
+
+### Other changes
+
+- TBA
+
+## iOS & tvOS App Extensions
+
+- Removed all interfaces deprecated in release `1.10.x`
+
+## Known Bugs
+
+The PowerAuth SDKs for iOS and tvOS App Extensions, as well as for watchOS, do not use time synchronized with the server for token-based authentication. To avoid any compatibility issues with the server, the authentication headers generated in your App Extension or on watchOS still use the older protocol version 3.1. This issue will be fixed in a future SDK update.
+
+You can watch the following related issues:
+
+- [wultra/powerauth-mobile-sdk#551](https://github.com/wultra/powerauth-mobile-sdk/issues/551)
+- [wultra/powerauth-mobile-watch-sdk#7](https://github.com/wultra/powerauth-mobile-watch-sdk/issues/7)
+- [wultra/powerauth-mobile-extensions-sdk#7](https://github.com/wultra/powerauth-mobile-extensions-sdk/issues/7)

docs/Migration-from-1.9-to-1.10.md

@@ -0,0 +1,84 @@
+# Migration from 1.9.x to 1.10.x
+
+PowerAuth Mobile SDK in version `1.10.0` provides the following improvements:
+
+- Removed support of activation by recovery code.
+
+
+### Compatibility with PowerAuth Server
+
+- This release is fully compatible with PowerAuth Server version `1.9.0` and newer.
+
+## Android
+
+### API changes
+
+- The following methods in `PowerAuthSDK` class are deprecated:
+  - `changePasswordUnsafe()` - use asynchronous `changePassword()` as a replacement.
+
+- Due to removed support of recovery codes, the following classes and methods are no longer available:
+  - Methods removed in `PowerAuthSDK`:
+    - `createRecoveryActivation()`
+    - `hasActivationRecoveryData()`
+    - `getActivationRecoveryData()`
+    - `confirmRecoveryCode()`
+  - Methods removed in `PowerAuthActivation.Builder`:
+    - all variants of `recoveryActivation()`
+  - Methods removed in `ActivationCodeUtil`:
+    - `parseFromRecoveryCode()`
+    - `validateRecoveryCode()`
+    - `validateRecoveryPuk()`
+  - Other removed methods:
+    - `CreateActivationResult.getRecoveryData()`
+    - `ErrorResponseApiException.getCurrentRecoveryPukIndex()`
+  - Removed classes and interfaces:
+    - `IGetRecoveryDataListener`
+    - `IConfirmRecoveryCodeListener`
+    - `RecoveryData`
+
+- Removed all interfaces deprecated in release `1.9.x`
+
+### Other changes
+
+- TBA
+
+## iOS & tvOS
+
+### API changes
+
+- The following methods in `PowerAuthSDK` class are deprecated:
+  - `unsafeChangePassword(from:to:)` - use asynchronous `changePassword(from:to:callback:)` as a replacement.
+
+- Due to removed support of recovery codes, the following classes and methods are no longer available:
+  - Methods removed in `PowerAuthSDK`:
+    - `createActivation(withName:recoveryCode:recoveryPuk:extras:callback:)`
+    - `hasActivationRecoveryData()`
+    - `activationRecoveryData(authentication:callback:)`
+    - `confirm(recoveryCode:, authentication:callback:)`
+  - Methods removed in `PowerAuthActivationCodeUtil`:
+    - `validateRecoveryCode()`
+    - `validateRecoveryPuk()`
+    - `parseFromRecoveryCode()`
+  - Other changes:
+    - removed class `PowerAuthActivationRecoveryData`
+    - removed property `PowerAuthActivationResult.activationRecovery`
+    - removed constructor `PowerAuthActivation(recoveryCode:recoveryPuk:name:)`
+
+- Removed all interfaces deprecated in release `1.9.x`
+
+### Other changes
+
+- TBA
+
+## iOS & tvOS App Extensions
+
+- The `PowerAuth2ForExtensions` library is now deprecated and no longer supported and maintained. You can use full feature PowerAuth mobile SDK as a replacement in your app extension.
+
+## Known Bugs
+
+The PowerAuth SDKs for watchOS, do not use time synchronized with the server for token-based authentication. To avoid any compatibility issues with the server, the authentication headers generated in your App Extension or on watchOS still use the older protocol version 3.1. This issue will be fixed in a future SDK update.
+
+You can watch the following related issues:
+
+- [wultra/powerauth-mobile-sdk#551](https://github.com/wultra/powerauth-mobile-sdk/issues/551)
+- [wultra/powerauth-mobile-watch-sdk#7](https://github.com/wultra/powerauth-mobile-watch-sdk/issues/7)