iOS Native Interop doesn't work with .NET 10.

[bwinklesky]

Description

When building with .NET 10 the .resources folder doesn't get generated. It appears the library is not compatible with the latest version of .net.

Steps to Reproduce

1. open template.
2. change to .NET 10
3. run dotnet build (or follow the instructions)

Link to public reproduction project repository

No response

Environment

• OS: Mac
• .NET MAUI: 10
• Target platforms: iOS

[HelloooJoe]

I can confirm this does work with .NET 10. I currently have a production app deployed to both the App Store and Google Play that relies on native interop and bindings.

The app uses Swift and Kotlin bindings for Stripe and Square SDKs to support in-person payments and also includes custom native bindings for Bluetooth printing to Epson and Star Micronics thermal printers.

All of this is built and running successfully on .NET 10 / .NET MAUI, including iOS targets.

[bwinklesky]

@HelloooJoe Can you share how you got it to work? I just tried building the Google Cast sample and the .resources folder doesn't get created. There is a "resources.stamp", but that it.

[bwinklesky]

I just tried a different Mac and the same result.

[Hamdev-Algo]

Well, i just tested the MauiSample project using this workload (both pc and mac with xcode 26.2) :

Workload version: 10.0.101.1

Installed Workload Id      Manifest Version         Installation Source
------------------------------------------------------------------------------------------------------
android                    36.1.2/10.0.100          SDK 10.0.100, VS 18.2.11415.280, VS 17.14.36414.22
ios                        26.2.10191/10.0.100      SDK 10.0.100, VS 18.2.11415.280, VS 17.14.36414.22
maccatalyst                26.2.10191/10.0.100      SDK 10.0.100, VS 18.2.11415.280, VS 17.14.36414.22
macos                      26.2.10191/10.0.100      SDK 10.0.100, VS 17.14.36414.22
maui                       10.0.1/10.0.100          SDK 10.0.100
maui-windows               10.0.1/10.0.100          SDK 10.0.100, VS 18.2.11415.280, VS 17.14.36414.22
tvos                       26.2.10191/10.0.100      SDK 10.0.100
wasm-tools-net6            10.0.101/10.0.100        SDK 10.0.100, VS 17.14.36414.22
wasm-tools-net7            10.0.101/10.0.100        SDK 10.0.100, VS 17.14.36414.22

The only modification I made was to change the TargetFrameworks property to net10.0-ios in both MauiSample.csproj and NewBinding.MaciOS.Binding.csproj.

And during compilation, I got the following error :

clang++ exited with code 1:
Undefined symbols for architecture arm64:
  "_OBJC_CLASS_$_DotnetNewBinding", referenced from:
       in registrar.o
ld: symbol(s) not found for architecture arm64
clang++: error: linker command failed with exit code 1 (use -v to see invocation)

Could you try running MauiSample with both .net 10 and xcode 26.2 and provide an explanation of the error encountered?

[bwinklesky]

Well, i just tested the MauiSample project using this workload (both pc and mac with xcode 26.2) :

Workload version: 10.0.101.1

Installed Workload Id      Manifest Version         Installation Source
------------------------------------------------------------------------------------------------------
android                    36.1.2/10.0.100          SDK 10.0.100, VS 18.2.11415.280, VS 17.14.36414.22
ios                        26.2.10191/10.0.100      SDK 10.0.100, VS 18.2.11415.280, VS 17.14.36414.22
maccatalyst                26.2.10191/10.0.100      SDK 10.0.100, VS 18.2.11415.280, VS 17.14.36414.22
macos                      26.2.10191/10.0.100      SDK 10.0.100, VS 17.14.36414.22
maui                       10.0.1/10.0.100          SDK 10.0.100
maui-windows               10.0.1/10.0.100          SDK 10.0.100, VS 18.2.11415.280, VS 17.14.36414.22
tvos                       26.2.10191/10.0.100      SDK 10.0.100
wasm-tools-net6            10.0.101/10.0.100        SDK 10.0.100, VS 17.14.36414.22
wasm-tools-net7            10.0.101/10.0.100        SDK 10.0.100, VS 17.14.36414.22

The only modification I made was to change the TargetFrameworks property to net10.0-ios in both MauiSample.csproj and NewBinding.MaciOS.Binding.csproj.

And during compilation, I got the following error :

clang++ exited with code 1:
Undefined symbols for architecture arm64:
  "_OBJC_CLASS_$_DotnetNewBinding", referenced from:
       in registrar.o
ld: symbol(s) not found for architecture arm64
clang++: error: linker command failed with exit code 1 (use -v to see invocation)

Could you try running MauiSample with both .net 10 and xcode 26.2 and provide an explanation of the error encountered?

You need to add [Protocol] on the ApiDefinitions.cs, but using the template never succeeded for me.

[Hamdev-Algo]

@bwinklesky Indeed, the project now compiles and works. Thank you for your help !

This does not solve our problem with our main project, but it shows that ios project binding can work under Maui .NET 10 and Xcode 26.2.

[bwinklesky]

@bwinklesky Indeed, the project now compiles and works. Thank you for your help !

This does not solve our problem with our main project, but it shows that ios project binding can work under Maui .NET 10 and Xcode 26.2.

@Hamdev-Algo My guess is that you will have trouble when you try to create new bindings and running a sharpie build (inside the .resources folder). If you get it working, I would be interested to know how you got it working.

[Ames]

Hello! I believe my team has been facing a similar error when migrating a native binding project to .NET 10 and thought I'd share part of our journey in case it helps anyone else.

Our app consumes the binding project as a NuGet package, and was failing to build with a linker error ...Undefined symbols for architecture arm64... which I know can mean a referenced binary is absent.

The binding csproj references our Swift wrapper library using XcodeProject and two third-party xcframework libraries using NativeReference. When targeting .NET 9 we were seeing all 3 in the output .resources directory, but with .NET 10 the one that used XcodeProject was no longer present. Eventually found that the dotnet pack command (rather than dotnet build ) seemed to have better results. This was likely because that command defaults to Release configuration, and indeed the issue only seemed to be happening when building for Debug.

Looking out at our Xcode Project there are some configurations that were overridden for Debug, and one that stood out was ONLY_ACTIVE_ARCH aka Build Active Architecture Only. It seems like a default that this is set to Yes for quicker debug cycles. After setting this to No / removing the line in the pbxproj, this also appears to help.

It still feels like a workaround but hope it could point towards a root issue.