fix(dashpay): resync before failing an accept whose request isn't in memory#829
Merged
QuantumExplorer merged 1 commit intoJul 16, 2026
Merged
Conversation
…memory Accepting a pending contact request resolved the live ContactRequest handle from the SDK's in-memory state, which is per-session — but the pending row the UI renders comes from SwiftData, which persists across sessions. Tap Accept before this session's first DashPay sync pass has repopulated the in-memory list (fresh launch, or the 15s background loop hasn't landed yet) and the lookup missed, surfacing the bogus "Contact request not found" error for a perfectly real request. On a miss, run a dashPaySyncNow pass and retry the lookup once; only a miss after a fresh pass is a genuinely revoked/consumed request. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Accepting a pending contact request could fail with "Contact request not found" for a perfectly real request (QA repro: tap Accept on a pending row shortly after launch).
Root cause: the pending rows the Contacts screen renders come from SwiftData, which persists across sessions — but
acceptContactRequestresolves the liveContactRequesthandle from the SDK's in-memory state, which is per-session and only populated by a DashPay sync pass (15s background loop / explicitsyncNow). Tapping Accept before this session's first pass lands → in-memory miss → bogus error.Fix: on a miss, run one
dashPaySyncNowpass and retry the lookup; only a miss after a fresh pass throwsrequestNotFound(genuinely revoked/consumed). The lookup is factored into a helper so both attempts share the exact same read.Test plan
dashpaysimulator build (arm64); installed on QA-iPhone16🤖 Generated with Claude Code