[MS-1239] Fragment correctly restores OCR state after being rotated

[alexandr-simprints]

JIRA ticket
Will be released in: 2025.4.0

Root cause analysis (for bugfixes only)

First known affected version: 2025.4.0

If device is rotated during the OCR scan, the UI is reverted back to the initial screen state. However, frames are still being captured for OCR in background.

This happens because there are two initializeFragment() invocations in the ExternalCredentialScanOcrFragment:

1. Within the async camera permission launchPermissionRequest
2. Within the onResume function

Ideally we would like to have the following logic in the fragment:

1. Check camera permissions
2. Start camera preview, if granted
3. Start observing OCR state

Notable changes

• Renaming stateLiveData to scanOcrStateLiveData to explicitly specify that this object stores the state of the OCR, not the state of the fragment
• Observers are only initialized when camera is ready

Screen_recording_20251107_134543.mp4

Testing guidance

• Start OCR
• Rotate the device
• Ensure the OCR state remains unchanged

Additional work checklist

• Effect on other features and security has been considered
• Design document marked as "In development" (if applicable)
• External (Gitbook) and internal (Confluence) Documentation is up to date (or ticket created)
• Test cases in Testiny are up to date (or ticket created)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[luhmirin-s]

Do we have a testiny case for MFID screen rotations?

[alexandr-simprints]

Do we have a testiny case for MFID screen rotations?

@luhmirin-s yes, there are tests: TC-310