Releases: ReachFive/identity-ios-sdk
Releases · ReachFive/identity-ios-sdk
6.3.0
New features
-
add MfA credentials support methods:
- mfaListCredentials, mfaStart, mfaVerify, mfaDeleteCredential
-
add MFA step up support methods:
- mfaStart, mfaVerify
Bug fixes
- Fix a bug where the provided scope parameter was not transmitted to the backend in
webviewLogin
- Allow the Sandbox app to run in the ARM iPhone simulator
6.2.0
New features
- Add privacy manifest.
Bug fix
- Fix a crash when calling
webviewLogin
in quick succession
Dependencies
- Updated Facebook from 16.2 to 17.0
6.1.0
6.0.0
New features
- New module IdentitySdkWeChat for native WeChat Login integration
- Add optional
origin
parameters to most authentification functions to help categorize your inbound traffic
Bug fix
- Fix passwordless flow with email
Breaking changes
- The functionality of module
IdentitySdkWebView
has been integrated into the mainIdentitySdkCore
module. ThereforeIdentitySdkWebView
has been deprecated. - The
origin
parameter inNativeLoginRequest
,NewPasskeyRequest
,PasskeySignupRequest
has changed meaning.- Up to now it meant the origin of the webauthn call. There is a new parameter
originWebAuthn
for this - Now
origin
has the same meaning as in all other authentification functions: to help categorize your inbound traffic
- Up to now it meant the origin of the webauthn call. There is a new parameter
- Add a new method in
Provider
andReachFive
:application(_:continue:restorationHandler:)
to handle universal links - Remove an obsolete method in
Provider
andReachFive
:application(_:open:sourceApplication:annotation:)
- New required property
GIDClientID
in property list to use Google SignIn loadLoginWebview(reachfive:state:nonce:scope:origin:)
now returns aFuture
and instead of taking aPromise
as argumentPasskeySignupRequest
now has its first parameter renamed frompasskeyPofile
topasskeyProfile
Dependencies
- New dependency in Core: DeviceKit
- Updated GoogleSignIn from 6 to 7
- Updated Facebook from 14.1 to 16.2
- Updated Alamofire to 5.8
- Updated CryptoSwift to 1.8
5.8.0
New features
- Support for Passkey in iOS 16 and up:
- Signup and login are supported in various UI modes
- Registering a new passkey on an exiting profile (with or without preexisting passkeys)
- List all passkeys associated to a profile
- Delete a passkey
- Support for native modal UI to automatically present password credentials
Demo App
Vastly improved demo app:
- Features a new tab bar navigation UI for easy access to the main demo, profile page and individual functions
- Demo tab that features login and signup using password or passkey
- Profile tab with more profile info, list of passkeys, and buttons to register passkey, change phone number or password
- Access every passkey UI mode individually
- Introducing Mac Catalyst support to easily launch the app outside a simulator on a real Mac device
- Better iPad support
- Support for Dark Mode
Other changes
- Improved error messages when using the
message()
function or when printing to the console - Update the Readme with instructions on configuring and running the demo app
5.7.2
New features
- Allow login with webview using a
WKWebview
. - Add new address complement field in the
ProfileAddress
model
5.7.1
New features
- Allow login with password using a custom identifier instead of an email or phone number.
Other changes
- Update dependency
GoogleSignIn
from 6.2.2 to 6.2.4
5.7.0
⚠️ Breaking changes ⚠️
- The SDK mandates a minimum version of iOS 13
loginWithPassword
takes either anemail
or aphoneNumber
instead of ausername
- New method
Provider.application(_:didFinishLaunchingWithOptions:)
to call at startup to initialize the social providers - New required key
FacebookClientToken
to configure Facebook Login - Parameter
viewController
inProvider.login(scope:origin:viewController:)
is now mandatory - Parameter
viewController
inProvider.login(scope:origin:viewController:)
must also conform to the protocolASWebAuthenticationPresentationContextProviding
when usingWebViewProvider
- Some error messages may have changed
New features
- Login using a webview:
AppDelegate.reachfive().webviewLogin
WebViewProvider
now usesASWebAuthenticationSession
instead ofSFSafariViewController
for better security. The associated webview UI is different.- Don't ask again to confirm app access for Facebook Login when a user still has a valid Access Token
Other changes
loginWithPassword
calls/identity/v1/password/login
instead of/oauth/token
- Update dependency
Alamofire
from 5.6.1 to 5.6.2 - Update dependency
BrightFutures
from 8.1.0 to 8.2.0 - Update dependency
CryptoSwift
from 1.3.8 to 1.5.1 - Update dependency
FBSDKCoreKit
from 9.0.0 to 14.1.0 - Update dependency
FBSDKLoginKit
from 9.0.0 to 14.1.0 - Update dependency
GoogleSignIn
from 5.0.2 to 6.2.2 - Remove dependencies
EllipticCurveKeyPair
,KeychainAccess
,PromiseKit
,FacebookCore
,FacebookLogin
5.6.2
Remove a dependency that relied on Swift 4 :
- Remove
WebAuthnKit
5.6.1
- Update
WebAuthnKit
to 0.9.6