-
Notifications
You must be signed in to change notification settings - Fork 504
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
Suddenly the source code stopped compiling into the release build #19371
Comments
I have exactly the same problem you mentioned about XCode 15 with the latest XCode, mac OS, and Visual Studio for mac. |
I couldn't wait for the fix so I renamed Xcode.app to Xcode1501.app, downloaded XCode 14.3.1, and followed the instructions at https://stackoverflow.com/questions/76958016/is-there-a-way-to-run-xcode-14-on-macos-sonoma. |
I have same issue migrating my bitrise workflow from xcode 14.3 to 15:
Build environment details (Apple Sillicon)
I have no problems building it on local workstation (Intel) xcode15/macOS 13.5 |
That is not true actually, if you try to make release build with linking it fails. |
And it looks to be fixed in xcode 15.1, works well on beta without applying workaround above. |
This happens because Xcode 15 has broken header files when it comes to compiling for armv7. See #19257 (comment) for more info. The fix/workaround is to remove Closing as a duplicate of #19257. |
@rolfbjarne For ARMV7s also build failed. So I just set only ARM64 and then build succeeded. |
It turns out that neither Mac nor xcode can be updated to support xamarin applications? Now I'm losing my time and money because I once trusted Microsoft... |
Suddenly the source code stopped compile release build's.
Even those source code commits that were compiled before.
There may have been some kind of software update.
Now the compilation of the release build ends with errors such as:
Changing used XCode to version 14.3.1 propagate another error:
Environment
Version information
Build Logs
FF.Mobile.iOS_Release_iPhone_Build_2023-10-29T14_03_52.4166050Z.msbuild.log
The text was updated successfully, but these errors were encountered: