Issue: CaptureSDK is not a valid framework

[IntegraSysIncJP]

Your Socket Mobile Developer ID

726c6cfd-8c1e-e911-a979-000d3a363879

Environment

OS Version - .Net 9 running ios framework 26.0.9752
CaptureSDK Version - 1.7.112.395 nuget
Capture Device - D840
Xcode - 26.0

Description

When trying to build either release or debug from Windows Visual Studio Insiders connected to my Mac, after updating workloads to ios 26, I get the below error.
File 'obj/Debug/net9.0-ios/ios-arm64/linker-cache/CaptureSDK.framework/CaptureSDK' is not a valid framework: Unable to read beyond the end of the stream.

This doesn't happen when using JetBrains, probably because it builds directly on the Mac.

Steps to Reproduce

Open attached project zip.
Attach Visual Studio running ios framework 26 to a Mac using XCode 26
Attempt either debug or release build

Expected Behavior

Expected result is to compile

Actual Behavior

Does not compile and gives this error
File 'obj/Debug/net9.0-ios/ios-arm64/linker-cache/CaptureSDK.framework/CaptureSDK is not a valid framework: Unable to read beyond the end of the stream.

Additional Context

MauiTestApp.zip

[Benjamin-Socket]

Hello @IntegraSysIncJP,

Thank you for the detailed information and for providing a test app. I'll check what is going on.

Regards,

Benjamin Goltz
SDK Engineer
Socket Mobile

[Benjamin-Socket]

Hello @IntegraSysIncJP,

I was able to reproduce the error with the environment you described. It seems that the issue is coming from Visual Studio and the .Net version it is using to build the app. Visual studio is forcing the usage of his version of .Net through the Mac

Could you provide the following information?

• What version of Visual Studio are you using? This will give me exactly what tools Visual Studio is using
• To compare with JetBrains, what .Net version is installed on your Mac, also could you provide the .Net Maui iOS workload version

Also, did you have a previous Visual Studio, .Net, Xcode setup that was working?

Regards,
Benjamin

[IntegraSysIncJP]

Hi Benjamin,

Windows (Primary Build Machine)

Visual Studio:

Microsoft Visual Studio Professional 2022 (64-bit) – Current

Version 17.14.19

.NET Framework version: 4.8.09221

Installed SDKs:

7.0.410
8.0.203
8.0.415
9.0.203
9.0.306
9.0.307
10.0.100

I also have a global.json that "should" force the build to use 9.0.306.

Mac side

Mac (Build Host Used by Visual Studio + JetBrains Rider)
dotnet --list-sdks:
6.0.425
7.0.317
8.0.403
9.0.301
9.0.306

Shared runtimes:

Microsoft.NETCore.App 9.0.6

Microsoft.NETCore.App 9.0.10

I don't remember what Visual Studio version was working, but this problem didn't pop up until another wonderful Microsoft workloads update which I believe forced .Net 10 down our throats.

If you need anything else please let me know.
James

[johncrowleydev]

I'm experiencing this same issue after upgrading to XCode 26. Is there a workaround I can use to build my app in the meantime while this is fixed?

[Benjamin-Socket]

Hi James,

Thank you for sharing your information. I'm still having issues finding what is going on exactly but I'll spend more time on this issue next week.

Hi @johncrowleydev,

I'm not accustomed to JetBrains, but I found a workaround to build the the project on Mac directly. Using .Net CLI and Visual Studio Code as IDE (not required but still good to have) you can use this command:

dotnet build -f net9.0-ios -r ios-arm64

If you must use XCode 26, then you should probably update your .Net workloads too with:

dotnet workload update

Note: Building the project without the -r ios-arm64 targets the iOS simulator and the same issue stated above also appears:

File 'obj/Debug/net9.0-ios/ios-arm64/iossimulator-arm64/linker-cache/CaptureSDK.framework/CaptureSDK' is not a valid framework: Unable to read beyond the end of the stream.

Thanks,
Benjamin

[johncrowleydev]

@Benjamin-Socket thank you. I don't have JetBrains but was able to build on my Mac just using dotnet CLI. Definitely still awaiting the resolution of this issue though so I can run on simulator.

[Benjamin-Socket]

Hi @IntegraSysIncJP @johncrowleydev,

My apology for the delayed response. I had some trouble finding clues about what was going on. The issue is still not fixed but I found some new leads.

It seems that embedded libraries are causing this issue and not correctly being extracted. The recent versions of Visual Studio did add new restrictions on those and I am currently exploring available solutions. This will require some extra time to solve, test and implement.

Thank you for your patience.

Thanks,
Benjamin

[mkeoppelCG4]

I'm also seeing the same issues with the recently released .net10 and xcode26. Looking forward to a solution. Thanks!

[mkeoppelCG4]

@Benjamin-Socket Have you been able to make any progress on this item? Thanks!

[Benjamin-Socket]

@mkeoppelCG4 @johncrowleydev @IntegraSysIncJP I was not able to find a solution to this issue. Visual Studio made some updates that are not compatible with the SDK's architecture.

Where it breaks, the SocketMobile.Capture SDK has a native library embedded in a .dll for. When Visual Studio extracts this embedded library, all files are empty and shouldn't be... this is why the error: File 'obj/Debug/net9.0-ios/ios-arm64/linker-cache/CaptureSDK.framework/CaptureSDK' is not a valid framework: Unable to read beyond the end of the stream. is showing.

For now, avoiding Visual Studio until it makes updates and using JetBrains seems to be the workaround.

If Visual Studio does not solve this, I'll have to re-think the architecture of the SDK.

I hope this is not too troublesome for now...

In the meantime, I wish you all happy holidays!

Thanks,
Benjamin

[johncrowleydev]

@Benjamin-Socket That's unfortunate as it is a lot more convenient to build and debug our iOS app from Visual Studio. Thanks for your work looking into this for us; hope they resolve it in the future.