Wallet Use Instructions¶
Developers testing with the National EUDI Wallet in the Sandbox should be aware of the following details, peculiarities and known bugs.
1. Wallet Set-Up and Operation¶
1.1 Distribution and Installation¶
The Closed Beta wallet is distributed via TestFlight, and later via the Google Beta Store as well.
Testflight Configuration
TestFlight should be configured to automatically install updates.
During the Closed Beta phase, updates will be frequent, and not announced in advance.
- Always verify the wallet version when testing or reporting issues.
- Re-test issues after installing the latest update.
2. Wallet Functionality and Quirks¶
This section documents current wallet behavior that may be surprising, non-obvious, or different from production expectations, but is considered expected behavior for the closed beta. These items are not bugs, but known characteristics or limitations of the wallet at this stage.
2.1 Simulated eID Card PID Issuance¶
For the benefit of testing, the wallet offers PID issuance with a simulated eID, that doesn't require a physical testing card. Note that with a simulated eID PID issuance, any PIN you enter will be accepted.
2.2 Credential Usage Limits¶
In the National EUDI Wallet, PIDs are single-use credentials to combat linkability. The current batch limit is 10 presentations per issuance event. Once the limit is reached, further presentations will fail. The credential must be reissued before it can be used again. This behavior is expected and should be accounted for in test scenarios.
2.3 Log Exports¶
To export the Wallet Logs for debugging purposes, enter the hamburger menu in the Wallet App. Press "Download Logs" to download a text file.
2.3 SD-JWT vc_values¶
The vct_values for a PID Presentation Request in SD-JWT format uses the following value for the German PID Provider: urn:eudi:pid:de:1.
In the long run, relying parties across Europe can query for a PID from any member state using the vct_value urn:eudi:pid:1.
3. Known Bugs and Temporary Workarounds¶
iOS¶
mDoc Presentation¶
During mDoc PID presentations, the wallet may hang and throw up a "Credential Revoked" error. This bug is currently under investigation. The advised course of action is to retry the presentation, or reissue the PID and retry the presentation.
Android¶
Simulated eID Card Does Not Advance Automatically¶
When using a simulated eID card (enabled via the toggle) instead of a physical card, the flow may not advance automatically on the card presentation screen.
Workaround: Tap the animated illustration displayed on the screen to proceed to the next step.
"Personal data" Entry Missing in Issued PID View¶
On some devices, opening an issued PID may not show the “Personal data” entry.
Details: This is a UI rendering issue where the entry is partially or fully obscured by the header, making it invisible. The underlying data is unaffected.
Status: A fix is planned for an upcoming release.
Issuance Flow May Stall After Wallet PIN Setup¶
During credential issuance, the application may become stuck on the “Wallet PIN Set – Success” screen without further user feedback.
Workaround: Restart the application and repeat the issuance flow.
Deleting a PID May Prevent Re-Issuance¶
In some cases, deleting a PID does not fully reset the internal state, which can block subsequent re-issuance attempts.
Workaround:
- Clear the application's cache and storage
- Restart the application
- Start the issuance flow again
General Recovery for Unexpected Behavior¶
If you encounter any other unexpected or blocking behavior during testing:
Recommended recovery step: Clear the application cache and storage, restart the app, and repeat the affected flow.