-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
SDK Not Supported by Compiler (Xcode 16) #13727
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
Based on #13731, our testing is showing that Xcode 16 works with the zip distro. Please check that you're only using binaries from 11.2.0 and the instructions are followed. We'll need a fully reproducible example to help. |
Hey @johnfrancmartin. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically. If you have more information that will help us get to the bottom of this, just add a comment! |
Since there haven't been any recent updates here, I am going to close this issue. @johnfrancmartin if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this. |
Description
Receiving the following issue with latest .xcframework release.
Reproducing the issue
Attempt to build using XCFramework zip inside Xcode 16.0.
Firebase SDK Version
11.2
Xcode Version
16.0
Installation Method
Zip
Firebase Product(s)
Analytics, Authentication, Crashlytics, Database, Messaging, Remote Config, Storage
Targeted Platforms
iOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved
Expand
Package.resolved
snippetReplace this line with the contents of your Package.resolved.
If using CocoaPods, the project's Podfile.lock
Expand
Podfile.lock
snippetReplace this line with the contents of your Podfile.lock!
The text was updated successfully, but these errors were encountered: