Strip error code 1 symbols referenced by indirect symbol table entries that can't be stripped

[Hamdev-Arnaud]

CameraTest_Release_AnyCPU_Build_2026-07-07T10_30_13.9701092+02_00.zip

Apple platform

iOS

Framework version

net10.0-*

Affected platform version

VS 2026 18.7.3

Description

Since the last update of VS to version 18.7.3 and the workload update on my pc to those versions:
Workload version: 10.0.300.3

Installed Workload Id Manifest Version Installation Source
android 36.1.53/10.0.100 SDK 10.0.300, VS 18.7.11925.98, VS 17.14.37411.7
ios 26.5.10284/10.0.100 SDK 10.0.300, VS 18.7.11925.98, VS 17.14.37411.7
maccatalyst 26.5.10284/10.0.100 SDK 10.0.300, VS 18.7.11925.98, VS 17.14.37411.7
maui 10.0.20/10.0.100 SDK 10.0.300
maui-windows 10.0.20/10.0.100 SDK 10.0.300, VS 18.7.11925.98, VS 17.14.37411.7
wasm-tools 10.0.108/10.0.100 SDK 10.0.300, VS 18.7.11925.98, VS 17.14.37411.7

Maui Version used 10.0.80
Xcode Version 26.6

We are again blocked during the build of our test project (just a project with a binding framework to open the ios camera ) included in this ticket only during the release build with the following error :
strip exited with code 1:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/strip: error: symbols referenced by indirect symbol table entries that can't be stripped in: /Users/arnaudberard/Library/Caches/maui/PairToMac/Builds/CameraTest/ec19af5832c10faf2d4bac2e1c047ab51299f8497a3d15e941c97410c0f9823a/bin/Release/net10.0-ios/ios-arm64/CameraTest.app/Frameworks/CameraFramework.framework/CameraFramework
_dispatch_once
_objc_alloc_init
_objc_msgSendSuper2
_objc_release
_objc_retain
_objc_retainAutoreleaseReturnValue
_objc_retainAutoreleasedReturnValue
_objc_storeStrong
_objc_msgSend
__NSConcreteStackBlock
_AVCaptureSessionPresetHigh
_AVLayerVideoGravityResizeAspectFill
_AVMediaTypeVideo

It seems that something changed because everything was fine until I update my Visual Studio.

CameraProjects0707.zip

So if you can help with that problem it will help our project a lot.

Steps to Reproduce

Create a project with a native binding framework(OBJ C) included in a nugget
Build in release paired to a mac
Error during the link phase

Did you find any workaround?

Disable the strip native debug symbol for release

Build logs

No response

[Hamdev-Arnaud]

Just to precise that the last version where it was working well was VS 18.6.2 with those workloads :
Workload version: 10.0.300-manifests.e0989437
Installed Workload Id Manifest Version Installation Source

android 36.1.43/10.0.100 VS 18.6.11822.322, VS 17.14.37411.7
ios 26.2.10233/10.0.100 VS 18.6.11822.322, VS 17.14.37411.7
maccatalyst 26.2.10233/10.0.100 VS 18.6.11822.322, VS 17.14.37411.7
macos 26.2.10233/10.0.100 VS 18.6.11822.322, VS 17.14.37411.7
maui-windows 10.0.20/10.0.100 VS 18.6.11822.322, VS 17.14.37411.7
wasm-tools-net6 10.0.108/10.0.100 VS 18.6.11822.322, VS 17.14.37411.7
wasm-tools-net7 10.0.108/10.0.100 VS 18.6.11822.322, VS 17.14.37411.7

[rolfbjarne]

Thanks for the report!

I can reproduce the problem, I'll have a look and see what I can find out.

[rolfbjarne]

Can you try removing this line from your binding project, and see if that works for you?

<NoBindingEmbedding>false</NoBindingEmbedding>

[Hamdev-Arnaud]

Same result even after I deleted bin/obj folder and try to rebuild the project.

CameraTest_Release_AnyCPU_Build_2026-07-07T17_55_37.0843298+02_00.zip

[rolfbjarne]

Same result even after I deleted bin/obj folder and try to rebuild the project.

The test project references the native framework using a NuGet; did you update the NuGet after changing the binding project? Also if you don't change the version number (and bump the version in your main project's PackageReference), and the old NuGet is already cached, you'll get the old NuGet during the build.

[Hamdev-Arnaud]

You're right, I had missed that step — sorry about that.
After updating the NuGet package and bumping the version number, the build succeeded. Thanks for your help!
So the fix is to remove this line from our binding project ?

[rolfbjarne]

So the fix is to remove this line from our binding project ?

Yes, that's correct.

FWIW NoBindingEmbedding=false will eventually be deprecated, so the fix is also a change that will be required at some point in the future anyway.

[rolfbjarne]

But I'll fix the problem on our side too!

[Hamdev-Arnaud]

Ok thanks for your help @rolfbjarne I will inform my team about that.