Skip to content

Commit

Permalink
Release commit for 4.2.1
Browse files Browse the repository at this point in the history
  • Loading branch information
JumioMobileTeam committed Oct 24, 2023
1 parent 7361986 commit e2bc37c
Show file tree
Hide file tree
Showing 113 changed files with 1,723 additions and 14,009 deletions.
208 changes: 64 additions & 144 deletions README.md

Large diffs are not rendered by default.

98 changes: 10 additions & 88 deletions docs/changelog.md
Original file line number Diff line number Diff line change
@@ -1,11 +1,10 @@
![Header Graphic](images/jumio_feature_graphic.jpg)

[![Version](https://img.shields.io/github/v/release/Jumio/mobile-sdk-android?style=flat)](../README.md#release-notes)
[![API Doc](https://img.shields.io/github/v/release/Jumio/mobile-sdk-android?label=API%20doc&color=green&style=flat)](https://jumio.github.io/mobile-sdk-android/)
[![License](https://img.shields.io/badge/license-commercial-3D3D3D?style=flat)](../README.md#copyright)
[![Platform](https://img.shields.io/badge/platform-Android-lightgrey?style=flat)](../README.md#general-requirements)
[![API Level](https://img.shields.io/badge/API%20level-21+-orange?style=flat)](../README.md#general-requirements)
[![Maven](https://img.shields.io/maven-metadata/v?metadataUrl=https%3A%2F%2Frepo.mobile.jumio.ai%2Fcom%2Fjumio%2Fandroid%2Fcore%2Fmaven-metadata.xml?style=flat)](../README.md#integration)
[![Version](https://img.shields.io/github/v/release/Jumio/mobile-sdk-android?style=flat)](#release-notes)
[![License](https://img.shields.io/badge/license-commercial-3D3D3D?style=flat)](#copyright)
[![Platform](https://img.shields.io/badge/platform-Android-lightgrey?style=flat)](#general-requirements)
[![Maven](https://img.shields.io/maven-metadata/v?metadataUrl=https%3A%2F%2Frepo.mobile.jumio.ai%2Fcom%2Fjumio%2Fandroid%2Fcore%2Fmaven-metadata.xml?style=flat)](#integration)
[![API Level](http://img.shields.io/badge/API%20Level-19+-orange?style=flat)](#general-requirements)

[Improvement]: https://img.shields.io/badge/Improvement-green "Improvement shield"
[Change]: https://img.shields.io/badge/Change-blue "Change shield"
Expand All @@ -16,93 +15,16 @@ All notable changes, such as SDK releases, updates and fixes, are documented in
For detailed technical changes please refer to our [Transition Guide](transition_guide.md).

## Support Period
Current SDK version: __4.8.1__
Current SDK version: __4.2.1__
The previous release version 4.1.0 of the Jumio Mobile SDK is supported until 2022-08-27.

Please refer to our [SDK maintenance and support policy](maintenance_policy.md) for more information about Mobile SDK maintenance and support.
When the support period has expired, bug fixes and technical support will no longer be provided. Current bugs are typically fixed in the upcoming versions. __Older SDK versions will keep functioning with our server until further notice,__ but we highly recommend you always update to the latest version to benefit from SDK improvements and bug fixes.

## SDK Version: __4.8.1__
## SDK Version: __4.2.1__
![Fixes](https://img.shields.io/badge/Fix-success) Removed Location handling to fix potential Google Play Store rejections

## SDK Version: __4.8.0__
![Improvement] Managing Liveness dependencies to help better conversion [Identity Verification]

## SDK Version: __4.7.1__
![Fixes](https://img.shields.io/badge/Fix-success) Removed Location handling to fix potential Google Play Store rejections

## SDK Version: __4.7.0__
![Improvement] Added support for [CameraX](https://developer.android.com/training/camerax)

![Improvement] Datadog SDK version update to 2.0: Added possibility to have a dedicated Jumio Datadog instance

![Improvement] Improved Jumio Liveness capturing experience [Identity Verification]

![Change] Updated Jumio Liveness module [Identity Verification]

![Change] Removed previous scanning functionalities, now all included in Autocatpure functionality [ID Verification]

![Change] Removed Microblink barcode scanning, switched to MLkit [ID Verification]

![Fix] Fixed Liveness customizaton bug [Identity Verification]

## SDK Version: __4.6.1__
![Fixes](https://img.shields.io/badge/Fix-success) Removed Location handling to fix potential Google Play Store rejections

## SDK Version: __4.6.0__
![Improvement] Added Jumio Liveness module to enhance the Liveness user experience and interface (Identity Verification)

![Improvement] Improved Liveness customization options (Identity Verification)

## SDK Version: __4.5.1__
![Fixes](https://img.shields.io/badge/Fix-success) Removed Location handling to fix potential Google Play Store rejections

## SDK Version: __4.5.0__
![Improvement] Added possibility for users to verify their identity using [Digital Identity](../README.md#digital-identity) [ID Verification, Identity Verification]

![Improvement] iProov SDK version update to 8.3.1 [Identity Verification]

![Improvement] Improved user consent handling [ID Verification, Identity Verification]
<details>
<summary>More details</summary>

### User consent
User consent is now acquired for all users to ensure the accordance with biometric data protection laws. Please also refer to the [User Consent section](integration_faq.md#user-consent) in our FAQ.
</details>

![Fix] Bug fixes: UI bugs, passport scanning issue for certain countries [ID Verification]

## SDK Version: __4.4.2__
![Fixes](https://img.shields.io/badge/Fix-success) Removed Location handling to fix potential Google Play Store rejections

## SDK Version: __4.4.1__

![Fix] Bug fix: Internal crashes for certain edge cases

## SDK Version: __4.4.0__

![Improvement] Fully redesigned ID Autocapture experience - seamless capturing, precise guidance and faster user journey [ID Verification]

![Improvement] Major iProov SDK version update to 8.0.3 - no more face scanning filter, improved UI and more customization options [Identity Verification]

![Improvement] Mandatory NFC scanning option [ID Verification]

![Fix] Bug fixes: UI bugs, internal crashes

## SDK Version: __4.3.0__

![Improvement] Autocapture functionality (introduced in SDK 4.2.0) is no longer in beta stage [ID Verification]

![Improvement] [Document Verification](../README.md#document-verification) functionality added

![Improvement] Improved user guidance: Clear distinction between scanning frontside or backside of ID document [ID Verification]

![Change] iProov SDK version update to 7.5.0 [Identity Verification]

![Change] The SDK's minSdkVersion has been increased to 21 (Lollipop). Please check the [Transition Guide](transition_guide.md) for details.

![Fix] UI bugs, internal crashes [Identity Verification]

## SDK Version: __4.2.0__
![Improvement] Alignment of previously existing scanning method and improved user experience through addition of Autocapture module (Beta) [ID Verification]
![Improvement] Alignment of previously existing scanning method and improved user experience through addition of Generic ID Scanning module (Beta) [ID Verification]

![Improvement] Support for device fingerprint capability [ID Verification, Identity Verification]

Expand Down
Binary file removed docs/images/capturing_methods/autocapture_01.jpg
Binary file not shown.
Binary file removed docs/images/capturing_methods/autocapture_02.jpg
Binary file not shown.
Binary file removed docs/images/consent/consent_active_checked.jpg
Binary file not shown.
Binary file removed docs/images/consent/consent_active_unchecked.jpg
Binary file not shown.
Binary file removed docs/images/consent/consent_passive.jpg
Binary file not shown.
Binary file modified docs/images/happy_paths/scanpart_happy_path_diagram.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/images/images_overview/confirm_screen.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/images/images_overview/images_overview.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/images/images_overview/intro_screen.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/images/images_overview/menu_screen.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
72 changes: 24 additions & 48 deletions docs/integration_faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,6 @@
# FAQ

## Table of Contents
- [User Consent](#user-consent)
- [Improve User Experience and Reduce Drop-off Rate](#improve-user-experience-and-reduce-drop-off-rate)
- [Managing Errors](#managing-errors)
- [Ad Blockers or Firewall](#ad-blockers-or-firewall)
Expand All @@ -21,18 +20,8 @@
- [Java 8 Compatibility](#Java-8-compatibility)
- [Overview of Scanning Methods](overview-of-scanning-methods)
- [Glossary of Commonly Used Abbreviations](#glossary)
- [Google Play Store Prominent Disclosure](#google-play-store-prominent-disclosure)
- [Jumio Support](#jumio-support)

## User Consent
User consent is now acquired for all users to ensure the accordance with biometric data protection laws. Depending on the legal requirements, consent can be acquired in one of two ways: __Active__ or __passive__.

For __active__ consent instances, the user needs to accept the consent items explicitly, e.g. by enabling a UI switch or checking a checkbox for each consent item. For __passive__ consent instances, it is enough to present the consent text and URL to the user. The user implicitly accepts the passive consent items by continuing with the journey.

<img src="images/consent/consent_passive.jpg" alt="Acquiring passive user consent">
<img src="images/consent/consent_active_unchecked.jpg" alt="Acquiring active user consent">
<img src="images/consent/consent_active_checked.jpg" alt="Acquired active user consent">

## Improve User Experience and Reduce Drop-off Rate
When evaluating user flows, one of the most commonly used metrics is the rate of drop-offs. At Jumio, we see considerable variance in drop-off rates across industries and customer implementations. For some implementations and industries, we see a higher rate of drop-offs on the first screens when compared with the average.
Scanning an ID with sensitive personal data printed on it naturally creates a high barrier for participation on the part of the end user. Therefore, conversion rates can be significantly influenced when the application establishes a sense of trust and ensures that users feel secure sharing their information.
Expand All @@ -56,12 +45,12 @@ Not every error that is returned from the SDK should be treated the same. The er

The following table highlights the most common error codes which are returned from the SDK and explains how to handle them appropriately in your application.

| Code | Cause | Recommended Handling |
|:-----------:|:---------------------------------------------------------------------------------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| A[xx][yyyy] | Caused by temporary network issues like a slow connection. | Advise to check the signal and retry the SDK journey. |
| E[xx][yyyy] | Flight mode is activated or no connection available. | The user should be asked to disable flight mode or to verify if the phone has proper signal. Advise to connect to WIFI and retry the SDK journey afterwards. |
| G[xx][0000] | The user pressed back or X to exit the SDK while no error view was presented. | Reasons for this could be manifold. Often it might be due to the fact that the user didn't have his identity document at hand. Give the user the option to retry. |
| J[xx][yyyy] | The SDK journey was not completed within the session's max. lifetime. (The default is 15 minutes.) | The user should be informed about the timeout and be directed to start a new Jumio SDK session. |
|Code | Cause | Recommended Handling |
|:---:|:------|:---------------------|
| A[x][yyyy] | Caused by temporary network issues like a slow connection. | Advise to check the signal and retry the SDK journey. |
| E[x][yyyy] | Flight mode is activated or no connection available. | The user should be asked to disable flight mode or to verify if the phone has proper signal. Advise to connect to WIFI and retry the SDK journey afterwards. |
| G[0][0000] | The user pressed back or X to exit the SDK while no error view was presented. | Reasons for this could be manyfold. Often it might be due to the fact that the user didn't have his identity document at hand. Give the user the option to retry. |
| J[x][yyyy] | The SDK journey was not completed within the session's max. lifetime. (The default is 15 minutes.) | The user should be informed about the timeout and be directed to start a new Jumio SDK session. |

### Ad Blockers or Firewall
End users might face the situation where they are connected to a network that can't reach our Jumio endpoints.
Expand All @@ -79,19 +68,20 @@ Depending on your specific needs, you may want to strip out unused functionality

The following table shows a range of different product configurations with the size and modules that are linked for it. These measurements reflect the extra size that Jumio components add to your app download size and are based on our [sample application](../sample/JumioMobileSample/).

| Product Configuration | Size | Modules |
| :------------------------------------------- | :------: | :------------------------------------------------------------------------------------------: |
| Base | 2.67 MB | core |
| Base + iProov | 3.52 MB | core, iproov |
| Base + Autocapture | 4.21 MB | core, docfinder |
| Base + Autocapture, Barcode-Vision | 4.51 MB | core, docfinder, barcode-vision |
| Base + Autocapture, Barcode-Vision, iProov | 5.35 MB | core, docfinder, barcode, iproov |
| Base + Autocapture, Barcode-Vision, Liveness | 6.28 MB | core, docfinder, barcode, liveness |
| Base + Autocapture, Barcode-Vision, NFC | 7.59 MB | core, docfinder, barcode, nfc |
| All (Custom UI only) | 10.33 MB | core, docfinder, barcode-vision, iproov, nfc, devicerisk, digital-identity, camerax,liveness |
| Base + Autocapture, Default UI | 4.60 MB | core, docfinder, default-ui |
| Base + Autocapture, Default UI, Datadog | 5.21 MB | core, docfinder, default-ui, datadog |
| All (with Default UI) | 11.17 MB | core, docfinder, barcode-vision, iproov, nfc, devicerisk, default-ui, datadog, liveness |
| Product Configuration | Size | Modules |
|:-----------------------|:--------:|:------------:|
| Base | 1.78 MB | core |
| Base + Liveness | 2.23 MB | core, iproov |
| Base + MRZ | 3.15 MB | core, mrz |
| Base + MRZ, Linefinder | 3.42 MB | core, mrz, linefinder |
| Base + MRZ, Linefinder, Barcode | 4.47 MB | core, mrz, linefinder, barcode |
| Base + MRZ, Linefinder, Barcode-Vision | 3.72 MB | core, mrz, linefinder, barcode-vision |
| Base + MRZ, Linefinder, Barcode, Liveness | 4.91 MB | core, mrz, linefinder, barcode, iproov |
| Base + MRZ, Linefinder, Barcode, NFC | 6.02 MB | core, mrz, linefinder, barcode, nfc |
| All (Custom UI only) | 12.30 MB | core, mrz, linefinder, barcode, barcode-vision, iproov, nfc, docfinder, devicerisk |
| Base + MRZ, Linefinder, Default UI | 3.84 MB | core, mrz, linefinder, default-ui |
| Base + MRZ, Linefinder, Default UI, DataDog | 4.34 MB | core, mrz, linefinder, default-ui, datadog |
| All (with Default UI) | 13.13 MB | core, mrz, linefinder, barcode, barcode-vision, iproov, nfc, docfinder, devicerisk, default-ui, datadog |

__Note:__ The size values in the table above depict the decompressed install size required on a device and are comparable to the estimated Play Store files size. The size value might vary by a few percent, depending on the actual device used. All sizes are calculated based on a build of our sample application using arm64 architecture, english translations and xxhdpi screen resolution.

Expand All @@ -114,7 +104,7 @@ defaultConfig {
}
```

It's also possible to manually provide a split apk on Google Play. The apk can be split based on the architecture if multiple apks should be uploaded to the Google Play Store. Google Play Store manages to deliver the appropriate apk for the device.
It's also possible to manually provide a splitted apk on Google Play. The apk can be split based on the architecture if multiple apks should be uploaded to the Google Play Store. Google Play Store manages to deliver the appropriate apk for the device.
```
splits {
abi {
Expand Down Expand Up @@ -209,28 +199,17 @@ android {

## Overview of Scanning Methods

#### Autocapture
Combines all previously existing scanning methods into one automatic, seamless experience.

![Autocapture Success](images/capturing_methods/autocapture_01.jpg) ![Autocapture Scanning](images/capturing_methods/autocapture_02.jpg)

#### Linefinder (deprecated)
***As of SDK version 4.7.0 this module has been deprecated. Please use [Autocapture](https://github.com/Jumio/mobile-sdk-android/blob/master/docs/integration_faq.md#autocapture)
instead.***
#### Linefinder
Scanning using edge detection.

![Linefinder Empty](images/capturing_methods/linefinder_scanning_01.jpg) ![Linefinder Document](images/capturing_methods/linefinder_scanning_02.jpg) ![Linefinder Processing](images/capturing_methods/linefinder_scanning_03.jpg)

#### MRZ (deprecated)
***As of SDK version 4.7.0 this module has been deprecated. Please use [Autocapture](https://github.com/Jumio/mobile-sdk-android/blob/master/docs/integration_faq.md#autocapture)
instead.***
#### MRZ
Data extraction from passports, some identity cards and some visas.

![MRZ Empty](images/capturing_methods/mrz_scanning_01.jpg) ![MRZ Document](images/capturing_methods/mrz_scanning_02.jpg)

#### Barcode (deprecated)
***As of SDK version 4.7.0 this module has been deprecated. Please use [Autocapture](https://github.com/Jumio/mobile-sdk-android/blob/master/docs/integration_faq.md#autocapture)
instead.***
#### Barcode
PDF417 barcode data extraction, for example from US and Canadian driver licenses.

![Barcode Empty](images/capturing_methods/barcode_scanning_01.jpg) ![Barcode Document](images/capturing_methods/barcode_scanning_02.jpg)
Expand All @@ -248,8 +227,5 @@ Data extraction from eMRTD documents, for example passports.
## Glossary
A [quick guide to commonly used abbreviations](integration_glossary.md) throughout the documentation which may not be all that familiar.

## Google Play Store Prominent Disclosure
Some parts of the SDK might require prominent disclosure - please see the [Privacy Notice](integration_guide.md#privacy-notice) section in the Integration Guide for further details

## Jumio Support
The Jumio development team is constantly striving to optimize the size of our frameworks while increasing functionality, to improve your KYC and to fight fraud. If you have any further questions, please reach out to our [support team](mailto:[email protected]).
3 changes: 0 additions & 3 deletions docs/integration_glossary.md
Original file line number Diff line number Diff line change
Expand Up @@ -60,6 +60,3 @@ Passport

### 3D-Liveness
Liveness check: The 3D-liveness check makes sure that a face scan performed was not of a picture, but of an actual, living person who also matches the picture on the previously scanned document

### DID
Digital Identity
Loading

0 comments on commit e2bc37c

Please sign in to comment.