Bugfix Prevent a possible database corruption when checking encryption status

[meladRaouf]

JIRA ticket
Will be released in: 2025.2.0

Root cause analysis (for bugfixes only)

First known affected version: 2025.2.0

Using SQLiteDatabase.openDatabase() without a passphrase on an encrypted Room database caused SQLite to treat the DB as corrupted, triggering an automatic wipe during internal diagnostics.

Corruption reported by sqlite on database: /data/user/0/com.simprints.id/databases/db-subjects
DB wipe detected: package=com.simprints.id reason=corruption
...
at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:1206)
at com.simprints.infra.enrolment.records.repository.local.RoomEnrolmentRecordLocalDataSource.isDBEncrypted(SourceFile:3)

Fix

• Removed unsafe direct DB access via SQLiteDatabase.openDatabase().

Testing guidance

Open the migration section in the troubleshooting screen when the active database is Room.

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)

[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]

This is definitely a simpler option :D