Device build fails with Error NETSDK1047

[marcoburato-ecutek]

Apple platform

iOS

Framework version

net10.0-*

Affected platform version

.NET iOS 26.2.10191/10.0.100

Description

I'm upgrading our app from .NET 9 to .NET 10. I had it building for both the Simulator and my device, but at some point it started failing with this error:

0>Microsoft.PackageDependencyResolution.targets(266,5): Error NETSDK1047 : Assets file '/Users/marco/Desktop/App/EviApp/EviApp.iOS/obj/project.assets.json' doesn't have a target for 'net10.0-ios26.2/ios-arm64'. Ensure that restore has run and that you have included 'net10.0-ios26.2' in the TargetFrameworks for your project. You may also need to include 'ios-arm64' in your project's RuntimeIdentifiers.

I tried to delete the bin, obj folders and the NuGet packages folder to start from a clean state, but I keep getting the same error.

It seems like it's trying to do a simulator build even when it should do a device build. This happens in both Debug and Release configuration.

I'm using JetBrains Rider 2025.3.1 as the IDE.

This should be the relevant part of the project file:

<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
    <TargetFramework>net10.0-ios26.2</TargetFramework>
    <OutputType>Exe</OutputType>
    <SupportedOSPlatformVersion>15.0</SupportedOSPlatformVersion>
    <Configurations>Debug;Release</Configurations>
    <RootNamespace>EviApp</RootNamespace>
    <EnableDefaultNoneItems>false</EnableDefaultNoneItems>
    <TrimmerSingleWarn>false</TrimmerSingleWarn>
</PropertyGroup>
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' ">
    <AllowUnsafeBlocks>true</AllowUnsafeBlocks>
    <DefineConstants>TRACE</DefineConstants>
    <WarningLevel>4</WarningLevel>
    <NoWarn>1701;1702;IL2026;IL2035;IL2036;IL2057;IL2062;IL2065;IL2067;IL2072;IL2080</NoWarn>
</PropertyGroup>
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' ">
    <AllowUnsafeBlocks>true</AllowUnsafeBlocks>
    <DefineConstants>TRACE</DefineConstants>
    <WarningLevel>4</WarningLevel>
    <NoWarn>1701;1702;IL2026;IL2035;IL2036;IL2057;IL2062;IL2065;IL2067;IL2072;IL2080</NoWarn>
</PropertyGroup>

If I add

<RuntimeIdentifiers>ios-arm64;iossimulator-x64</RuntimeIdentifiers>

then the build produces this warning:

0>Xamarin.Shared.Sdk.targets(309,3): Warning  : RuntimeIdentifier was set on the command line, and will override the value for RuntimeIdentifiers set in the project file.

...however, it will build successfully.

I don't think that's the right solution, though. Always building both RIDs would be a waste of time and I would not want to include x64 binaries when building the app bundle for release.

Steps to Reproduce

1. Select a real device in the IDE as the run target
2. Build the project (either Debug or Release)

Did you find any workaround?

No

Build logs

I can't provide build logs publicly, but I can send them privately if there's a way.

[rolfbjarne]

I had it building for both the Simulator and my device, but at some point it started failing with this error:

Do you get the same error when building for both simulator and device now?

Also: does it work if you build from the command line?

<RuntimeIdentifiers>ios-arm64;iossimulator-x64</RuntimeIdentifiers>

Don't do this, it won't work as expected, because it's not possible to create a single app that installs and runs on both simulator and device.

I'm using JetBrains Rider 2025.3.1 as the IDE.

My guess is that it's Rider getting confused somehow.

It would be interesting to see exactly the build command Rider executes (try initiating a build, and then run ps aux | grep dotnet.*build in a terminal and see if you can catch the actual command in the process list).

[marcoburato-ecutek]

Do you get the same error when building for both simulator and device now?

No, only when building for the device. Simulator build works fine.

It would be interesting to see exactly the build command Rider executes

I wasn't seeing the process with ps aux | grep dotnet.*build. I had to switch off the "Use ReSharper Build" option. Now it uses the dotnet program to build (it fails with the same error).

This is the command line when I try a device build:

/usr/local/share/dotnet/dotnet /usr/local/share/dotnet/sdk/10.0.101/MSBuild.dll /noconsolelogger /property:Configuration=Debug /property:Platform=Any CPU /property:EnableCodeSigning=False /property:TargetFramework=net10.0-ios26.2 /property:RuntimeIdentifier=ios-arm64 /t:EviApp_iOS:Rebuild /logger:/Applications/Rider.app/Contents/lib/ReSharperHost/JetBrains.Platform.MsBuildEventLogger.dll;54481 /m:14 /fileLogger1 /fileloggerparameters1:LogFile=/Users/marco/Library/Logs/JetBrains/Rider2025.3/SolutionBuilder/JetBrainsLog.ReSharperBuild_2026_01_08_12_55_45_9339.log; /fileLoggerParameters1:Verbosity=Diagnostic /Users/marco/Desktop/App/EviApp/EviApp.sln

Also: does it work if you build from the command line?

I tried to replicate the build with dotnet build. I don't know how to specify the target, though.
This works:

 dotnet build -p:TargetFramework=net10.0-ios26.2 -p:RuntimeIdentifier=ios-arm64 -p:Configuration=Debug

And oddly, this works too, which should be the same thing Rider does:

/usr/local/share/dotnet/dotnet /usr/local/share/dotnet/sdk/10.0.101/MSBuild.dll /property:Configuration=Debug /property:Platform="Any CPU" /property:EnableCodeSigning=False /property:TargetFramework=net10.0-ios26.2 /property:RuntimeIdentifier=ios-arm64 /t:EviApp_iOS:Rebuild /m:14 /Users/marco/Desktop/App/EviApp/EviApp.sln

The only iffy thing I noticed is how "Any CPU" is passed on the command line. It appears to be unquoted when Rider does it. But, if I do it in terminal, that causes MSBuild to error immediately. So, not sure if it's just being reported incorrectly by ps (though, in the MSBuild log saved to file, it's also unquoted).

Other than that, I don't know what to think. Could it be a race condition?

[marcoburato-ecutek]

I've managed to reproduce the issue on the command line. Not sure what triggered it, but it seems to be caused by a stale project.assets.json file:

% /usr/local/share/dotnet/dotnet /usr/local/share/dotnet/sdk/10.0.101/MSBuild.dll /verbosity:minimal /property:Configuration=Debug /property:Platform="Any CPU" /property:EnableCodeSigning=False /property:TargetFramework=net10.0-ios26.2 /property:RuntimeIdentifier=ios-arm64 /t:EviApp_iOS:Rebuild /m:14 /fileLogger1 /fileloggerparameters1:LogFile=/Users/marco/Desktop/msbuild.log /fileLoggerParameters1:Verbosity=Diagnostic /Users/marco/Desktop/App/EviApp/EviApp.sln
MSBuild version 18.0.6+fad253f51 for .NET
/usr/local/share/dotnet/sdk/10.0.101/Sdks/Microsoft.NET.Sdk/targets/Microsoft.PackageDependencyResolution.targets(266,5): error NETSDK1047: Assets file '/Users/marco/Desktop/App/EviApp/EviApp.iOS/obj/project.assets.json' doesn't have a target for 'net10.0-ios26.2/ios-arm64'. Ensure that restore has run and that you have included 'net10.0-ios26.2' in the TargetFrameworks for your project. You may also need to include 'ios-arm64' in your project's RuntimeIdentifiers. [/Users/marco/Desktop/App/EviApp/EviApp.iOS/EviApp.iOS.csproj]
% date
Fri  9 Jan 2026 10:48:31 CET
% ls -l ~/Desktop/App/EviApp/EviApp.iOS/obj/project.assets.json
-rw-r--r--@ 1 marco  staff  60830  9 Jan 10:32 /Users/marco/Desktop/App/EviApp/EviApp.iOS/obj/project.assets.json
% grep ios-arm64 ~/Desktop/App/EviApp/EviApp.iOS/obj/project.assets.json
% grep iossimulator-x64 ~/Desktop/App/EviApp/EviApp.iOS/obj/project.assets.json
    "net10.0-ios26.2/iossimulator-x64": {
    "iossimulator-x64": {
% 

After deleting the file, the build failed due to file not found, suggesting NuGet restore needs to be run to generate it:

% /usr/local/share/dotnet/dotnet /usr/local/share/dotnet/sdk/10.0.101/MSBuild.dll /verbosity:minimal /property:Configuration=Debug /property:Platform="Any CPU" /property:EnableCodeSigning=False /property:TargetFramework=net10.0-ios26.2 /property:RuntimeIdentifier=ios-arm64 /t:EviApp_iOS:Rebuild /m:14 /fileLogger1 /fileloggerparameters1:LogFile=/Users/marco/Desktop/msbuild.log /fileLoggerParameters1:Verbosity=Diagnostic /Users/marco/Desktop/App/EviApp/EviApp.sln
MSBuild version 18.0.6+fad253f51 for .NET
/usr/local/share/dotnet/sdk/10.0.101/Sdks/Microsoft.NET.Sdk/targets/Microsoft.PackageDependencyResolution.targets(266,5): error NETSDK1004: Assets file '/Users/marco/Desktop/App/EviApp/EviApp.iOS/obj/project.assets.json' not found. Run a NuGet package restore to generate this file. [/Users/marco/Desktop/App/EviApp/EviApp.iOS/EviApp.iOS.csproj]

However, after restoring the packages, we circle back to the original issue:

% dotnet restore
Restore complete (2.1s)

Build succeeded in 2.2s
% /usr/local/share/dotnet/dotnet /usr/local/share/dotnet/sdk/10.0.101/MSBuild.dll /verbosity:minimal /property:Configuration=Debug /property:Platform="Any CPU" /property:EnableCodeSigning=False /property:TargetFramework=net10.0-ios26.2 /property:RuntimeIdentifier=ios-arm64 /t:EviApp_iOS:Rebuild /m:14 /fileLogger1 /fileloggerparameters1:LogFile=/Users/marco/Desktop/msbuild.log /fileLoggerParameters1:Verbosity=Diagnostic /Users/marco/Desktop/App/EviApp/EviApp.sln
MSBuild version 18.0.6+fad253f51 for .NET
/usr/local/share/dotnet/sdk/10.0.101/Sdks/Microsoft.NET.Sdk/targets/Microsoft.PackageDependencyResolution.targets(266,5): error NETSDK1047: Assets file '/Users/marco/Desktop/App/EviApp/EviApp.iOS/obj/project.assets.json' doesn't have a target for 'net10.0-ios26.2/ios-arm64'. Ensure that restore has run and that you have included 'net10.0-ios26.2' in the TargetFrameworks for your project. You may also need to include 'ios-arm64' in your project's RuntimeIdentifiers. [/Users/marco/Desktop/App/EviApp/EviApp.iOS/EviApp.iOS.csproj]
% grep ios-arm64 ~/Desktop/App/EviApp/EviApp.iOS/obj/project.assets.json
% 

I would expect NuGet packages to contain data for all the RIDs and simply be downloaded on a nuget restore. It seems wrong for project.assets.json to be generated on a nuget restore but target a specific RID. Am I missing something?

[rolfbjarne]

So this is a quirk with some our mobile platforms:

• RuntimeIdentifier (singular): means produce an app bundle for the specified runtime identifier.
• RuntimeIdentifiers (plural): means produce a single ("universal" is Apple's terminology) app bundle for all the listed runtime identifiers.

This is a deviation from normal .NET projects, where the plural version means "restore the project for all the listed runtime identifiers", typically used to restore all possible runtime identifiers for a given project.

Another piece of the puzzle is also required: if no RuntimeIdentifier is specified, we'll choose a default one (typically iossimulator-arm64 for iOS).

So what happens is this:

1. dotnet restore will restore RuntimeIdentifier=iossimulator-arm64 (because that's the default RuntimeIdentifier).
2. dotnet build -t:Rebuild -p:RuntimeIdentifier=ios-arm64 will not work, because it's building for ios-arm64, which hasn't been restored.

There are a couple of solutions:

• Run dotnet restore -p:RuntimeIdentifier=ios-arm64: this will restore the RuntimeIdentifier that will later get built.
• Run dotnet build (and not pass -t:Rebuild, nor --no-restore): this works because dotnet build will restore by default.

So this seems like it's a bug with Rider, if they depend on a dotnet restore command before building, they must also specify the RuntimeIdentifier that will later be built.

[rolfbjarne]

That said, we might implement a solution to forcefully restore all possible runtime identifiers, although I don't know when that might be done.

[marcoburato-ecutek]

Is this a breaking change in .NET 10? Because I was not experiencing this issue on .NET 9.

[rolfbjarne]

Is this a breaking change in .NET 10? Because I was not experiencing this issue on .NET 9.

It's not something we did on purpose at least, but I'll look into it and see if we changed behavior somewhere unintentionally.

[rolfbjarne]

I tried this with Rider, and I can reproduce the problem.

However, I can also reproduce the problem with a .NET 9 project.

Can you try a .NET 9 project again, and if that works, attach the output of dotnet --info when executed from the command line in that project's directory?