### React Native
Module packages are installed from the root of your React Native project, alongside the core package. Each module must be installed together with its peer dependencies:
| Module package | Peer dependencies to install alongside it |
| ---------------------------------------------------------- | ----------------------------------------- |
| `@entrust.corporation/idvsdk-reactnative-welcome` | `@entrust.corporation/idvsdk-reactnative` |
| `@entrust.corporation/idvsdk-reactnative-document` | `@entrust.corporation/idvsdk-reactnative`, `@entrust.corporation/idvsdk-reactnative-device-security` |
| `@entrust.corporation/idvsdk-reactnative-nfc` | `@entrust.corporation/idvsdk-reactnative`, `@entrust.corporation/idvsdk-reactnative-device-security` |
| `@entrust.corporation/idvsdk-reactnative-face-photo` | `@entrust.corporation/idvsdk-reactnative`, `@entrust.corporation/idvsdk-reactnative-device-security`, `@entrust.corporation/idvsdk-reactnative-analytics-events-face` |
| `@entrust.corporation/idvsdk-reactnative-face-motion` | `@entrust.corporation/idvsdk-reactnative`, `@entrust.corporation/idvsdk-reactnative-device-security`, `@entrust.corporation/idvsdk-reactnative-analytics-events-face` |
| `@entrust.corporation/idvsdk-reactnative-biometric-token` | `@entrust.corporation/idvsdk-reactnative` |
| `@entrust.corporation/idvsdk-reactnative-consent` | `@entrust.corporation/idvsdk-reactnative` |
For example, to add the Face Motion module to a project that already has the core package installed:
```shell
$ npm install @entrust.corporation/idvsdk-reactnative-face-motion @entrust.corporation/idvsdk-reactnative-device-security @entrust.corporation/idvsdk-reactnative-analytics-events-face
or
$ yarn add @entrust.corporation/idvsdk-reactnative-face-motion @entrust.corporation/idvsdk-reactnative-device-security @entrust.corporation/idvsdk-reactnative-analytics-events-face
```
> ⚠️ **Warning:** Peer dependencies must be installed explicitly. On iOS, every package vendors only its own frameworks, and React Native autolinking links a package only when it is present in `node_modules`. If a peer is missing, the shared framework it provides is left out of the app and the build fails to link. On Android, Gradle resolves the shared artifacts transitively, so an omitted peer breaks only the iOS build.
Module packages track the version of the core package, so install the same version of each.
Building the app
No manual Xcode or Gradle changes are required — autolinking configures both platforms: - **iOS**: run `pod install` from the `ios/` directory. CocoaPods reads each package's podspec and embeds the vendored `.xcframework` binaries into your target. - **Android**: build the project as usual. Each package contributes a Gradle module that resolves the matching `com.entrust.identity.verification.sdk` artifact from Maven Central. **Note**: the React Native Consent package carries the Android artifact only. It vendors no iOS framework, so installing it has no effect on an iOS build, and the Consent module runs as a Web module there. The Entrust IDV SDK for iOS does ship a native `Consent` framework for direct iOS integrations. #### Adding language/translation files to the base bundle ### Android Similarly to adding native Kotlin modules, language bundles can be added manually to the embedding app's `build.gradle.kts` file by including the required dependencies as shown below: ```kotlin dependencies { // `en-gb` can be replaced with any of the supported locales implementation("com.entrust.identity.verification.sdk:translations-complete-en-gb:<NFC
Storage | | Proof of Address | Camera (back)
Storage | | Face Photo | Camera (front) | | Face Video | Camera (front)
Audio | | Face Motion | Camera (front)
Audio (unless capture option is disabled) | Modules not listed above do not require dedicated permissions. ### SDK permission inheritance User permissions have been optimized to reduce the number of requests made to the end user. By default, if the embedding app has already requested a given permission from the end user, the SDK will automatically inherit that permission and not request it again. Additionally, permissions are shared across all modules invoked by the SDK, whether in their native or Web form. **Note** that permissions still need to be declared as described in the next section. ### SDK permission requests ### Android For Android apps, permissions don't need to be explicitly declared since they are handled by the SDK. ### iOS For iOS apps, permissions must be declared in the application's `Info.plist` file.
| Permissions | OS instruction |
|---|---|
| Camera (combined front/back) |
|
| Audio |
|
| NFC |
```xml
|
| Storage |
|
#### Document filtering
As part of the flow, the end user is prompted to select the issuing country and document type before proceeding to the document's capture. This information is used to optimize the capture experience, as well as inform the end user about which documents they are allowed to use.
**Please note:**
- The selection screen is dynamic and will be automatically hidden when the document filtering configuration doesn't require the end user to indicate which document will be captured
- In a very limited number of cases, the end user may also be asked if they have a card or paper version of their document via an additional prompt
As part of the workflow configuration, it is possible to restrict the documents that can be selected in two ways:
- Within a Document Capture task, documented in the [Studio Product guide](/getting-started/workflow-studio-product/#document-capture-task)
- Otherwise, the recommended approach is to apply this configuration globally in your Dashboard under Accounts \ Supported Documents, as this configuration is also applied to your Document Reports. Any document that has been uploaded by an end user against your guidance will result in a Document Report sub-result of "rejected" and be flagged as `Image Integrity` > `Supported Document`
##### Document filtering for non-workflow based sessions
For integrations that are yet to migrate to workflow-based flows in Studio, the `Document` step defined in SDK initialization configuration may optionally include:
- `documentFiltering: {Filters}` - default all documents allowed
The `documentFiltering` parameter accepts two optional lists of `DocumentSelection` objects: one to `exclude` particular document types or countries and one to only `include` certain document types or countries. The two can be used together to provide the appropriate selection to the user.
The `DocumentSelection` object is defined as below:
```kotlin
DocumentSelection(
documentType: <>, // "Generic" is defined in the following section
issuingCountry: String, // Issuing country of the document in 3-letter ISO 3166-1 alpha-3 format. Must not be used in conjuction with "allCountries" option
allCountries: Boolean, // Whether the documentType selected should be applied to all possible countries
id: String, // Used to uniquely identify a "Generic" documentType
)
```
In the example below, the user will only be able to select a passport or driving license from any country (as a result of the `include` definition), but for France only passports will be accepted (`exclude` removes the option of a driving license for that country):
### Android
```kotlin
override fun onCreate(savedInstanceState: Bundle?) {
...
entrustIdv.start(ClassicParameters(
...
steps = listOf>(
...
Document(options = Options(
documentFiltering = DocumentFiltering(
include = listOf(
DocumentSelection(
documentType = DocumentType.Passport,
allCountries = true
),
DocumentSelection(
documentType = DocumentType.DrivingLicence,
allCountries = true
)),
exclude = listOf(
DocumentSelection(
documentType = DocumentType.DrivingLicence,
issuingCountry = "FRA"
)),
)
)),
)
))
}
```
### iOS
```swift
EntrustIdv(
sdkParameters: ClassicParameters(
...
steps:[
...
Document( options: .init(
documentFiltering: .init(
exclude: [ .init(
documentType: .drivingLicense,
issuingCountry: "FRA"
)],
include: [
.init(
documentType: .passport,
allCountries: true
),
.init(
documentType: .drivingLicense,
allCountries: true
)
]
))
)]
))
```
### React Native
```javascript
entrustIdv.start({
...
steps: [
...
Document({
documentFiltering: {
include: [{
documentType: DocumentType.Passport,
allCountries: true,
},
{
documentType: DocumentType.DrivingLicence,
allCountries: true,
},
],
exclude: [{
documentType: DocumentType.DrivingLicence,
issuingCountry: 'FRA',
},
],
},
}),
],
});
```
An additional option to `extend` the `DocumentFiltering` list can be used to add custom document types to the existing list of documents. This is explained in the following section.
**Please note the following SDK behaviors:**
- Hard-coding any document type and issuing country configuration in your SDK integration will fully override the Dashboard-based settings
- Passports have the same format worldwide, so the SDK will not show the country selection screen if `include` only contains passports and they are not restricted by country (e.g. `allCountries = true`)
- Currently only the following document types are supported by the SDK. If you select other document types in your Dashboard (visa, for example), these will not be displayed in the SDK selection screen. If you need to add other document types to the document selection screen, you can mitigate this limitation in the short-term, using the [Generic Document feature](#inclusion-of-generic-document-types):
- Driving License
- National Identity Card
- Passport
- Passport Card
- Residence Permit
- Generic - more information in the next section
##### Inclusion of generic document types
This feature is currently only available for non-workflow-based flows. It allows for an arbitrary document type to be shown to the end user for selection.
To use this feature:
- Generic documents must be defined in the `genericDocuments` property
- Using their unique identifiers, the newly defined generic document types can be added either to the `extend` property of the `DocumentFiltering` property (to add it to the default selection list) or the `include` property (to add it to a specific filtered list)
- `genericDocuments: {List}` - defaults to no generic documents
The `GenericDocument` object is defined as below:
```kotlin
GenericDocument(
id: String, // Unique identifier of the document type
country: String, // Issuing country of the document in 3-letter ISO 3166-1 alpha-3 format
pages: Int, // Number of pages that should be captured for this document. Can either be 1 or 2
title: String, // Name of the document as it will appear on the screen
subTitle: String, // Short description of the document that will appear on the document selection screen
)
```
In the example below, a custom, one-sided, document type is added to the default document selection list. It will only be available for French documents (as per its definition):
### Android
```kotlin
...
entrustIdv.start(ClassicParameters(
...
steps = listOf>(
...
Document(options = Options(
documentFiltering = DocumentFiltering(
extend = listOf(
GenericDocument(
id = "custom_lunch_card_FR",
country = "FRA",
pages = 1,
title = "Lunch Card",
subtitle = "Front picture of your lunch card"
)
)
)
))
)
))
```
### iOS
```swift
EntrustIdv(
sdkParameters: ClassicParameters(
...
steps:[
...
Document( options: .init(
documentFiltering: .init(
extend: [ .init(
id: "custom_lunch_card_FR",
title: "Lunch Card",
subtitle: "Front picture of your lunch card",
country: "FRA",
pages: 1
)],
)
))
]
))
```
### React Native
```javascript
entrustIdv.start({
...
steps: [
...
Document({
...
documentFiltering: {
extend: [{
id: "custom_lunch_card_FR",
country: "FRA",
pages: 1,
title: "Lunch Card",
subTitle: "Front picture of your lunch card"
}]
}
}),
],
});
```
#### NFC
> **Note:** NFC capture will be introduced in the new mobile SDKs in early 2026. The
> following section is intended to provide an overview of the expected
> capabilities
Recent passports, national identity cards and residence permits contain a chip that can be accessed using Near Field Communication (NFC). The SDK provides a set of screens and functionalities to extract this information, verify its authenticity and provide the results as part of a Document report.
The behavior of NFC capture is controlled within the Document Capture Studio task by one of the following options:
- Disabled: NFC reading will not be asked of end users
- Optional (Default): NFC reading will be attempted, if possible
- Required: NFC reading will be enforced, preventing end users from completing the flow without a successful reading
For more information on how to configure NFC and the list of supported documents, please refer to the NFC for [Document Report guide](/guide/document-report-nfc).
#### Configuration for non-workflow based sessions
For non-workflow-based flows, the `Document` step may optionally include the following options:
- `nfcPolicy: { Disabled | Optional | Required }` - default: `Optional`
### Android
```kotlin
override fun onCreate(savedInstanceState: Bundle?) {
...
entrustIdv.start(ClassicParameters(
...
steps = listOf>(
...
Document(options = Options(
nfcPolicy = NFCPolicy.Required
...
)),
)
))
}
```
### iOS
```swift
EntrustIdv(
sdkParameters: ClassicParameters(
...
steps:[
...
Document( options: .init(
nfcPolicy: NFCPolicy.required
))
]
))
```
### React Native
Information to be added shortly.
### Proof of Address capture
The Proof of Address capture module allows for the verification of an end user's address document. Users will be asked to select the issuing country of their document, the document type, and to provide images of their selected document. They will also have a chance to check the quality of the images before confirming.
There are currently no customization options for this step in Workflow Studio.
#### Proof of Address document filtering
As part of the flow, the end user is prompted to select the issuing country and document type before proceeding to the capture of the proof of address. This information is used to optimize the capture experience, as well as inform the end user about which documents they are allowed to use.
> ⚠️ **Warning:** This set of configuration options is not yet available in Studio Workflow
#### Configuration for non-workflow based sessions
For integrations that are yet to migrate to workflow-based flows in Studio, the `ProofOfAddress` step defined in SDK initialization configuration may **optionally** include:
- `proofOfAddressFiltering: {ProofOfAddressFiltering}` - default all types are allowed
The `proofOfAddressFiltering` parameter accepts a list of `ProofOfAddressSelection` objects used to `include` certain document types or countries.
**It is necessary to only provide types that are applicable in a given country for this functionality to work.** Please refer to the [Proof of Address product guide](/guide/proof-of-address-report/) for the full list of documents available for each country.
In the example below, the user will only be able to select a bank statement or utility bill from the USA or a bank statement for France:
### Android
```kotlin
override fun onCreate(savedInstanceState: Bundle?) {
...
entrustIdv.start(ClassicParameters(
...
steps = listOf>(
...
ProofOfAddress(
options = ProofOfAddress.Options(
proofOfAddressFiltering = ProofOfAddressFiltering(
include = (
listOf(
ProofOfAddressSelection(
proofOfAddressType = ProofOfAddressType.BankBuildingSocietyStatement,
issuingCountry = "USA"
),
ProofOfAddressSelection(
proofOfAddressType = ProofOfAddressType.UtilityBill,
issuingCountry = "USA"
),
ProofOfAddressSelection(
proofOfAddressType = ProofOfAddressType.BankBuildingSocietyStatement,
issuingCountry = "FRA"
)
))
))
))
))
}
```
### iOS
```swift
EntrustIdv(
sdkParameters: ClassicParameters(
...
steps:[
...
ProofOfAddress( options: ProofOfAddress.ProofOfAddressOptions(
proofOfAddressFiltering: ProofOfAddress.ProofOfAddressFiltering(
include: [
ProofOfAddress.ProofOfAddressSelection(
proofOfAddressType: .bankBuildingSocietyStatement,
issuingCountry: "USA"
),
ProofOfAddress.ProofOfAddressSelection(
proofOfAddressType: .utilityBill,
issuingCountry: "USA"
),
ProofOfAddress.ProofOfAddressSelection(
proofOfAddressType: .bankBuildingSocietyStatement,
issuingCountry: "FRA"
)
]
)),
)]
))
```
### React Native
```javascript
entrustIdv.start({
...
steps: [
...
ProofOfAddress({
documentFiltering: {
include: [{
proofOfAddressType: ProofOfAddressType.BankBuildingSocietyStatement,
issuingCountry: 'USA',
},
{
proofOfAddressType: ProofOfAddressType.UtilityBill,
issuingCountry: 'USA',
},
{
proofOfAddressType: ProofOfAddressType.BankBuildingSocietyStatement,
issuingCountry: 'FRA',
}],
},
}),
],
});
```
### Face Photo
The Face Photo module enables the capture of the end user's face in the form of a photo. For performance and compliance purposes, the Face Motion module is recommended instead.
| | |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| The execution of this module is controlled by the presence of a ["Face Capture: Photo" task](/getting-started/workflow-studio-product/#face-capture-photo-task) in your Studio workflow. The task has the following configuration options: - Show introduction screen (default `true`). When disabled, the end user would be taken directly to the capture screen. |  | ⚠️ As the Intro screen provides valuable information on how to successfully get verified, it is recommended to display it unless the integrator decides to provide their own instruction screen. #### Configuration for non-workflow based sessions For non-workflow-based flows, the `FacePhoto` step may optionally include the `showIntro: Boolean` property (default `true`) in its `Options`. ### Android ```kotlin override fun onCreate(savedInstanceState: Bundle?) { ... entrustIdv.start(ClassicParameters( ... steps = listOf>( ... FacePhoto(options = Options(showIntro = true)), ) ) ) } ``` ### iOS ```swift EntrustIdv( sdkParameters: ClassicParameters( ... steps:[ ... FacePhoto( options: .init( showIntro: true )) ] ) ) ``` ### React Native ```javascript entrustIdv.start({ ... steps: [ ... FacePhoto({ showIntro: true, }), ], }); ``` ### Face Video > **Note:** The current version of the SDK no longer contains a native variant of the Face > Video module. A Web variant can still be used in workflow and > non-workflow-based sessions The Face Video module enables the capture of the end user's face in the form of a video. For performance and compliance purposes, the Face Motion module is recommended instead. | | | | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- | | The execution of this module is controlled by the presence of a ["Face Capture: Video" task](/getting-started/workflow-studio-product/#face-capture-video-task) in your Studio workflow. The task has the following configuration options:
- Show introduction screen (default `true`). When disabled, the end user would be taken directly to the capture screen.
- Show confirmation video preview (default `true`). When disabled, the video file is automatically submitted after the capture finishes.
- (coming soon to Studio) Record Audio (default `false`). When enabled, the video capture will include sound capture. |  | ⚠️ As the Intro screen provides valuable information on how to successfully get verified, it is recommended to display it unless the integrator decides to provide their own instruction screen. #### Configuration for non-workflow based sessions For non-workflow-based flows, the `FaceVideo` step may optionally include the following options: - `showIntro: Boolean` (default `true`) - `showConfirmation: Boolean` (default `true`) - `recordAudio: Boolean` (default: `false`) ### Android ```kotlin override fun onCreate(savedInstanceState: Bundle?) { ... entrustIdv.start(ClassicParameters( ... steps = listOf>( ... FaceVideo(options = Options( showIntro = true, showConfirmation = true, recordAudio = false )), ) ) ) } ``` ### iOS ```swift EntrustIdv( sdkParameters: ClassicParameters( ... steps:[ ... FaceVideo(options: .init( showIntro: true, recordAudio: false, showConfirmation: true )) ] ) ) ``` ### React Native ```javascript entrustIdv.start({ ... steps: [ ... FaceVideo({ showIntro: true, showConfirmation: true, recordAudio: false, }), ], }); ``` ### Face Motion The Face Motion module enables the capture of the end user's face in the form of motion capture. | | | | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ | | The execution of this module is controlled by the presence of a ["Face Capture: Motion" task](/getting-started/workflow-studio-product/#face-capture-motion-task) in your Studio workflow. The task has the following configuration options:
- Show introduction screen (default `true`). When disabled, the end user would be taken directly to the capture screen.
- Record Audio (default `false`). When enabled, the video capture will include sound capture. |  | ⚠️ As the Intro screen provides valuable information on how to successfully get verified, it is recommended to display it unless the integrator decides to provide their own instruction screen. #### Configuration for non-workflow based sessions For non-workflow-based flows, the `FaceMotion` step may optionally include the following options: - `showIntro: Boolean` (default `true`) - `recordAudio: Boolean` (default: `false`) ### Android ```kotlin override fun onCreate(savedInstanceState: Bundle?) { ... entrustIdv.start(ClassicParameters( ... steps = listOf>( ... FaceMotion(options = Options( showIntro = true, recordAudio = false )), ) ) ) } ``` ### iOS ```swift EntrustIdv( sdkParameters: ClassicParameters( ... steps:[ ... FaceMotion( options: .init( showIntro: true, recordAudio: false )) ] ) ) ``` ### React Native ```javascript entrustIdv.start({ ... steps: [ ... FaceMotion({ showIntro: true, recordAudio: false, }), ], }); ``` ### One-time Password (OTP) The [One-time Password task](/getting-started/workflow-studio-product/#one-time-password-capture-task) allows for the verification of a mobile phone number when used in conjuction with the Qualified Electronic Signature task.
This task has no SDK configuration options and is available only via Studio.
### Qualified Electronic Signature (QES)
The [Qualified Elentronic Signature task](/getting-started/workflow-studio-product/#qualified-electronic-signature-capture-task) embeds the process provided by a Qualified Trust Service Provider to digitally sign a document.
This task has no SDK configuration options and is available only via Studio.
### Retry task
The Studio [Retry task](/getting-started/workflow-studio-product/#retry-task) allows orchestration between workflow tasks based on logical checks.
When the task's condition fails, the SDK will display a dedicated screen to the user, prompting them to proceed to the next logical task (or repeat a previous one).
This task has no additional configuration option beyond selecting a "Retry Reason". It is only available via Studio.
**Please note**: when a custom reason is provided in the task definition, it cannot be automatically translated by the SDK.
# More Information
## Accessibility
All SDKs have been optimized to provide the following accessibility support by default:
- Screen reader support: accessible labels for textual and non-textual elements available to aid TalkBack navigation, including dynamic alerts
- Dynamic font size support: all elements scale automatically according to the device's font size setting
- Sufficient color contrast: default colors have been tested to meet the recommended level of contrast
- Sufficient touch target size: all interactive elements have been designed to meet the recommended touch target size
Refer to our [accessibility statement](/sdk/sdk-accessibility-statement) for more details.
## Licensing
Due to API design constraints, and to avoid possible conflicts during the integration, we bundle some of our 3rd party dependencies as repackaged versions of the original libraries.
Please refer to the [SDK license acknowledgements](/sdk/sdk-licenses/) guide for more information.
# Appendix
## List of supported languages and locales
Entrust supports and maintains translations for 44 languages that can be implemented directly inside the SDK.
All of these languages are supported across Android, iOS and Web, under the following locales:
| Language | Locale | Android | iOS | Web |
| ------------------------ | --------- | ------- | ---------------- | ----------- |
| Arabic | `ar` | ✔ | ✔ | ✔ |
| Armenian | `hy` | ✔ | ✔ | ✔ |
| Bulgarian | `bg` | ✔ | ✔ | ✔ |
| Chinese (Simplified) | `zh_CN` | ✔ | ✔ (as `zh_Hans`) | ✔ |
| Chinese (Traditional) | `zh_TW` | ✔ | ✔ (as `zh_Hant`) | ✔ |
| Croatian | `hr` | ✔ | ✔ | ✔ |
| Czech | `cs` | ✔ | ✔ | ✔ |
| Danish | `da` | ✔ | ✔ | ✔ |
| Dutch | `nl` | ✔ | ✔ | ✔ |
| English (United Kingdom) | `en_GB` | ✔ | ✔ | ✔ |
| English (United States) | `en_US` | ✔ | ✔ | ✔ |
| Estonian | `et` | ✔ | ✔ | ✔ |
| Finnish | `fi` | ✔ | ✔ | ✔ |
| French | `fr` | ✔ | ✔ | ✔ |
| French (Canadian) | `fr_CA` | ✔ | ✔ | ✔ |
| German | `de` | ✔ | ✔ | ✔ |
| Greek | `el` | ✔ | ✔ | ✔ |
| Hebrew | `he` | ✔ | ✔ | ✔ |
| Hindi | `hi` | ✔ | ✔ | ✔ |
| Hungarian | `hu` | ✔ | ✔ | ✔ |
| Indonesian | `id` | ✔ | ✔ | ✔ |
| Italian | `it` | ✔ | ✔ | ✔ |
| Japanese | `ja` | ✔ | ✔ | ✔ |
| Korean | `ko` | ✔ | ✔ | ✔ |
| Latvian | `lv` | ✔ | ✔ | ✔ |
| Lithuanian | `lt` | ✔ | ✔ | ✔ |
| Malay | `ms` | ✔ | ✔ | ✔ |
| Norwegian | `nb` | ✔ | ✔ | ✔ |
| Persian | `fa` | ✔ | ✔ | ✔ |
| Polish | `pl` | ✔ | ✔ | ✔ |
| Portuguese | `pt` | ✔ | ✔ | ✔ |
| Portuguese (Brazil) | `pr_BR` | ✔ | ✔ | ✔ |
| Romanian | `ro` | ✔ | ✔ | ✔ |
| Russian | `ru` | ✔ | ✔ | ✔ |
| Serbian | `sr_Latn` | ✔ | ✔ | ✔ (as `sr`) |
| Slovak | `sk` | ✔ | ✔ | ✔ |
| Slovenian | `sl` | ✔ | ✔ | ✔ |
| Spanish | `es` | ✔ | ✔ | ✔ |
| Spanish (Latin America) | `es_419` | ✔ | ✔ | ✔ |
| Swedish | `sv` | ✔ | ✔ | ✔ |
| Thai | `th` | ✔ | ✔ | ✔ |
| Turkish | `tr` | ✔ | ✔ | ✔ |
| Ukrainian | `uk` | ✔ | ✔ | ✔ |
| Vietnamese | `vi` | ✔ | ✔ | ✔ |
# Changelog
### Android
### iOS
### React Native