-
Notifications
You must be signed in to change notification settings - Fork 77
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
Braintree support for iOS 14/Xcode 12 #233
Comments
Hi @shivamkapur - can you help us with some more details on how we can replicate your issue, such as sending us your Podfile? |
@scannillo: FYI we're seeing this issue too, also with Cocoapods But From the Xcode 12 Release Notes:
Hopefully this is helpful, having problems finding a reason why only Braintree is giving us problems right now though. Nothing looks out of the ordinary in the Framework configuration. |
@scannillo - I'm using Xcode 12.0, Cocoapods version 1.10.0.rc.1. P.S. I've redacted others pods and retained all of the post install configuration.
|
Hello again. I made a sample app and included the |
@scannillo More info: Also happened to me regardless of cocoapods version. Existing project from xcode 11 migrating to xcode 12. iOS 12 Deployment target. |
Hello - for now, please use the workaround of setting We've reached out to our internal team who manages |
Also - can you share the exact |
I just ran into a similar problem. On a new project with this pod file:
Cocoapods 1.9.3 will give you the above errors. Cocoapods 1.10.rc.1 fixes the above errors, but adds a new one: If you select "update pod project to recommended settings" you get deprecation/unable to compile errors. If you then pod deintegrate/pod install... without letting xcode "fix" the project it works. Looks like there's lots of ancient objective C in this library. |
Circling back to this issue while we wait for our Magnes team to get back to us. For reference, this stack overflow post outlines the issue well. We excluded arm64 simulator architectures in our Braintree xcodeproj in a branch called
|
I've experienced this issue as well and for me the problem was with (mis)using custom build configurations with Cocoapods, I noticed that the build settings of all of my build configurations except The problem in particular was that To solve it I added the By configuring the Podfile properly and using the latest release of Cocoapods (1.10.0), the project was able to run out of the box after running |
We've released a fix for this in the |
This fix has been released in version 8.1.2 of |
@sestevens Any plans on bringing this back so we can build for arm64 simulators? |
👋 Our 3DS provider, CardinalMobile, is still blocking this for us. You can follow that thread here - braintree/braintree_ios#564. |
@scannillo Pointing to a specific example we can see that in the Braintree.podspec.json file for 5.4.3 they have these lines. This is what blocks us from migrating to SPM for other frameworks. Please help. |
Hi @abhishek-ios-stockX - please open a new GitHub with more details! |
Integration Details (please complete the following information):
Describe the bug
I'm unable to compile BraintreeDropIn and Braintree(it's Dependancy) on Xcode 12.0
I get the below error -
Showing Recent Messages
In
/Users/shivam/Desktop/iOS/platform-x-
os/Pods/Braintree/BraintreePayPal/PayPalDataCollector/Risk/libPPRiskMagnesOC.a(PPRMOCMagnesConstants.o), building for iOS Simulator, but linking in object file built for iOS, file '/Users/shivam/Desktop/iOS/platform-x-ios/Pods/Braintree/BraintreePayPal/PayPalDataCollector/Risk/libPPRiskMagnesOC.a' for architecture arm64`I am aware of a "workaround" of adding
arm64
inEXCLUDED_ARCHS
, while it does work I think having Xcode 12 support would really help.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Project should compile successfully..
The text was updated successfully, but these errors were encountered: