googlesamples / googlesamples/mlkit

Document Scanner review screen shows only "Retake" — no confirm button, unresponsive to taps/gestures (Galaxy S25, Android 16)

Open
#1,065 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Kotlin
Stars
4.3k
Forks
3.1k
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**

On a Samsung Galaxy S25 (SM-S931B) running Android 16 (SDK 36), the Document Scanner's post-capture review screen renders with a visible "Retake" button but no confirm/accept/checkmark button anywhere. The screen is otherwise unresponsive:

- Tapping the scanned image does nothing
- Tapping the gear/settings icon does nothing
- Swiping in any direction does nothing
- Only "Retake" is reachable; there is no way to accept the scan and complete the flow

This reproduces with both SCANNER_MODE_FULL and SCANNER_MODE_BASE — switching modes has no effect on the missing button, which rules out the ML-cleanup/filter UI as the cause and points at the base review/control-panel layout itself.

**To Reproduce**

1. Integrate play-services-mlkit-document-scanner:16.0.0 (via GmsDocumentScannerOptions/GmsDocumentScanning).
2. Launch the scanner on a Samsung Galaxy S25 (SM-S931B), Android 16.
3. Scan a plain A4 page.
4. Observe the review screen: "Retake" is present; no confirm/accept control is visible or reachable by tap, swipe, or rotation.

**Expected behavior**

The review screen should show a confirm/accept control (checkmark or equivalent) that lets the user complete the scan.

**SDK Info**
- com.google.android.gms:play-services-mlkit-document-scanner:16.0.0
- Google Play services: 26.26.34
- Scanner modes tested: SCANNER_MODE_FULL, SCANNER_MODE_BASE (both affected)

**Smartphone**
- Device: Samsung Galaxy S25 (SM-S931B)
- OS: Android 16 (API 36)
- Screen: 1080×2340, 480dpi (~360dp width — standard phone width, not a large-screen/tablet layout)

**Possibly related**

This may be related to #1026 (document scanner's activity hardcoded to portrait orientation causing large-screen-compatibility issues "from Android 16"), given this device is on Android 16 and the symptom (control-panel elements unreachable) is consistent with a layout/letterboxing issue triggered by that OS version's large-screen compatibility enforcement, even though the S25 isn't a tablet/foldable.

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the flow using play-services-mlkit-document-scanner:16.0.0 through GmsDocumentScannerOptions/GmsDocumentScanning on the listed Galaxy S25 and Android 16 configuration. Compare SCANNER_MODE_FULL and SCANNER_MODE_BASE, then review the relationship to issue #1026; done means the post-capture screen exposes a reachable confirm control and completes the scan.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.