-
Notifications
You must be signed in to change notification settings - Fork 519
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 15.3/4 Support for .NET 8 and MAUI #20257
Comments
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. |
Just chiming in to say I've updated xcode and my dotnet version and all is working perfectly. I verified the SDK crash in my maui app & then performed the following steps and all is working smoothly:
Thanks for providing this thread and keeping us updated 😊 |
@Axemasta , this did not work for me I installed .Net 8.0.302. it still failed on Rider 2024.1.3. Has anyone else tried?? |
Are you using a 'global.json' file to pin the latest version? here is the contents of mine. {
"sdk": {
"version": "8.0.301"
}
} And from the rider terminal if I run |
I'm running XCode 15.4, Rider 2024.1.3, .NET 8.0.302, all workloads updated (ios, android, maui). All works fine |
There must be something special you have to do. I upgraded to .NET 8.0.302 / 8.0.6 and now the simulator doesn't work on iOS. It was working for me on 8.0.101 / 8.0.1 this morning with Xcode 15.3. The only reason I updated was because I watched a video by the NET MAUI team and they said this was fixed. I assume I have SR5, but have not way to validate that as far as I know. The video said 8.0.40 SR5 and my output says 8.0.40. Not sure if that is the same thing. If that is, then please advise on how to get this to work. I am using it on MacOS on a MacBook pro 2021 with the latest MacOS release version Sonoma. |
Please file a new issue, since it might very well be something unrelated. |
Done: #20734 |
I'm still having issues with this. Specifically with Devexpress MAUI charts, but the devexpress team says they can't resolve this since it's a .net/maui issue with the simulator. Error log: ================================================================= Native Crash Reporting ================================================================= Got a SIGBUS while executing native code. This usually indicates ================================================================= ================================================================= Native stacktrace: ================================================================= Call Stack ================================================================= Basic Fault Address Reporting ================================================================= Call Stack All components updated to latest which should not have anymore simulator issues according to Microsoft MAUI team.
All workloads updated on Win and Mac
|
According to the releases page, this issue can be marked as closed. https://github.com/dotnet/maui/wiki/Release-Versions |
The current release works with Xcode 15.3/15.4, but we haven't released bindings for new APIs added Xcode 15.3/15.4 yet, which is also what this issue is about. |
@rolfbjarne When do you intend to release bindings for new APIs added in Xcode 15.3 / 15.4. I have a 3rd party library written with iOS 17.4 and I cannot get the app to publish. This is a very major problem for my app. |
@rolfbjarne sorry but i think this issue is really mandatory. Actually if Apple determine that we should compile with the last 2 xcode versions as minimum we cannot do anything. And/or if we have a customer that wants to publish in the alternative store that Apple brings in February... we cannot do it with net4ios/maui. |
Could you please provide an estimated month for the 15.3 and 15.4 bindings releases? @rolfbjarne |
What we need to know is the average time for the bindings releases each time Apple publish a new version. This can help us to schedule the implementations in our software. There was a time when bindings used to be published the day after Apple released them |
The support for Xcode 15.4 in .NET 8 has been merged into the next release of VS so it will be available in the following weeks. .NET 9 Preview 7 will also contain Xcode 15.4 support. |
Will this make it into a final release of VS for Mac? Also, I know this is the wrong thread, but what about support for interface builder for VS Code? |
That's tracked here: microsoft/vscode-dotnettools#571 |
No more updates are planned for VS for Mac. |
That said nothing stops you doing a ‘dotnet workload update’ in your mac that has VSMac installed once the new version of .NET for IOS is released |
Can someone explain to me why I suddenly get this warning? What is Microsoft.iOS version 17.5.8018 and how did I get it? Where are the release notes for it? Is it safe to update to XCode 15.4 now? |
I use XCode 15.4 with no problem |
Thank you. I also updated to Xcode 15.4 and it work's fine. |
Or, use XCodes 👍 |
There was a miscommunication on our side; the iOS team thought the release was going out next week, but then it went out yesterday instead, so the release notes weren't ready. They've been published now: https://github.com/xamarin/xamarin-macios/releases/tag/dotnet-8.0.1xx-xcode15.4-8018 And yes, it's safe to update to Xcode 15.4 now. |
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/4 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.At the moment we have no record of any outstanding issues that prevents Xcode 15.3/4 from working with the latest release of .NET 8 + our workloads (except that none of the new APIs in Xcode 15.3/4 will be available until we release support specifically for Xcode 15.3/4).
However, if you need to download Xcode 15.2 you can get it from the Apple Developer portal.
Known issues
iOS 17.4 Simulator crashes
ICU causes crash on iOS 17.4 simulatorWorkaround: 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 ICU causes crash on iOS 17.4 simulator runtime#98941.This issue has been fixed in .NET 8.0.300. There's no need to update the iOS workload to get the fix, only .NET itself.
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: