Known issues in .NET8

This document lists known issues in the SDKs.

Launching from the command line is awkward

Launching an app in the simulator (iOS, tvOS)

1. Use the following command to get a list of all the simulators:

$ /Applications/Xcode.app/Contents/Developer/usr/bin/simctl list

2. Choose one, and copy the corresponding UDID.

3. Set the _DeviceName property like this to select the simulator:

dotnet build -t:Run -p:_DeviceName=:v2:udid=<UDID>

Note that a simulator runtime identifier must be used (either set in the project file, or passed to the command above like this: /p:RuntimeIdentifier=iossimulator-x64).

Launching an app on device (iOS, tvOS)

1. Open Xcode, then the menu Window -> Devices and Simulators.

2. Choose a device on the left, and copy the Identifier from the device info section.

3. Set the _DeviceName property like this to select the device:

dotnet build -t:Run -p:_DeviceName=<IDENTIFIER>

Note that a device runtime identifier must be used (either set in the project file, or passed to the command above like this: /p:RuntimeIdentifier=ios-arm64).

Launching an app on desktop (macOS, Mac Catalyst)

Just dotnet run should work just fine.

If something goes wrong (the app crashes, etc.), it's often useful to see stdout and stderr (Console.Out / Console.Error) from the app (this can even be useful as a debugging mechanism in certain cases). In order to see this output, it's necessary to execute the actual macOS executable directly from the terminal. The executable can be found inside the Contents/MacOS directory of the app, which can be found in the output directory.

An example path for a Mac Catalyst app built for x86_64 (relative to the project directory):

$ ./bin/Debug/net6.0-maccatalyst/maccatalyst-x64/MySimpleApp.app/Contents/MacOS/MySimpleApp
[output]

If the app is a universal app (built for both x64 and arm64), the path to the app won't contain the runtime identifier:

$ ./bin/Debug/net6.0-maccatalyst/MySimpleApp.app/Contents/MacOS/MySimpleApp
[output]

Ref: https://github.com/dotnet/xamarin/issues/26.

Mac Catalyst app signed with a provisioning profile with configuration "Mac Catalyst" crashes at launch.

A Mac Catalyst app with entitlements and signed with a macOS provisioning profile with configuration "Mac Catalyst" crashes at launch with "Security policy does not allow @ path expansion".

There are two known workarounds:

1. Add the following to the project file:

   <PropertyGroup>
     <_LibMonoLinkMode>Static</_LibMonoLinkMode>
     <_LibXamarinLinkMode>Static</_LibXamarinLinkMode>
   </PropertyGroup>

   Ref: https://github.com/xamarin/xamarin-macios/issues/14686#issuecomment-1106418177

2. Use a provisioning profile with configuration "Mac" instead of "Mac Catalyst"

   See: https://github.com/xamarin/xamarin-macios/issues/14686#issuecomment-1109808007

Ref: https://github.com/xamarin/xamarin-macios/issues/14686

Selecting the simulator architecture remotely from Windows

When:

• Building remotely from Visual Studio (on Windows).
• Building for the simulator.
• The remote mac is an ARM64 machine.

Visual Studio will build using the iossimulator-arm64 RuntimeIdentifier.

For some projects this may not work correctly (in particular projects that depend on third-party native libraries that don't provide an iossimulator-arm64 version of their library), and for those cases it's possible to make Visual Studio build using iossimulator-x64 instead, by setting the following property in the project file:

<PropertyGroup>
  <ForceSimulatorX64ArchitectureInIDE>true</ForceSimulatorX64ArchitectureInIDE>
</PropertyGroup>

This is supported starting in Visual Studio 17.7 preview 3.