Known issues in .NET

.NET 8 Preview 1 does not yet support win-arm64

Some of the changes that enable win-arm64 are in .NET 7, but did not make it appropriately to .NET 8 Preview 1. This should be addressed in a future preview.

.NET 8 Preview 1: mono-aot-cross is not executable

On macOS, if you encounter a build error related to mono-aot-cross:

An error occurred trying to start process '/usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-x64.Cross.android-arm/8.0.0-preview.1.23110.8/Sdk/../tools/mono-aot-cross'. Permission denied

You can workaround the issue, by making the file executable:

sudo chmod +x /usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.*/8.0.0-preview.1.*/tools/mono-aot-cross

This is tracked in dotnet/runtime#82201.

.NET 8 Preview 1: dotnet new maui apps crash in Release mode

Some apps crash with:

02-21 17:03:17.515  9548  9548 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x000000000000001c
02-21 17:03:17.515  9548  9548 F DEBUG   : Cause: null pointer dereference

You can workaround by passing -p:AndroidEnableMarshalMethods=false, or in your .csproj file via:

<AndroidEnableMarshalMethods>false</AndroidEnableMarshalMethods>

This is tracked in #7819

Specifying both -f and -r to dotnet build fails to restore for multi-targeted projects

This will manifest as a build error like this:

error : The RuntimeIdentifier 'android-arm64' is invalid.

The cause is that by passing -r <runtime identifier> to 'dotnet build' that runtime identifier is used for all target frameworks in the project file when the project is restored, while it's only a valid runtime identifier for one of the target frameworks.

Potential workaround is to restore manually, and build without restoring:

$ dotnet restore
$ dotnet build --no-restore -f net6.0-android -r android-arm64

This happens with dotnet publish as well.

This will be fixed in a future version of NuGet.

Ref: https://github.com/dotnet/sdk/issues/21877.
Ref: https://github.com/NuGet/Home/issues/11653.