Passkey sign-in, Arkade change and home balances
TLDR
1 PR merged, 2 PRs opened, 0 commits across all branches, 1 repo (the Nuri app: 3), 2 deployments, +677 / -40 lines. 0 new features, all three were fixes.
Signing in with an existing passkey is shipped: the tap opens the passkey picker right away and a failure now shows an error. Still open are a fix for Arkade sends that leave too little change, and a home screen that stops showing 0,00 and a missing name while it is still loading.
Signing in with an existing passkey
This is merged, in the Nuri app. Before, tapping “Use existing Passkey” could show no passkey UI at all, and every failure on that path was silent, so the only thing a user could report was that the button does nothing.
The first tap now starts the passkey prompt directly instead of opening a “continue” screen first. On iOS and desktop you still land on the wallet’s own passkey, and on Android you get the system picker. Android also showed the picker with every Nuri passkey but then rejected the one you picked, so now it accepts your pick there. Every restored passkey still goes through the server check before anything is saved on the device.
Every passkey prompt now has a 90 second limit. That is above the 60 second prompt timeout, so a slow PIN is never cut off, but a prompt that never comes back no longer leaves a dead button, you get an error and can retry. That error is now actually shown on the sign-in screen, in all 12 languages, instead of the screen silently resetting. The support dump also includes the last five passkey attempts with type, result and duration, without any passkey data in it.
Typecheck and lint are clean and all 2,774 tests pass, including new tests for the time limit, the support trace and the Android picker behavior. The case where the server reports an account as not registered is not part of this and is tracked separately.
Arkade sends with small change
Open, not merged. On Arkade every output has to be at least the server’s minimum, and inputs and outputs must add up exactly. So when a send leaves change between zero and that minimum, the server refuses it, but the app only found out after the user had already approved with the passkey, and the user saw a raw error plus a pending row. This came from a real payout funded from a Lightning balance where the change would have been 169 sats.
The app now plans the send against the wallet’s own coins first. If the change is zero or above the minimum, nothing changes. If the change is too small but adding one more coin fixes it, the app picks those coins itself. If all coins are already used and the change is still too small, the send is refused.
Name and balances on the home screen
Also open, not merged. After signing out and back in, the home greeted people without their name and every euro, dollar, card and IBAN balance read 0,00, even though nothing was lost. The screen was showing values it had not loaded yet.
Now the greeting stays empty until the name is known, keeping its height so the header does not jump. A balance that has not loaded shows as unknown instead of zero, while an account that is actually empty still shows zero. The card also stops adding 0 to the total before its first status read comes back.