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.
!!! info "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 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.1 SD-JWT vc_values¶
The vct_values for a PID Presentation Request in SD-JWT format uses the following URL: https://demo.pid-provider.bundesdruckerei.de/credentials/pid/1.0.
In the future, we expect to use the value urn:eudi:pid:de:1 for the German PID Provider. 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.
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.
3. Known Bugs¶
1. 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