[META] Xcode 15.3/4 Support for .NET 8 and MAUI #20257
Comments
dalexsoto
added
macOS
|
I have a problem. I can run just fine in the iOS simulator, but when I try to run it on a physical ipad with xcode 15.3 and iOS 17.4 it crashes with the error code below. I posted a question on Microsoft Learn, but was guided here. Could you confirm that this is an issue with Maui and xcode 15.3/iOS 17.4? Severity Code Description Project File Line Suppression State |
|
@Excubitor that's not something we know about. Can you please file a new issue here and we'll have a look. |
|
There are surely some problems related to XCode 15.3 and ios 17.4. But I've been able to build an archive (not publish directly to ipad, that doesn't work for 15.3/17.4). I have tried added nugets and it still worked. I seem to run in to problems however when using connected services. I use connected services to connect to an existing soap-api. I haven't recieved "Undefined symbols for architecture arm64: "_SSLCopyALPNProtocols", referenced from" yet but I do get an error "system.NotsupportedException: The given paths format is not supported at System.Security..."" when adding one of the soap api:s as a connected service. |
|
When will Xcode 15.3 be supported? (Xamairn.iOS) |
|
I am also getting an error when I try to publish, but it is different from the one above. Is this because of the 15.3 support? Here is the stack trace from the publish output. Or at least the first group. I can include the rest if needed. Every line is prefixed with this first line. I figured I'd leave out the repetition. `/usr/local/share/dotnet/packs/Microsoft.iOS.Sdk/17.2.8043/targets/Xamarin.Shared.Sdk.targets(1214,3): error MSB4018: The "AOTCompile" task failed unexpectedly. [/myproject.csproj::TargetFramework=net8.0-ios] |
|
bump. xcode 15.3 has been out (in beta form at least) since late january. how many months does it take to make things compatible? people's trust in these components has already been shaken with the transition to dotnet maui, now this is dealing a killer blow. |
Any particular reason you can't use Xcode 15.2? |
|
migrating a xamarin forms app to maui, there are enormous amounts of bugs and issues to resolve. some of them were only resolved when moving to 15.3. In any case, you shouldn't be shaming users for using something that has been released several months ago when the deal with these components was that whenever a new release rolled out there'd be an update within a few days. How can people expect to keep using this platform if breaking changes are seemingly unaddressed for several months? |
Hello! Thanks a lot for being a member of our community, Xcode 15.3 has been somewhat a major release (even if it is a minor version bump) it has come with some complications that has implications down in our stack, we have been working on getting support for it but as you have noticed it has taken us time to get it right; it is not our intention to shame anyone for using "x", we are just pointing out that at this time Xcode 15.3 is not something we support and that you are able to use Xcode 15.2 in the meantime, even Apple still supports uploading apps as far as Xcode 14.x and will enforce Xcode 15 until April 29, 2024. I strongly encourage you to use Xcode 15.2 for now as it is the official supported Xcode for both MAUI and .NET for iOS/macOS, as mentioned we are working to support the latest Xcode and once we are are ready to ship with the quality our community expects from us we'll ship it. |
|
@mmiller-d8 Did you fix this error? I have this error also. I have downgraded XCode 15.3 to 15.2 but that does not fix this issue (by default). Is there something else that needs to be done? |
|
Um... I just upgraded to 15.3 and publishing worked. I rebooted and tried again. First time, I got an error without any messages. Tried again and it worked. Cleaned and rebuilt, and it worked. Since I downgraded manually and then upgraded from the App Store, is it possible that the 15.2 libraries are still there and Visual Studio is using those? Also, not having gotten a response on this one, I created a new issue for this specific error. It is at #20387 |
|
What bugs were there in 15.2 that were fixed in 15.3? All I can say is, we've got a very complex app that touches, bluetooth, camera, file management, sharing, Skia, lottie, online/offline, video playback, custom video handling (custom logic for things like our own subtitle and playback handling), image processing, email and god knows what else. This all builds absolutely fine on 15.2 🤷 (Note: we don't use MAUI) |
|
I didn't keep track of the specifics as it would be a waste of time to detail issues that had been solved by simply moving to the next production version of the platform... and that's really not relevant. We expect microsoft to provide support within a reasonable timeframe - they're keeping quiet months down the line, this looks very bad. |
|
15.4 is already in beta stage, and there's still no light at the end of the tunnel for 15.3. |
|
Unacceptable response times... |
|
Can't publish MAUI as well.
|
Try this: #20406 (comment) |
|
xcode 15.4 already in release candidate mode. any light at the end of this tunnel? |
|
15.4 is released (not beta / RC anymore) Why does .NET8 not emit a warning that the XCode SDK is not compatible? I've just spent 8 hours trying to understand all sorts of bizarre issues with an iOS build and weird native stack crashes.... and it turns out that XC 15.4 with Visual Studio Latest is simply not compatible right now. You could maintain this compat list centrally and have the build system keep a locally cached copy for doing its compat checks. |
dalexsoto
changed the title
|
Also, don't download XCode directly. Use the "Xcodes" tool from https://github.com/XcodesOrg/xcodesapp/releases/ which gives you a clean UX to manage your Xcode installations (side by side) with: 
|
|
My app no longer crashes within the first second or two of execution after:
iOS 17.5 simulator (even though compiled with 15.2 SDK) is still crashing. Furthermore, Apple App Review rejected my app for these crashes (and they reviewed it on iOS 17.5). So it seems .NET is broken right now on iOS 17.5...? |
|
@nbevans please file a new issue with what you are seeing, we are working to bring support as soon as possible. |
|
My issue is the same as in this thread dotnet/runtime#98941 I have a WKWebView. I focus a text box. It crashes. The Apple App Review tested the app with 17.4 (crash dump doesn't indicate whether it was a simulator or not, but I assume it was?) |
|
Same for me. Simulator with iOS 17.4 crashes when UITextField got focus. The 17.2 works fine. |
|
Do we have an update on when this is going to be available |
|
Anyone had any luck with upcoming MAUI preview builds for this issue? |
|
Yes the apps are crashing during App Review too, from what I can tell. I feel like everyone thinks this issue only affects the iOS simulators Our app is just a WKWebView. It doesn't even do very much and we havent changed any code compared to last month. Last month it was fine, but this month they are using 17.4 for App Review and it's crashing. Our app was built for release via AzureDevOps build agent using Xcode 15.2. At first we thought it was a trimming linker issue but it seems that it isn't. Usually with those you'd see LinkedAway in the god awful iOS crash dump; but not this time. |
|
Having checked this morning I can see that a new test build of our app built on AzureDevOps with Xcode 15.2 AND with the following adding to the project file... appears to have resolved the issue but until I put it thru their App Review I won't be 100% sure. To be clear: this was mandatory to get the app to work at all. Without this in the project file - even a build produced with AzDevOps agent with Xcode 15.2 won't run on iOS 15.8.1 (that's just an old iPad I have lying around to do smoke tests like this with) I'm guessing it is the InvariantGlobalization=true that does the heavy lifting of fixing the issue. And maybe the _Lib prefixed properties too. The FixMonoLinkMode stuff appears to only be necessary to get it working for local iOS Simulators. |
Adding this to the iOS csproj allowed running on the local simulators running xcode15.4, iOS17.5 |
|
The .NET 8.0.5 servicing is out and the fix for dotnet/runtime#98941 is in and should unblock Xamarin/MAUI to upgrade to Xcode 15.3. FYI: @dalexsoto @rolfbjarne @jfversluis |
Tried to update .Net on my mac and got new Calling 'dotnet workload restore' now gives an exception after that Used Xcode 15.3 and the latest VS for mac update (today). |
|
I don't want to beat a dead horse here, but I really hope that the .net product managers are aware that this is a very serious issue that is causing people to lose confidence in the product. This isn't the only quality issue I'm facing. I'm still working on Maui issues that were caused by the .net 8 upgrade, which, in my opinion, should have gone to the top of the issue list right behind this one. Instead, they went into the backlog with the thousands of issues already there that aren't being resolved. I don't know if it's an issue of funding, but taking four - going on five - months to support the now previous version of Xcode with almost no communication is really bad. It, along with all the other issues, paints a picture that cross platform development doesn't really have the resources or commitment needed for companies to bet their businesses on it. If you're not careful, this will go the way of AppCenter. Or Visual Studio for Mac. Too many bugs and not enough resources to fix them. And then calling "time of death" for VS for Mac when the replacement is nowhere near ready for prime time. All of this causes developer confidence to drop. Once it drops enough, they will leave. I understand that Maui isn't a revenue generator. It's open source and it's free. But to treat it like a cost center will ultimately hurt Microsoft's revenue generators. If I abandon Maui because of a lack of confidence, it's only a matter of time before I abandon C# in general. And then Azure, which also means SQL Server and Windows. I'm not trying to beat you guys up. I have worked in software dev for a very long time. I'm just saying that I hope your product managers are getting the message. |
|
@elamaunt, |
Thanks! It fixed the issue. Checked simulator iOS 17.4 and it works fine with XCode 15.3 and Net Sdk 8.0.3 on my Net.8.0-ios project. |
Hello!
Xcode 15.3 was released on March 5, 2024. We are in the process of updating our bindings and our infra in order to support this release.
As of the time of this post, Xcode 15.3 is not recommended to be used with our .NET MAUI or Xamarin SDKs so our advise is not to install it just yet and keep using Xcode 15.2 for the time being.
If you need to download Xcode 15.2 you can get it from the Apple Developer portal.
Known issues
iOS 17.4 Simulator crashes
Workaround: Use Xcode 15.2. If you really need to use Xcode 15.3 then either use iOS Simulator 17.2 or the workaround provided in dotnet/runtime#98941.
We'll keep this post updated as we learn more.
Thank you!
-The macios team
The text was updated successfully, but these errors were encountered: