Initialization

All the functionalities of the Nevis Mobile Authentication SDK are accessible through the MobileAuthenticationClient _{java, swift, objc, flutter, react native} interface of the SDK.

Creating a MobileAuthenticationClient can be time-consuming when your application runs in slow devices. We recommend creating a single instance of MobileAuthenticationClient and reusing it to execute multiple operations.

caution

On iOS platform do not block the main thread during SDK initialization, as this can lead to UI unresponsiveness or deadlocks. The initialization process may need to dispatch work to the main thread in certain scenarios. Avoid using blocking techniques such as DispatchSemaphore or DispatchGroup's wait() method on the main thread.

To create a MobileAuthenticationClient, use the MobileAuthenticationClientInitializer _{java, swift, objc, flutter, react native} as described in the following code example:

Android/Kotlin

Initialization

Android/Java

Initialization

iOS/Swift

Initialization

iOS/Objective-C

Initialization

Flutter/Dart

Initialization

React Native/TypeScript

Initialization