Hello All - I'm attempting to enable my companies app to add credit card to Apple Wallet. Part of our app enables customers to generate new virtual cards on demand and I'm attempting to enable the ability to add these cards to the Apple Wallet. Everything seems to be working all the way to the final stage of the process where I get a PKPassKitErrorDomain systemCancelled and I can't seem to find any clues as to why the system is canceling. For context - I have the com.apple.developer.payment-pass-provisioning entitlement. I have both the Wallet and In-App Provisioning capabilities enabled in the App. I have defined a PKAddPaymentPassViewControllerDelegate class that implements both the generateRequest and didFinishAdding methods. I'm leveraging PKAddPaymentPassViewController in SwiftUI by using a UIViewControllerRepresentable implementing class that returns the view controller properly when makeUIViewController is called. I build a PKAddPaymentPassRequest object and ensure that it is properly filled with encryptedPassData, activationData, and ephemeralPublicKey. As a user I'm able to go to the virtual card view, open the instance of PKAddPaymentPassViewController, select the destination for the card, see the Add Card information. I get to the point where the view tells me it's contacting the card issuer and then I get an error message "Could Not Add Card - Try again later or contact your card issuer for more information" with a "Set Up Later" button. I then get the system canceled error. I should mention that I'm able to add these virtual cards manually via the Apple Wallet. The process works similarly but requires me to provided an OTP to conclude the process. This flow works and I have active cards in my wallet. I'm having a very hard time figuring out how to try and debug this issue further. The only error that the system returns is the system canceled notice. Any insight into where I might be missing something or how to debug the issue further would be greatly appreciated. Any thought on how I could debug this further would also be greatly appreciated. Thanks in advance - AYAL

Hi All - I'm working on a password autofill credential provider extension for an iOS app and experiencing some weirdnesses that I'm trying to figure out if it's my specific code or the fact that I'm using things like SwiftUI and Tasks. Instead of asking a lot of deep technical questions I figured I would start with some basic high level questions to figure out if I'm even in the ballpark: Is it ok to use SwiftUI in a password autofill credential provider extension? I know that I can use/embed a SwiftUI view in the ASCredentialProviderViewController but is there something wrong with doing that? Things like Widgets clearly heavely leverage SwiftUI but it's not so clear with password autofill credential provider extension. Is it ok to use concurrency in an extensions? For example when func provideCredentialWithoutUserInteraction(for credentialIdentity: ASPasswordCredentialIdentity) is called I'd like to start a Task to leverage some of our existing async/await functions. Given that extensionContext.completeRequest or extensionContext.cancelRequest can be called when the work is done it would seem that leveraging a Task should not be a problem but it's not clear from the documentation if extensions or the specific functions are concurrency friendly. I understand that we can do these things, ie the code works, but I'm more interested in a should we do these things or is doing these things potentially leading to my issues. Any suggestions, references, or general ideas are extremely welcomed. Thanks in advance - AYAL