Description
On the Restore screen, when a user enters their security answer to recover their account, the input is displayed in plain text. This is inconsistent with the behaviour when the security answer is first set in the application, where the input is masked (hidden). The answer field should behave the same way in both places for consistency and to protect sensitive recovery information.

Reported by Talha
Steps to reproduce
- Open the eID wallet application.
- Navigate to the Restore / account recovery flow.
- Reach the "Enter answer to your question" screen.
- Begin typing the security answer in the Recovery field.
Expected behavior
The security answer input should be masked (obscured, e.g. dots/asterisks), matching the behaviour of the same field when the answer is first saved in the app.
Actual behavior: The typed security answer is displayed in plain text in the input field.
Supporting Media

Desktop:
- Device: Mobile
- OS: (fill in — e.g. iOS / Android + version)
- Browser: N/A (native app)
- Version: (fill in)
Additional Context
Severity: P3 – Low (cosmetic / UX inconsistency, no error thrown). No logs — purely a visual issue.
Description
On the Restore screen, when a user enters their security answer to recover their account, the input is displayed in plain text. This is inconsistent with the behaviour when the security answer is first set in the application, where the input is masked (hidden). The answer field should behave the same way in both places for consistency and to protect sensitive recovery information.
Steps to reproduce
Expected behavior
The security answer input should be masked (obscured, e.g. dots/asterisks), matching the behaviour of the same field when the answer is first saved in the app.
Actual behavior: The typed security answer is displayed in plain text in the input field.
Supporting Media
Desktop:
Additional Context
Severity: P3 – Low (cosmetic / UX inconsistency, no error thrown). No logs — purely a visual issue.