Skip to content
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

Closed
dalexsoto opened this issue Mar 6, 2024 · 59 comments
Closed

[META] Xcode 15.3/4 Support for .NET 8 and MAUI #20257

dalexsoto opened this issue Mar 6, 2024 · 59 comments
Labels
iOS Issues affecting iOS macOS Issues affecting macOS
Milestone

Comments

@dalexsoto
Copy link
Member

dalexsoto commented Mar 6, 2024

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


We'll keep this post updated as we learn more.

Thank you!

-The macios team

@Excubitor
Copy link

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
Error clang++ exited with code 1:
Undefined symbols for architecture arm64:
"_SSLCopyALPNProtocols", referenced from:
_AppleCryptoNative_SslGetAlpnSelected in libSystem.Security.Cryptography.Native.Apple.a(pal_ssl.c.o)
"_SSLCopyDistinguishedNames", referenced from:
_AppleCryptoNative_SslCopyCADistinguishedNames in libSystem.Security.Cryptography.Native.Apple.a(pal_ssl.c.o)
"_SSLCopyPeerTrust", referenced from:
_AppleCryptoNative_SslCopyCertChain in libSystem.Security.Cryptography.Native.Apple.a(pal_ssl.c.o)
_AppleCryptoNative_SslIsHostnameMatch in libSystem.Security.Cryptography.Native.Apple.a(pal_ssl.c.o)
"_SSLCreateContext", referenced from:
_AppleCryptoNative_SslCreateContext in libSystem.Security.Cryptography.Native.Apple.a(pal_ssl.c.o)
"_SSLGetNegotiatedCipher", referenced from:
_AppleCryptoNative_SslGetCipherSuite in libSystem.Security.Cryptography.Native.Apple.a(pal_ssl.c.o)
"_SSLGetNegotiatedProtocolVersion", referenced from:
_AppleCryptoNative_SslGetProtocolVersion in libSystem.Se FlyoutPageSample

@rolfbjarne
Copy link
Member

@Excubitor that's not something we know about. Can you please file a new issue here and we'll have a look.

@Excubitor
Copy link

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.

@gwise-vision
Copy link

When will Xcode 15.3 be supported? (Xamairn.iOS)

@mmiller-d8
Copy link

mmiller-d8 commented Mar 27, 2024

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]
error MSB4018: System.AggregateException: One or more errors occurred. (One or more errors occurred. (One or more errors occurred. (An error occurred trying to start process '/usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-arm64.Cross.ios-arm64/8.0.1/Sdk/../tools/mono-aot-cross' with working directory 'MySolutionDirectory'. No such file or directory))) (One or more errors occurred. (One or more errors occurred. (An error occurred trying to start process '/usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-arm64.Cross.ios-arm64/8.0.1/Sdk/../tools/mono-aot-cross' with working directory 'MySolutionDirectory'. No such file or directory))) (One or more errors occurred. (One or more errors occurred. (An error occurred trying to start process '/usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-arm64.Cross.ios-arm64/8.0.1/Sdk/../tools/mono-aot-cross' with working directory 'MySolutionDirectory'. No such file or directory))) (One or more errors occurred. (One or more errors occurred. (An error occurred trying to start process '/usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-arm64.Cross.ios-arm64/8.0.1/Sdk/../tools/mono-aot-cross' with working directory 'MySolutionDirectory'. No such file or directory))) (One or more errors occurred. (One or more errors occurred. (An error occurred trying to start process '/usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-arm64.Cross.ios-arm64/8.0.1/Sdk/../tools/mono-aot-cross' with working directory 'MySolutionDirectory'. No such file or directory))) (One or more errors occurred. (One or more errors occurred. (An error occurred trying to start process '/usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-arm64.Cross.ios-arm64/8.0.1/Sdk/../tools/mono-aot-cross' with working directory 'MySolutionDirectory'. No such file or directory))) (One or more errors occurred. (One or more errors occurred. (An error occurred trying to start process '/usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-arm64.Cross.ios-arm64/8.0.1/Sdk/../tools/mono-aot-cross' with working directory 'MySolutionDirectory'. No such file or directory))) (One or more errors occurred. (One or more errors occurred. (An error occurred trying to start process '/usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-arm64.Cross.ios-arm64/8.0.1/Sdk/../tools/mono-aot-cross' with working directory 'MySolutionDirectory'. No such file or directory))) (One or more errors occurred. (One or more errors occurred. (An error occurred trying to start process '/usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-arm64.Cross.ios-arm64/8.0.1/Sdk/../tools/mono-aot-cross' with working directory 'MySolutionDirectory'. No such file or directory))) (One or more errors occurred. (One or more errors occurred. (An error occurred trying to start process '/usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-arm64.Cross.ios-arm64/8.0.1/Sdk/../tools/mono-aot-cross' with working directory 'MySolutionDirectory'. No such file or directory))) (One or more errors occurred. (One or more errors occurred. (An error occurred trying to start process '/usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-arm64.Cross.ios-arm64/8.0.1/Sdk/../tools/mono-aot-cross' with working directory 'MySolutionDirectory'. No such file or directory))) (One or more errors occurred. (One or more errors occurred. (An error occurred trying to start process '/usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-arm64.Cross.ios-arm64/8.0.1/Sdk/../tools/mono-aot-cross' with working directory 'MySolutionDirectory'. No such file or directory))) (One or more errors occurred. (One or more errors occurred. (An error occurred trying to start process '/usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-arm64.Cross.ios-arm64/8.0.1/Sdk/../tools/mono-aot-cross' with working directory 'MySolutionDirectory'. No such file or directory))) (One or more errors occurred. (One or more errors occurred. (An error occurred trying to start process '/usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-arm64.Cross.ios-arm64/8.0.1/Sdk/../tools/mono-aot-cross' with working directory 'MySolutionDirectory'. No such file or directory))) (One or more errors occurred. (One or more errors occurred. (An error occurred trying to start process '/usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-arm64.Cross.ios-arm64/8.0.1/Sdk/../tools/mono-aot-cross' with working directory 'MySolutionDirectory'. No such file or directory))) [myproject.csproj::TargetFramework=net8.0-ios]
---> System.AggregateException: One or more errors occurred. (One or more errors occurred. (An error occurred trying to start process '/usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-arm64.Cross.ios-arm64/8.0.1/Sdk/../tools/mono-aot-cross' with working directory 'MySolutionDirectory'. No such file or directory)) [MyProject.csproj::TargetFramework=net8.0-ios]
---> System.AggregateException: One or more errors occurred. (An error occurred trying to start process '/usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-arm64.Cross.ios-arm64/8.0.1/Sdk/../tools/mono-aot-cross' with working directory 'MySolutionDirectory'. No such file or directory) [MyProject.csproj::TargetFramework=net8.0-ios]
---> System.ComponentModel.Win32Exception (2): An error occurred trying to start process '/usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-arm64.Cross.ios-arm64/8.0.1/Sdk/../tools/mono-aot-cross' with working directory 'MySolutionDirectory'. No such file or directory [MyProject.csproj::TargetFramework=net8.0-ios]
at System.Diagnostics.Process.ForkAndExecProcess(ProcessStartInfo startInfo, String resolvedFilename, String[] argv, String[] envp, String cwd, Boolean setCredentials, UInt32 userId, UInt32 groupId, UInt32[] groups, Int32& stdinFd, Int32& stdoutFd, Int32& stderrFd, Boolean usesTerminal, Boolean throwOnNoExec) [MyProject.csproj::TargetFramework=net8.0-ios]
at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo) [MyProject.csproj::TargetFramework=net8.0-ios]
at Xamarin.Utils.Execution.<>c__DisplayClass24_1.b__0() in /Users/builder/azdo/_work/1/s/xamarin-macios/tools/common/Execution.cs:line 103 [MyProject.csproj::TargetFramework=net8.0-ios]
--- End of stack trace from previous location`

@MitchBomcanhao
Copy link

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.

@rolfbjarne
Copy link
Member

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?

@MitchBomcanhao
Copy link

MitchBomcanhao commented Apr 8, 2024

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?

@dalexsoto
Copy link
Member Author

dalexsoto commented Apr 8, 2024

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.

@npostma
Copy link

npostma commented Apr 9, 2024

@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?

@mmiller-d8
Copy link

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

@npostma

@IainS1986
Copy link

IainS1986 commented Apr 16, 2024

@MitchBomcanhao

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)

@MitchBomcanhao
Copy link

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.

@MitchBomcanhao
Copy link

MitchBomcanhao commented Apr 22, 2024

15.4 is already in beta stage, and there's still no light at the end of the tunnel for 15.3.

@stemig
Copy link

stemig commented Apr 27, 2024

Unacceptable response times...

@Valronicon
Copy link

Can't publish MAUI as well.
Downgrading xcode to 15.2 didn't help.

C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8022\targets\Xamarin.Shared.Sdk.targets(1559,3): error : clang++ wurde mit dem Code 1 beendet: [C:\Repos\MauiApp.csproj::TargetFramework=net8.0-ios] C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8022\targets\Xamarin.Shared.Sdk.targets(1559,3): error : Undefined symbols for architecture arm64: [C:\Repos\MauiApp.csproj::TargetFramework=net8.0-ios] C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8022\targets\Xamarin.Shared.Sdk.targets(1559,3): error : "_SSLCopyALPNProtocols", referenced from: [C:\Repos\MauiApp.csproj::TargetFramework=net8.0-ios] C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8022\targets\Xamarin.Shared.Sdk.targets(1559,3): error : _AppleCryptoNative_SslGetAlpnSelected in libSystem.Security.Cryptography.Native.Apple.a(pal_ssl.c.o) [C:\Repos\MauiApp.csproj::TargetFramework=net8.0-ios] C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8022\targets\Xamarin.Shared.Sdk.targets(1559,3): error : "_SSLCopyDistinguishedNames", referenced from: [C:\Repos\MauiApp.csproj::TargetFramework=net8.0-ios] C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8022\targets\Xamarin.Shared.Sdk.targets(1559,3): error : _AppleCryptoNative_SslCopyCADistinguishedNames in libSystem.Security.Cryptography.Native.Apple.a(pal_ssl.c.o) [C:\Repos\MauiApp.csproj::TargetFramework=net8.0-ios] C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8022\targets\Xamarin.Shared.Sdk.targets(1559,3): error : "_SSLCopyPeerTrust", referenced from: [C:\Repos\MauiApp.csproj::TargetFramework=net8.0-ios] C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8022\targets\Xamarin.Shared.Sdk.targets(1559,3): error : _AppleCryptoNative_SslCopyCertChain in libSystem.Security.Cryptography.Native.Apple.a(pal_ssl.c.o) [C:\Repos\MauiApp.csproj::TargetFramework=net8.0-ios] C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8022\targets\Xamarin.Shared.Sdk.targets(1559,3): error : _AppleCryptoNative_SslIsHostnameMatch in libSystem.Security.Cryptography.Native.Apple.a(pal_ssl.c.o) [C:\Repos\MauiApp.csproj::TargetFramework=net8.0-ios] C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8022\targets\Xamarin.Shared.Sdk.targets(1559,3): error : "_SSLCreateContext", referenced from: [C:\Repos\MauiApp.csproj::TargetFramework=net8.0-ios] C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8022\targets\Xamarin.Shared.Sdk.targets(1559,3): error : _AppleCryptoNative_SslCreateContext in libSystem.Security.Cryptography.Native.Apple.a(pal_ssl.c.o) [C:\Repos\MauiApp.csproj::TargetFramework=net8.0-ios] C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8022\targets\Xamarin.Shared.Sdk.targets(1559,3): error : "_SSLGetNegotiatedCipher", referenced from: [C:\Repos\MauiApp.csproj::TargetFramework=net8.0-ios] C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8022\targets\Xamarin.Shared.Sdk.targets(1559,3): error : _AppleCryptoNative_SslGetCipherSuite in libSystem.Security.Cryptography.Native.Apple.a(pal_ssl.c.o) [C:\Repos\MauiApp.csproj::TargetFramework=net8.0-ios] C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8022\targets\Xamarin.Shared.Sdk.targets(1559,3): error : "_SSLGetNegotiatedProtocolVersion", referenced from: [C:\Repos\MauiApp.csproj::TargetFramework=net8.0-ios] C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8022\targets\Xamarin.Shared.Sdk.targets(1559,3): error : _AppleCryptoNative_SslGetProtocolVersion in libSystem.Se [C:\Repos\MauiApp.csproj::TargetFramework=net8.0-ios]

@rolfbjarne
Copy link
Member

Can't publish MAUI as well. Downgrading xcode to 15.2 didn't help.

C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8022\targets\Xamarin.Shared.Sdk.targets(1559,3): error : clang++ wurde mit dem Code 1 beendet: [C:\Repos\MauiApp.csproj::TargetFramework=net8.0-ios] C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8022\targets\Xamarin.Shared.Sdk.targets(1559,3): error : Undefined symbols for architecture arm64: [C:\Repos\MauiApp.csproj::TargetFramework=net8.0-ios] C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8022\targets\Xamarin.Shared.Sdk.targets(1559,3): error : "_SSLCopyALPNProtocols", referenced from: [C:\Repos\MauiApp.csproj::TargetFramework=net8.0-ios] C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8022\targets\Xamarin.Shared.Sdk.targets(1559,3): error : _AppleCryptoNative_SslGetAlpnSelected in libSystem.Security.Cryptography.Native.Apple.a(pal_ssl.c.o) [C:\Repos\MauiApp.csproj::TargetFramework=net8.0-ios] C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8022\targets\Xamarin.Shared.Sdk.targets(1559,3): error : "_SSLCopyDistinguishedNames", referenced from: [C:\Repos\MauiApp.csproj::TargetFramework=net8.0-ios] C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8022\targets\Xamarin.Shared.Sdk.targets(1559,3): error : _AppleCryptoNative_SslCopyCADistinguishedNames in libSystem.Security.Cryptography.Native.Apple.a(pal_ssl.c.o) [C:\Repos\MauiApp.csproj::TargetFramework=net8.0-ios] C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8022\targets\Xamarin.Shared.Sdk.targets(1559,3): error : "_SSLCopyPeerTrust", referenced from: [C:\Repos\MauiApp.csproj::TargetFramework=net8.0-ios] C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8022\targets\Xamarin.Shared.Sdk.targets(1559,3): error : _AppleCryptoNative_SslCopyCertChain in libSystem.Security.Cryptography.Native.Apple.a(pal_ssl.c.o) [C:\Repos\MauiApp.csproj::TargetFramework=net8.0-ios] C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8022\targets\Xamarin.Shared.Sdk.targets(1559,3): error : _AppleCryptoNative_SslIsHostnameMatch in libSystem.Security.Cryptography.Native.Apple.a(pal_ssl.c.o) [C:\Repos\MauiApp.csproj::TargetFramework=net8.0-ios] C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8022\targets\Xamarin.Shared.Sdk.targets(1559,3): error : "_SSLCreateContext", referenced from: [C:\Repos\MauiApp.csproj::TargetFramework=net8.0-ios] C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8022\targets\Xamarin.Shared.Sdk.targets(1559,3): error : _AppleCryptoNative_SslCreateContext in libSystem.Security.Cryptography.Native.Apple.a(pal_ssl.c.o) [C:\Repos\MauiApp.csproj::TargetFramework=net8.0-ios] C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8022\targets\Xamarin.Shared.Sdk.targets(1559,3): error : "_SSLGetNegotiatedCipher", referenced from: [C:\Repos\MauiApp.csproj::TargetFramework=net8.0-ios] C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8022\targets\Xamarin.Shared.Sdk.targets(1559,3): error : _AppleCryptoNative_SslGetCipherSuite in libSystem.Security.Cryptography.Native.Apple.a(pal_ssl.c.o) [C:\Repos\MauiApp.csproj::TargetFramework=net8.0-ios] C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8022\targets\Xamarin.Shared.Sdk.targets(1559,3): error : "_SSLGetNegotiatedProtocolVersion", referenced from: [C:\Repos\MauiApp.csproj::TargetFramework=net8.0-ios] C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\17.2.8022\targets\Xamarin.Shared.Sdk.targets(1559,3): error : _AppleCryptoNative_SslGetProtocolVersion in libSystem.Se [C:\Repos\MauiApp.csproj::TargetFramework=net8.0-ios]

Try this: #20406 (comment)

@MitchBomcanhao
Copy link

xcode 15.4 already in release candidate mode. any light at the end of this tunnel?

@nbevans
Copy link

nbevans commented May 14, 2024

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 dalexsoto changed the title [META] Xcode 15.3 Support for .NET 8 and MAUI [META] Xcode 15.3/4 Support for .NET 8 and MAUI May 14, 2024
@Axemasta
Copy link

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:

  • Updating xcode to 15.4
  • Installing .NET 8.0.6 (SDK 8.0.301)
  • Installing maui workloads again (sudo dotnet workload install maui --source "https://api.nuget.org/v3/index.json")
  • Building and running very happily :)

Thanks for providing this thread and keeping us updated 😊

@jacobc94
Copy link

@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??

@Axemasta
Copy link

Axemasta commented Jun 12, 2024

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 dotnet --version i see 8.0.301

@matteomonizza
Copy link

I'm running XCode 15.4, Rider 2024.1.3, .NET 8.0.302, all workloads updated (ios, android, maui). All works fine

@tpitman
Copy link

tpitman commented Jun 13, 2024

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.

@rolfbjarne
Copy link
Member

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.

Please file a new issue, since it might very well be something unrelated.

@tpitman
Copy link

tpitman commented Jun 17, 2024

Done: #20734

@primozcerar
Copy link

primozcerar commented Jun 19, 2024

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
a fatal error in the mono runtime or one of the native libraries
used by your application.

=================================================================

=================================================================

Native stacktrace:

=================================================================

Call Stack
0x103130414 - /Users/vasco/Library/Developer/CoreSimulator/Devices/A87FFE72-81B1-480F-9E73-58B54CC6DB14/data/Containers/Bundle/Application/161EEBD5-9132-4816-BE1C-AEC55684BBA0/DXChartConstantLineBug.app/libmonosgen-2.0.dylib : mono_dump_native_crash_info
0x1030e0600 - /Users/vasco/Library/Developer/CoreSimulator/Devices/A87FFE72-81B1-480F-9E73-58B54CC6DB14/data/Containers/Bundle/Application/161EEBD5-9132-4816-BE1C-AEC55684BBA0/DXChartConstantLineBug.app/libmonosgen-2.0.dylib : mono_handle_native_crash
0x103047b0c - /Users/vasco/Library/Developer/CoreSimulator/Devices/A87FFE72-81B1-480F-9E73-58B54CC6DB14/data/Containers/Bundle/Application/161EEBD5-9132-4816-BE1C-AEC55684BBA0/DXChartConstantLineBug.app/libmonosgen-2.0.dylib : mono_sigsegv_signal_handler_debug
0x11a5fbc60 - /usr/lib/system/libsystem_platform.dylib : _sigtramp
0x120431ff8 - /Library/Developer/CoreSimulator/Volumes/iOS_21E213/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 17.4.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/OpenGLES.framework/libCoreVMClient.dylib : cvmsServerElementBuild
0x12042de34 - /Library/Developer/CoreSimulator/Volumes/iOS_21E213/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 17.4.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/OpenGLES.framework/libCoreVMClient.dylib : cvms_element_build_from_source
0x11e07a854 - /Library/Developer/CoreSimulator/Volumes/iOS_21E213/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 17.4.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/OpenGLES.framework/libCVMSPluginSupport.dylib : _Z26cvm_deferred_build_modularPv
0x118f67978 - /Library/Developer/CoreSimulator/Volumes/iOS_21E213/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 17.4.simruntime/Contents/Resources/RuntimeRoot/usr/lib/system/libdispatch.dylib : _dispatch_client_callout
0x118f6fb10 - /Library/Developer/CoreSimulator/Volumes/iOS_21E213/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 17.4.simruntime/Contents/Resources/RuntimeRoot/usr/lib/system/libdispatch.dylib : _dispatch_lane_serial_drain
0x118f70688 - /Library/Developer/CoreSimulator/Volumes/iOS_21E213/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 17.4.simruntime/Contents/Resources/RuntimeRoot/usr/lib/system/libdispatch.dylib : _dispatch_lane_invoke
0x118f7ba84 - /Library/Developer/CoreSimulator/Volumes/iOS_21E213/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 17.4.simruntime/Contents/Resources/RuntimeRoot/usr/lib/system/libdispatch.dylib : _dispatch_root_queue_drain_deferred_wlh
0x118f7b0d0 - /Library/Developer/CoreSimulator/Volumes/iOS_21E213/Library/Developer/CoreSimulato
r/Profiles/Runtimes/iOS 17.4.simruntime/Contents/Resources/RuntimeRoot/usr/lib/system/libdispatch.dylib : _dispatch_workloop_worker_thread
0x11a61b924 - /usr/lib/system/libsystem_pthread.dylib : _pthread_wqthread
0x11a61a6e4 - /usr/lib/system/libsystem_pthread.dylib : start_wqthread

=================================================================

Basic Fault Address Reporting

=================================================================

Call Stack
Memory around native instruction pointer (0x11a5fb8a0):0x11a5fb890 28 24 40 a8 2a 2c 41 a8 21 80 00 91 42 00 05 cb ($@.*,A.!...B...
0x11a5fb8a0 0c 34 00 a9 0e 3c 01 a9 42 00 01 f1 29 01 00 54 .4...<..B...)..T
0x11a5fb8b0 68 24 00 a9 6a 2c 01 a9 63 80 00 91 28 24 40 a8 h$..j,..c...($@.
0x11a5fb8c0 2a 2c 41 a8 21 80 00 91 42 80 00 f1 28 ff ff 54 *,A.!...B...(..T

All components updated to latest which should not have anymore simulator issues according to Microsoft MAUI team.

.net SDK 8.0.302
VS 17.10.2
MAUI 8.0.60
Simulator iPhone 15 iOS 17.4 or 17.5
XCode 15.4

All workloads updated on Win and Mac

Installed Workload Id Manifest Version Installation Source
android 34.0.113/8.0.100 SDK 8.0.300, VS 17.10.35004.147
aspire 8.0.1/8.0.100 SDK 8.0.300, VS 17.10.35004.147
ios 17.2.8053/8.0.100 SDK 8.0.300, VS 17.10.35004.147
maccatalyst 17.2.8053/8.0.100 SDK 8.0.300, VS 17.10.35004.147
maui 8.0.40/8.0.100 SDK 8.0.300
maui-windows 8.0.40/8.0.100 SDK 8.0.300, VS 17.10.35004.147
wasi-experimental 8.0.6/8.0.100 SDK 8.0.300

@zippo227
Copy link
Contributor

zippo227 commented Jul 9, 2024

According to the releases page, this issue can be marked as closed. https://github.com/dotnet/maui/wiki/Release-Versions

@rolfbjarne
Copy link
Member

According to the releases page, this issue can be marked as closed. Wiki: Release Versions (dotnet/maui)

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.

@ggbtvs
Copy link

ggbtvs commented Jul 17, 2024

@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.

@rfsouto
Copy link

rfsouto commented Jul 17, 2024

@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.

@zippo227
Copy link
Contributor

zippo227 commented Jul 22, 2024

According to the releases page, this issue can be marked as closed. Wiki: Release Versions (dotnet/maui)

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.

Could you please provide an estimated month for the 15.3 and 15.4 bindings releases? @rolfbjarne

@matteomonizza
Copy link

matteomonizza commented Jul 23, 2024

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

@dalexsoto
Copy link
Member Author

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.

@ggbtvs
Copy link

ggbtvs commented Aug 1, 2024

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?

@rolfbjarne
Copy link
Member

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

@rolfbjarne
Copy link
Member

Will this make it into a final release of VS for Mac?

No more updates are planned for VS for Mac.

@dalexsoto
Copy link
Member Author

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 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

@phillippschmedt
Copy link

phillippschmedt commented Aug 6, 2024

Can someone explain to me why I suddenly get this warning?
ILLINK : warning MT0079: The recommended Xcode version for Microsoft.iOS 17.5.8018 is Xcode 15.4 or later. The current Xcode version (found in /Applications/Xcode-15.2.0.app/Contents/Developer) is 15.2.

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?

@matteomonizza
Copy link

I use XCode 15.4 with no problem

@phillippschmedt
Copy link

Thank you. I also updated to Xcode 15.4 and it work's fine.

@Domik234
Copy link

Domik234 commented Aug 7, 2024

In case of need you should be able to download Xcode's specific version, rename it (like on picture - suffix with version), copy it to Applications on Mac and then switch between default and "custom downloaded" by changing the Xcode path in VS settings because they can co-exists next to themself.
image

Note: Remote Simulator on changed Xcode path does not work so you have to use VNC or directly Mac to access the simulator.

@IainS1986
Copy link

Or, use XCodes 👍
https://www.xcodes.app/

@rolfbjarne
Copy link
Member

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?

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.

@rolfbjarne rolfbjarne unpinned this issue Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
iOS Issues affecting iOS macOS Issues affecting macOS
Projects
None yet
Development

No branches or pull requests