-
Notifications
You must be signed in to change notification settings - Fork 4k
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
🐛 [firebase_app_check] Semantic Issue (Xcode): 'new' is unavailable
after upgrading xcode
#10694
Comments
same issue. |
Hi @mdddj, is this error only on Xcode 14.3? or did you get this error before the upgrade? |
Yes, it didn't appear until xcode was upgraded. |
Same issue here |
Will this "stick" for the compile process? Or does compiling ignore a manual change like that? |
same here |
Same issue here since upgrading xcode:
|
Happened to me after I upgraded Xcode. |
My current workaround is to switch to older version of Xcode. And here is how: https://stackoverflow.com/questions/14756026/how-to-downgrade-xcode-to-previous-version |
Same issue here - I can confirm this occurred after updating to the latest Xcode version 14.3 (14E222b). |
This tmp workaround will get your app to compile while we wait for an update |
Semantic Issue (Xcode): 'new' is unavailable
after upgrading xcode
I attempted to reproduce this locally but I'm running into an issue with cocoapods. Similar to CocoaPods/CocoaPods#11808 (comment) Labeling for further investigation from the team. cc @Lyokone
|
This has to do with flutter/flutter#123903 . Solution (for now...) is to upgrade min deployment target for all Pods to
The issue is, once you do this and get past the CocoaPods error, if you depend on |
In the meantime, I'm personally just downgrading to XCode 14.2 until Flutter + CocoaPods update to not require these workarounds. Easier than trying to play whack-a-mole w/ different libraries 😄 |
I also ran into this error after upgrading... updating the Minimum Deployments - iOS value from 8.0 default to 11.0 or higher for the 'leveldb-library' Pod - got rid of this error in my case. NOTE: This manual setting change is no longer required as there has been an updated to the cocoapod that sets the default value to a Minimum Deployment version of 11.0 |
Every time there's an update from Xcode we are forced to download it (because we can't run the app on our device), it's at least 7GB large, it's slow, AND it causes problems every time. Apple should be more careful about doing this. A temporary solution is to replace those |
After working around the issue with Changing
|
Flutter issued a new release supposed to fix this: https://groups.google.com/g/flutter-announce/c/9qZL8GOVNb4 |
After updating to version 3.3.10, there were no noticeable changes. |
The error with firebase_app_check is still present - setting the 3 instances of 'new' to 'alloc' as mentioned previously will allow the build to complete. This latest update to Flutter 3.7.10 fixes another bug that would stop the 'flutter build ipa' command from completing successfully. |
it still happens with Flutter 3.7.10 |
Same issue |
when can we expect an update? |
It has been released as part of firebase_app_check version 0.1.2+1 |
The text was updated successfully, but these errors were encountered: