Skip to content
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

PKPaymentAuthorizationControllerExportedObject authorizationDidFinishWithError #117

Closed
janhalousek opened this issue Apr 18, 2015 · 11 comments

Comments

@janhalousek
Copy link

Hi,

I am seeing objc_msgSend crash in [PKPaymentAuthorizationControllerExportedObject authorizationDidFinishWithError:] occurring on production.
Seems like the crash comes after successful BTPaymentMethod creation, just moments after dismissing PKPaymentAuthorizationViewController.
The flow is integrated using BTPaymentProvider.

Do you have any similar issues, or any idea how to prevent this from happening?
Thanks

@mickeyreiss
Copy link
Contributor

Hi! Are you seeing this in development or via crash reports in production? Any correlation with iOS base SDK version or runtime version?

We've been seeing reports of this issue intermittently but have not been able to narrow it down between our sdk's usage of PassKit and PassKit itself.

@janhalousek
Copy link
Author

Hi,
thanks for your reply. We see it only in reports from production, no correlation with iOS versions, failing on 8.1, 8.2 and 8.3. Could my usage of your SDK be the problem?

I understand, please keep me updated if anything new arises.

We might consider implementing the flow via direct use of PassKit. If we do, I'll let you know if any correlation arises.

@mickeyreiss
Copy link
Contributor

We're curious to find out how that goes! Feel free to re-open this issue if our usage of the PassKit APIs is at fault for the crasher.

@chamarapaul
Copy link

I'm seeing this issue in my production crash logs as well, and I'm using the PassKit integration style documented here: https://developers.braintreepayments.com/ios+ruby/guides/apple-pay/client-side

There are a couple of Apple bug reports filed too:
http://www.openradar.appspot.com/19767271
https://openradar.appspot.com/20189448

Maybe reopen this issue? Let me know if I can provide more info (logs, etc.)

@burnto
Copy link
Contributor

burnto commented Apr 28, 2015

Thanks @chamarapaul.

The Apple bug reports do further indicate that this is likely a PassKit bug. I'm fine re-opening to indicate that we believe resolution is waiting on PassKit.

@janhalousek are you still seeing this issue with the direct PassKit usage?

@burnto burnto reopened this Apr 28, 2015
@janhalousek
Copy link
Author

@burnto Unfortunately we don't use the direct PassKit integration yet.. I'll keep you informed in case we do

@glentregoning
Copy link

FYI I opened a radar for this an it was marked as a duplicate by Apple which indicates to me this is an Apple Issue. See http://www.openradar.appspot.com/19767271

@mthole-old
Copy link

I discussed this error with Apple engineers at the WWDC Labs. They confirmed that it was indeed an Apple issue, and that it should be fixed in iOS 9. I don't expect it in an 8.x, unfortunately.

@mthole-old
Copy link

I was able to (fairly grossly) work around this issue by explicitly leaking the PKPaymentAuthorizationViewController once I was done with it. If you do so, make sure you clear out the delegate too.

@burnto
Copy link
Contributor

burnto commented Aug 5, 2015

Since we have some evidence this is an Apple issue, I'm closing this. Thanks everyone for reporting and helping us figure this out.

@burnto burnto closed this as completed Aug 5, 2015
@moughxyz
Copy link

@mthole what do you mean by explicitly leaking? Did you go into the Braintree framework itself and modify the source?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants