Repository navigation
bug: wallet backup retries every 10s while the homeserver is down #1746
Description
What happened?
While the Pubky homeserver is unreachable, the WALLET backup fails and retries every 10 s:
WARN [BackupRepo.kt:691] Retrying backup for: 'WALLET' in '10s' [AppError='code=transport_error, context=get_paykit_app_registry: fetch Paykit App Registry']
METADATA, ACTIVITY and WIDGETS back up normally during the same outage. The WALLET backup depends on fetching the Paykit App Registry from the homeserver, so a homeserver outage blocks it and the 10 s retry never backs off.
Expected behavior
Either the WALLET backup does not depend on the homeserver, or its retries back off while the homeserver stays unreachable.
Steps to Reproduce
- Use a wallet with a Pubky identity.
- Make the homeserver unreachable: block or hold traffic to it, for example through an HTTP proxy that blackholes the homeserver host.
- Trigger a wallet change that schedules a WALLET backup.
- The log repeats the line above every 10 s for as long as the outage lasts.
Logs / Screenshots / Recordings
Seen on master 1337f12 and on #1684 head fd617bf, during that PR's device gate.
Bitkit Version
master 1337f12
Device / OS
Pixel_9 emulator (Android 16), dev regtest/staging.
Reproducibility
Every time.
Activity
jvsena42 commentedon Nov 5, 2026
The WALLET backup includes the Paykit state, and the Paykit SDK keeps that state on the homeserver (
PubkySharedStateStorage). Exporting it takes a homeserver write lock and reads the encrypted state blob, so the backup cannot complete while the homeserver is unreachable. Removing the App Registry fetch (#1784, synonymdev/bitkit-ios#1219, both closed) only moved the failure toacquire Pubky write lock.The retries already back off. A device run with the homeserver blocked showed WALLET retrying at 10 s, 20 s and 40 s (doubling to a 5 min cap since #1552), while ACTIVITY, METADATA and WIDGETS kept backing up. The next attempt after the homeserver comes back succeeds. So this is working by design; the 10 s in the title is only the first retry. Making WALLET back up during an outage would need a paykit-rs export from local state, or a separate backup category for Paykit state.