-
Notifications
You must be signed in to change notification settings - Fork 295
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
Apple Pay entitlement is required even when not used #60
Comments
@sergey-sportsetter Is this message a warning or an error that blocks submission to the app store? I can confirm that if you have not explicitly implemented Apple Pay, the Apple Pay code within the SDK will not run. |
This is an automated warning I got immediately after upload to iTunes Connect. It's currently in review, so I'll be sure to let you guys know how it goes |
It had no effect on the review - the update went through, as expected |
Thanks for reporting back. If anyone experiences further problems with this, we can try to use the preprocessor to compile out any Apple Pay related code. |
Also using the v.zero 3.4.0 Drop-in UI, we got the above warning on submission, and then got a Review feedback request: "Does the app currently have Apple Pay functionality? If so, please provide detailed steps on where to find the Apple Pay functionality in the app." I assume the comment, 'if you have not explicitly implemented Apple Pay...', refers to whether or not we have switched it on in our Braintree processing settings? |
and, if we have a build of the app without the in-app-payment entitlement, what happens if we later turn it on at Braintree? Will the deployed apps break, or will they detect they don't have the entitlement and simply not offer that choice to the user? |
No, what this refers to is whether you have actually implemented Apple Pay in your mobile application. It requires specific code and configuration (entitlements).
To clarify, Apple Pay is enabled via configuration in the Apple Developer Center, and the entitlement is set via Xcode in a plist that is part of the app bundle. So the entitlement is something that you enable/disable for a particular build of your app. It is not a Braintree setting. Separate but related is your Braintree configuration of whether Apple Pay is enabled for your Braintree account. You need to enable and set up Apple Pay in your Braintree account first in order to obtain the CSR that you'll use to set up Apple Pay in the Apple Developer Center, which in turn is necessary to set up the entitlement for your app. If you integrate via If you integrate via Either way though, enabling Apple Pay in your Braintree account should not affect existing deployments of your app that do not use Apple Pay. |
Hi @mickeyreiss , as @jamesrgrinter I just have received an email from apple asking for the 'Missing apple-pay feature', due to this issue:
I've already answered them and my app is in review now, but could you guys consider this to try to exclude this 'flag' from the lib by default somehow. Best |
@jerez Thanks for the feedback. We'll work on a fix that makes it simple to exclude the |
have same issue with iTC — upload build and get mail from apple. Do not use any of ApplePay set up or usage code, xcode's capabilities and developer.apple.com do not have ApplePay enabled. |
+1 |
Is this issue getting fixed soon? |
Yes we are working on a fix and will update here shortly. |
Hi all, apologies for the delay. We have a solution for this that we're doing some final verification on. Expect a commit and an update here soon. |
Starting in e142286 (which will be part of a tagged release in the next few days), Apple Pay is only part of the Braintree iOS build when the optional The basic tests are pretty simple, if a little coarse, and just use Thanks all! |
Hi everybody... i added to my podfile: pod "Braintree" and i have this error: [!] Unable to satisfy the following requirements:
Can you help? |
Hi @lupugabriel - as noted in #83, this was an inaccuracy in the README that I fixed in 36e90bf. Let us know if |
Closing as this is resolved in the latest release. Feel free to re-open, if you experience any continued issues with |
Using Braintree 3.4.0, v.zero drop-in UI
Upon submission to Apple, got the message:
Previously, this entitlement was not necessary
The text was updated successfully, but these errors were encountered: