-
Notifications
You must be signed in to change notification settings - Fork 996
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
Push provisioning take 2 #1396
Push provisioning take 2 #1396
Conversation
09e08f4
to
f49f799
Compare
The code looks good, though I have some FUD around how App Review will treat references to PKAddPaymentPassViewController in apps that don't have the correct entitlement. We might want to send this through App Review at least once before we ship it out in an SDK. Can you fix the errors in the CI build? |
Ooh, good point on the app warnings. I'll try and submit something to the app store this week. Fixed the build issues in the meantime! |
Sounds good! I’m cool with this going in once we’ve tried that. |
* Fix Catalyst build on Xcode 14 * Fix Swift 6 compile error * Update CHANGELOG * Cleanup
Summary
This is a second take at the functionality in #1052.
PKAddPaymentPassViewController
.STPPushProvisioningContext
, a stateful class that is used to handle fetching an ephemeral key from a user's server and then using that key to call the aforementioned API.STPFakeAddPaymentPassViewController
, a UI class that is API-compatible withPKAddPaymentPassViewController
but can be more easily used for testing and debugging.Motivation
Enable push provisioning
Testing
Added snapshot tests for the new API code.