-
Notifications
You must be signed in to change notification settings - Fork 514
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
[Meta] Xcode 14.1 Support #16659
Comments
I've been having an absolute nightmare with the build tooling for MAUI over the last week and a half. We were able to produce dotnet 6.0 MAUI iOS ipa that could be pushed to App Store about 10 days ago. Then we discovered a need to look at dotnet 7.0 MAUI (still RC2 at that stage) and ever since then I've been able to produce packages and run builds on simulators and devices, but when I submit to App Store for TestFlight distribution the package is rejected due to Bitcode being included for the nuget packages we are using. We ran into this problem initially with the dotnet 6.0 MAUI iOS packages and eventually discovered that using -p:EnableAssembyILStripping=true with the publish command would remove the bitcode and allow us to publish successfully to App Store. Since I started using the dotnet 7.0 build tooling that property has completely stopped having any effect. I'm going to have a look through all the issues on this repo and start adding in stuff that I'm seeing at the moment, but keen for a comment on what combination of tooling I can use to successfully use to publish an ipa to App Store for distribution (including nuget packages because the issue doesn't appear if there aren't any packages included) |
For macOS the package failed to install (EDIT: for some reason it installed on the second try). For iOS the share extension could not be compiled in debug, I get this:
|
@ivanicin any chance you can provide a bin log (https://github.com/xamarin/xamarin-macios/wiki/Diagnosis#build-logs) and open a new issue about this? |
@dalexsoto I have updated today Visual Studio, as the version is newer I guess that you have changed something so I did not get that error anymore. EDIT: actually the update was to the old version, but after installing the new version again it seems to work... |
This should have been included in 14.1, but the error remains when building with it and submitting to the App Store. |
@ivanicin latest visual studio for mac was released on November 8-th, i think it doesn't have the fix yet. Or u have a new VS update? |
@PavloLukianets you have the links in this issue description… |
Severity Code Description Project File Line Suppression State Warning Still producing with yesterday's update VS 2022 v.17.4.2 |
+1 to above comment. For now I'm avoiding the issue by using Xcodes program for Mac (and assigning Xcode 13.3 as current active version), but would much prefer the latest versions of VS and Xcode to be compatible and run together. :) |
@Saigronas How do you have Visual Studio version ? I have Xcode 13.3 and Visual Studio 17.4.2 and I have this error: |
Is there an ETA on releasing 16.1 with Visual Studio for Mac 2022? |
iOS16.2RC2 just out, I'd expect formal release in a week or two, so as a new version of XCode. Hope 14.1 support could be released before it's already outdated... |
Unfortunately I am also running Visual Studio 14.4.2 and XCode 13.3. I do however have XCode 14.1 installed on the mac at the same time, perhaps that is related to me not receiving the same errors as you have. |
Xcode 14.2 is here :( |
Xcode 14.1 has been released to the stable channels as of today. Xcode 14.2 is being worked on as we speak. I'll open a separated issue for this one. Thank you all for your patience. |
Apple released Xcode 14.1 on November 1st, 2022, we have what we believe are the final builds for you to test on Xamarin.
Update: Nov 24, new builds.
For MAUI we are still producing builds compatible with Xcode 14.1 so we recommend using Xcode 14.0 for now. If you updated to Xcode 14.1 and want to go back to Xcode 14.0 you can download Xcode 14.0 from the downloads page in the Apple Developer Portal and continue to use it.
We will keep this issue updated as we go to have the final builds declared.
Thank you for your patience!
The macios team!
The text was updated successfully, but these errors were encountered: