MS-1433 Persist data for MFID analytics events across activity recreation

[luhmirin-s]

JIRA ticket
Will be released in: 2026.2.0

Root cause analysis (for bugfixes only)

First known affected version: 2026.1.0

• Lateinit fields are not persisted if the "Don't keep activities" flag is enabled.
• Fields in question are used for analytics and cannot be "recreated".

Notable changes

• Add a basic persistence for the lateinit fields.

Testing guidance

• Have “Don’t keep activities” enabled. Have MFID enabled in the project.
• Start identification flow, capture face.
• Press “Skip” on MFID selection screen
• Press home/minimise the app
• Reopen the app and press “Skip scanning”

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)
• Other teams notified about the changes (if applicable)

[Copilot]

Pull request overview

This PR adds SavedStateHandle-backed persistence for MFID external credential analytics timestamps/IDs so analytics events can survive ViewModel recreation.

Changes:

• Injects SavedStateHandle into ExternalCredentialViewModel.
• Restores and persists selection start time, selection event ID, and capture start time.
• Adds unit tests covering persistence/restoration paths.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
feature/external-credential/src/main/java/com/simprints/feature/externalcredential/screens/controller/ExternalCredentialViewModel.kt	Adds SavedStateHandle persistence for analytics-related fields.
feature/external-credential/src/test/java/com/simprints/feature/externalcredential/screens/controller/ExternalCredentialViewModelTest.kt	Adds tests for saved/restored analytics state.

[BurningAXE]

Should the savedStateHandle be updated in an onStop() callback instead of being scattered throughout the VM?

[luhmirin-s]

I think this is simpler and safer, since the onStop() could be called before "captureStartTime" is initialised and we would need to have extra error handling.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud