You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We could finally reproduce the timeout issue. The ephemeral identifier present in the QR code/redirect link has a 10 second validity.
For cross-device flows, this makes sense, since the user first needs to unlock their NL Wallet app, and then scan the QR code. In this case, the NL Wallet fetches the disclosure information immediately.
In same-device flows, the link also has 10 seconds expiry time, but the disclosure information is only fetched after the user unlocks the wallet. What can happen is that the user takes longer than 10 seconds to unlock the wallet, and then they get a timeout error.
Please see the videos below for an example.
Success Case (Fast User)
ScreenRecording_01-20-2025.15-56-59_1.mov
Fail Case (Slower User)
ScreenRecording_01-20-2025.15-55-55_1.MP4
The text was updated successfully, but these errors were encountered:
Thanks for filing the issue! We understand that 10 seconds may be too quick for some users. We're currently discussing if we should prolong this time window and if so by how much, or if we should find some other way of dealing with this problem. We'll get back to you.
Hello,
We could finally reproduce the timeout issue. The ephemeral identifier present in the QR code/redirect link has a 10 second validity.
For cross-device flows, this makes sense, since the user first needs to unlock their NL Wallet app, and then scan the QR code. In this case, the NL Wallet fetches the disclosure information immediately.
In same-device flows, the link also has 10 seconds expiry time, but the disclosure information is only fetched after the user unlocks the wallet. What can happen is that the user takes longer than 10 seconds to unlock the wallet, and then they get a timeout error.
Please see the videos below for an example.
Success Case (Fast User)
ScreenRecording_01-20-2025.15-56-59_1.mov
Fail Case (Slower User)
ScreenRecording_01-20-2025.15-55-55_1.MP4
The text was updated successfully, but these errors were encountered: