-
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
BraintreeCore Fails to Build in Xcode 16 Beta 3 with Error: Type 'UIApplication' does not conform to protocol 'URLOpener' #1359
Comments
Hey @RGG-jayoung - Thanks for bringing this issue to our attention! The method signature for this changed in Xcode 16 beta 3 (apple dev docs diff here). Since changing to the new signature in our protocol would then produce the same error you are seeing in versions lower than Xcode 16 beta 3, we will need to under the hood call the both the old and new method. I've done some testing in Xcode 16 beta 3 as well as Xcode 15.4 and the change in PR #1360 seems to resolve both issues. If you'd like to pull down that branch and let us know if you're seeing the issue resolved on your end, please feel free. |
I also ran into this today, so I'm happy to see this getting addressed so quickly! |
Hey all - The fix for this issue has been released in version 6.23.0 of the SDK. Thanks again for bringing this to our attention! |
Update react-native-braintree-no-ui.podspec braintree/braintree_ios#1359
Braintree SDK Version
6.17.10 - 6.22.0
Environment
Both
Xcode Version
Xcode 16 Beta 3
OS Version & Device
iOS 18
Integration type
Swfit Package Manager
Development Processor
Apple Silicon (M-series chips)
Describe the bug
After updating to Apple's latest Beta 3, BraintreeCore fails to build due the following compiler error:
It seems that the
UIApplication+URLOpener.swift
conformance to URLOpener requires stubs to fulfill it's contract.To reproduce
Other steps taken:
Expected behavior
App target should build without issue like Xcode 16 Beta 1 and Xcode 16 Beta 2
Screenshots
The text was updated successfully, but these errors were encountered: