10.0.0

Breaking changes

• Support new option to prevent login with unverified identifier after a signup. Method signup returns a SignupFlow that can be an AchievedLogin(authToken: AuthToken) or an AwaitingIdentifierVerification

New Features

• support parameter origin to requestPasswordReset
• allow to trust device during mfa credential registering
• support action parameter for step up and mfa credential registering

9.1.2

Bug fix

Achieve step up in login webview by clicking on link received by email

9.1.1

Improve the handling of the web session

9.1.0

New features

• add new logout options for revoking tokens and browser cookies

9.0.0

Breaking changes

• Use Swift's native concurrency model instead of Futures. See the migration guide at https://developer.reachfive.com/sdk-ios/guides/migrate-futures.html
• New SDK Reach5Future to enable a gradual migration. See the use guide at https://developer.reachfive.com/sdk-ios/guides/migrate-reach5future.html

New features

• New option to view the network activity as logs in the console. This can be enabled by setting the loggingEnabled property of the new SdkInternalConfig to true.

Other changes

• The other dependencies have also been removed, notably Alamofire. The SDK now uses the native URLSession for all network calls.

8.2.0

New features

• Add method sendEmailVerification and verifyEmail to verify email identifier

8.1.0

New features

• Support retrieving nested custom fields when using getProfile

8.0.0

New features

Breaking changes

• Allow to initiate an mfa step up when required during a call to loginWithPassword and login(withRequest:usingModalAuthorizationFor:display:) (when .Password is used).
  For that the return type of these methods were changed from AuthToken to a new type LoginFlow to represent the potential new MFA step up introduced.
• Change the name of StartStepUp to StartStepUp.AuthTokenFlow and make its authToken parameter mandatory
• Some method will see their returned error type change from .TechnicalError to .AuthFailure or .RequestError, and will now come with an ApiError containing the details of the error.

7.2.0

New features

• Add a new method updateProfile(authToken:profileUpdate:) to be able to update and delete fields from the user profile

7.1.5

Fixes

• Make an internal method visible to providers
• Better error message in technical errors