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
{{ message }}
Repository navigation
feat: retry failed paykit receipts in the background #1941
A failed Paykit receipt is tried again only once per app launch, or when the user taps Retry. After a short homeserver outage the payment keeps showing "Receipt failed" until the user notices and taps Retry or restarts the app, and most users won't know what a receipt is.
Retry failed receipts in the background on the periodic Paykit refresh, with a backoff (each refresh at first, then spaced out), and stop only on a permanent failure such as the contact being removed or blocked. Manual Retry can then move to activity details for a receipt that keeps failing.
Also from the iOS device gate (synonymdev/bitkit-ios#1335 (comment)): a manual Retry right after an outage issued the receipt at once, but the drain after it recorded no delivery, likely because the contact was still inside its retry backoff from an earlier failed message; the next periodic refresh delivered it about 48 s later. Android's second Retry looked the same. The follow-up should make a user-triggered Retry bypass or reset that contact's backoff if the SDK allows it.
Activity
ovitrif commentedon Nov 16, 2026
Also from the iOS device gate (synonymdev/bitkit-ios#1335 (comment)): a manual Retry right after an outage issued the receipt at once, but the drain after it recorded no delivery, likely because the contact was still inside its retry backoff from an earlier failed message; the next periodic refresh delivered it about 48 s later. Android's second Retry looked the same. The follow-up should make a user-triggered Retry bypass or reset that contact's backoff if the SDK allows it.