0.16.2 Android + iOS

Common changes

In previous build we promised a reset() method to be removed, but this unfortunately didn't go very well, so we're finally removing that method now. At first, let me explain some reasons why we wanted to remove the method at all.

We had a several problems with an oldreset implementation:

• The naming of the method was not very descriptive. I would expect that reset will also reset the persisted data.
• The reset just reseted an internal object, without taking a care about the rest of the SDK object. This might lead to inconsistent states between the persisted data and the in-memory SDK object.
• We were forcing developers to reset the SDK object in many situations, like as response for the error, during the activation, or before the starting of the activation process. This one particular subject we also addressed in this new build.

How to migrate

1. You have to just replace reset() with a brand new removeActivationLocal() method. The new method also guarantees that the underlying storage is also properly wiped out.
2. You don't need to "reset" the SDK instance when an error occurs, during the activation process. The new createActivation* implementation guarantees that SDK object ends in "empty" state when the activation fails. You need to start a new activation process in this situation.
3. removeActivationLocal() should work in all situations. The method doesn't check the state of the activation (so you can call it also when there's no activation).
4. Known bug: removeActivationLocal() doesn't cancel a pending asynchronous task. You should not call the method when the SDK object is communicating with the server. This problem will be resolved in some future release of the library.

Android

• Added PowerAuthSDK.removeActivationLocal(Context context, boolean removeSharedBiometryKey) method which gives you a chance to do not remove a shared biometry key.
  • This addition is useful only for applications using multiple SDK instances at the same time. We're internally sharing the biometry key between these instances and thus this kind of control is required. It is recommended to remove the key together with removing the last local activation.

0.16.1 Android + iOS

Common changes

• OpenSSL updated to 1.0.2l (no vulnerabilities reported)
• Improved internal data format compatibility with prehistoric PowerAuth versions. This change doesn't affect library functionality, but allows better migration from (very) old PowerAuth implementations.

Android changes

• ⚠️ Removed PowerAuthSDK.reset() method
• Added PowerAuthSDK.removeActivationLocal() method for removing local activation data
• Improved state validations in PowerAuthSDK methods. This is in general prevention against misuse of public API.
• FingerprintAuthenticationDialogFragment can be cancelled by pressing back button

IOS changes

• ⚠️ Removed PowerAuthSDK.reset() method
• ⚠️ Removed PowerAuthSDK.clearActivationDataKeychain() method
• Added PowerAuthSDK.removeActivationLocal() method for removing local activation data
• PowerAuthSDK.fetchActivationStatus now returns nullable status object in callback

0.16.0 - Android + IOS

Android changes

• Fixed multiple issues in HTTP response processing
• Now it's possible to connect to development servers over plain HTTP connection
• Now you can turn on HTTP request & response debug logging by calling PA2Log.setEnabled(true)
• Added support for "offline signatures"

IOS changes

• Added support for "offline signatures"

First jcenter release

Summary

This release brings an easy integration with jcenter repository

Android changes

• io.getlime.security:powerauth-restful-model upgraded to 0.15.0

IOS changes

This build has no changes for IOS codebase

First CocoaPods release

Summary

This release brings an easy integration with CocoaPods packaging