Repository navigation
Feat/mobile scanner migration - #3591
Merged
Merged
Conversation
The Yoti AI selfie age verification is no longer used. Remove its pages, camera cubit, models and assets, the HomeCubit calls to the Yoti endpoints, the AI validation URLs and the strings only it used. Discover now sends every age card (Over 13 to 65, age range) to the ID360 KYC flow, the other option of the removed method chooser; enterprise profiles still open the issuer link. Also drop the image and flutter_image_compress dependencies, used only by this feature, and describe the camera permission as QR code scanning on iOS.
The scanner fed every camera frame from the camera plugin to ML Kit through Dart, without waiting for the previous frame: on Android this churned hundreds of MB of frame buffers per second, and a camera disposed while still starting was never released. Users saw a grey preview for a while when opening the scanner. Replace QrCameraView with QrScannerView, built on mobile_scanner 7.5.0 (CameraX on Android, Vision on iOS). Frames stay native, the widget starts and releases the camera with the page and the app lifecycle, and only the first QR code inside the darkened scan window is handed over. The Scan tab and QrScannerPage both use it. A denied camera permission now shows a message with Open settings and Try again instead of an empty view. Drop the camera, google_mlkit_barcode_scanning and google_mlkit_commons dependencies, and the first-frame skip workaround for stale frames of the camera plugin.
These cards are no longer offered. Remove the Over 13, 15, 18 (all formats), 21, 50 and 65, DeFi compliance and liveness (Humanity) cards from Discover, the KYC routing only they used, the checkForAIKYC getter and the supportDefiCompliance parameter. Credentials of these types that users already hold still display, and the discoverCardsOptions profile fields stay in the configuration model.
These cards are no longer offered either. Discover now sends only the ID card to the ID360 KYC flow. Credentials of these types that users already hold still display, and the discoverCardsOptions profile fields stay in the configuration model.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Type of Change