-
Notifications
You must be signed in to change notification settings - Fork 4
feat: upgrade paykit to rc51 #697
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
ben-kaufman
wants to merge
13
commits into
master
Choose a base branch
from
codex/paykit-rc50-auth
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
5386569
feat: upgrade paykit auth to rc50
ben-kaufman c1a03c4
chore: rename changelog fragment
ben-kaufman 586fce5
fix: reconcile paykit auth failures
ben-kaufman f32b56f
test: cover private endpoint reconciliation
ben-kaufman b62fedf
test: use grant auth fixtures
ben-kaufman 0e0725a
fix: approve external Pubky grants
ben-kaufman 4befe20
fix: harden Pubky session recovery
ben-kaufman d383646
test: cover external auth client ID
ben-kaufman c23748a
fix: bound auth requester label
ben-kaufman 35816dd
fix: clear abandoned paykit sessions
ben-kaufman d90a6a9
fix: harden Paykit session recovery
ben-kaufman 2777d79
fix: reset forgotten Paykit sessions
ben-kaufman 57dc1cc
fix: preserve payment request history
ben-kaufman File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
4 changes: 2 additions & 2 deletions
4
Bitkit.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This branch hardcodes
privateSharingEnabled: false, but it is reached wheneverPublicPaykitService.pendingReconciliationMode()returns.removePublishedState, and that helper only looks atPublicPaykitService.publishingEnabledKey. In the private-only state (sharesPublicPaykitEndpointsfalse,sharesPrivatePaykitEndpointstrue) we therefore callsyncLocalReceiverMarkerwith both flags false, which makesisDiscoverablefalse and drivesPaykitSdkService.syncLocalReceiverMarkerintosdk.removePaykitReceiverMarker()— tearing down the marker for a user whose private sharing is still on. That state is reachable and deliberately supported:ContactPaymentsService.restorewritessharesPublicEndpoints=falsealongsiderestoresPrivateEndpoints=true, andrefreshPrivateOnlyPaykitReceiverMarkerexists in this same file purely to keep the marker published for it.markPaykitReconciliationPendingAfterFailedSignOutalso sets the public pending flag when only private sharing is enabled, so a failed sign-out routes exactly this state here, and the private reconciliation that runs afterwards never republishes the marker. Could we pass the real private flag here, for exampleprivateSharingEnabled: UserDefaults.standard.bool(forKey: PrivatePaykitService.publishingEnabledKey), or drop both arguments sosyncLocalReceiverMarker()reads the stored flags itself?