Skip to main content
Version: 4.3.x.x RR (Android, iOS) / 4.4.x.x RR (Flutter, React Native)

Requirements

The topic lists the minimum requirements that the mobile application, as well as the devices integrating the Nevis Mobile Authentication SDK need to meet.

We first show you what is required for the development phase of the mobile application, then what changes you need to make to move from the development phase to the phase where the mobile application is prepared for a production release.

The SDK has to be compatible with the version deployed in the Nevis Mobile Authentication backend.

Mobile device requirements

The following prerequisites have to be met by any mobile device to run an application integrating the Nevis Mobile SDK:

  1. The client device has to fulfill the minimum OS requirements listed for the individual platforms.
  2. The SDK requires the presence of the following:
  3. A device locking mechanism has to be in place.
  4. The device is not to be rooted or jailbroken.

Nevis backend requirements

  • Customer Authentication Cloud: Fully supported.
  • Nevis Software Delivered / Identity Suite: Requires the nevisFIDO component version 1.11.0 or later, which applies to nevisAppliance versions 2.202102.x or later, as well as the LTS21 release.

Networking/TLS requirements

The usage of self-signed certificates or cleartext non-HTTPS traffic is not supported, trusted Root-CA signed certificates are required. One of the reasons are strict requirements imposed by Apple regarding trusted TLS certificates.

Self-signed certificate usage for development and testing

The debug flavor of the SDK is more "lenient" and allows the usage of self-signed certificates in the networking layer. For more information, see chapter on Security Consideration.

Supported platforms

The Nevis Mobile Authentication SDK supports Android and iOS. Cross-platform support is available through React Native and Flutter plugins.

Unsupported Android-based and non-Android platforms

HarmonyOS Next is a completely new operating system that is no longer based on Android. Applications built with the Nevis Mobile Authentication SDK cannot run on HarmonyOS Next. While earlier versions of Huawei's HarmonyOS were Android-based and could run apps integrating the SDK, HarmonyOS Next is an entirely different platform. There are no plans to support it at this time.

Custom and open-source Android ROMs such as GrapheneOS, LineageOS, CalyxOS, /e/OS, and similar community-driven operating systems are not supported. The hardening framework used by the SDK may detect these devices as rooted, preventing the SDK from functioning. This applies to any operating system that was not shipped with the device. See Known Issues for details and possible workarounds.

Software requirements

  • Android 7 or later, with API level 24
  • Android 10 or later, with API level 29, for the biometric authenticator to work
  • Android 11 or later, with API level 30, for the device passcode authenticator to work
  • Android Studio 3.5.1 or later
  • OpenJDK 17 or later
  • Gradle 8.7 or later
  • Android Gradle Plugin 8.6.0 or later
  • Application has to be composed of a root module, and a single application module
  • android.permission.USE_BIOMETRIC and android.permission.USE_FINGERPRINT permissions