Issue: error compiling app (while using SocketMobile.Capture) targeting iOS with maui in .NET9.0

[rporto]

Your Socket Mobile Developer ID

79A57E81-F63B-460D-960A-EEEEB744B801

Environment

Visual Studio Professional 2022, using a Maui Application project targetting Android and iOS.
SocketMobile.Capture nuget version 2.0.19.509
Device is iPhone 16 Pro connected to a Mac (the Mac is paired to the Visual Studio machine)

Description

When compiling with the iphone connected to the Mac (which is paired to the visual studio laptop), i get a compilation error with this message:

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.

Steps to Reproduce

1. add nuget to project
2. connect iphone to mac
3. rebuild using visual studio
4. error shows ate the end of compilation

Expected Behavior

When compiling with an android tablet, the compilation works and the app runs in android and i can scan without issues.

Compiling for a connected iphone should just work like android.

Actual Behavior

compilation 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

I followed some suggestions from ChatGpt, Copilot and Gemini. No luck.
Deleted project temporary folders in visual studio (obj and bin); deleted temporary folders in the mac; disconnected, forgot, and paired with mac again; removed linking from the compilation process (just in case).
Nothing worked.

Every single time i compile and get the error i can see the folder "../obj/Debug/net9.0-ios/ios-arm64/linker-cache/CaptureSDK.framework/" with all files showing 0 kb size, which is obviously wrong.

[rporto]

after reading related (closed) issues in here, i followed these steps:

• updated Visual Studio Professional 2022 to the latest build, Version 17.14.29 (March 2026)
• updated Xcode from 26.0 to 26.2 (required once i updated the workloads in VS)
• set the registry key LongPathsEnabled = 1
• repaired/updated workloads in both windows laptop and mac

When i compile now it DOES NOT shows the original error (... CaptureSDK.framework/CaptureSDK' is not a valid framework: Unable to read beyond the end of the stream.). The compiling finishes WITHOUT ERROR but it now has a WARNING saying

C:\Program Files\dotnet\packs\Microsoft.iOS.Windows.Sdk.net9.0_26.2\26.2.9000\tools\msbuild\iOS\Xamarin.iOS.Common.After.targets(387,3): warning IL2007: Could not resolve assembly 'SocketMobile.Capture'.

So we traded an error for an equally bad warning because even though it loads my app in the iphone now, when i try to connect to the scanner doing this:

socketCapture.OpenAsync(PackageName, SocketDeveloperId, SocketAppKey);

It returns -93, which makes sense since VS could not resolve the socket assembly while compiling

[Benjamin-Socket]

Hello @rporto,

Thank you for reaching out. I'll look into the IL2007 warning. However, the -93 error indicates that your app credentials are incorrect. The most common mistake is the that has to be formatted as follow: ios:<PackageName> for iOS.

For example:

PackageName = com.myapp.allyoucanscan

socketCapture.OpenAsync(ios:com.myapp.allyoucanscan, SocketDeveloperId, SocketAppKey);

Since the app worked on Android I assume you did use the android: prefix for Android already.

Also what is recommended in your case, is to register both the iOS and Android on Socket Mobile's Developer Portal so that you have a unique SocketAppKey for each apps.

Regards,

Benjamin Goltz
SDK Engineer
Socket Mobile

[rporto]

Hi Benjamin,

Thank you for the quick response. It worked !!
You were right, the "ios:" prefix was missing for the package name. I had not seen in any documentation or sample that part, even though i should have suspected it since I have been using "android:" prefix for my android apps.
I guess the fact that the compiler was giving that warning IL2007- Could not resolve assembly 'SocketMobile.Capture' let me to believe the assemblies were not being properly deployed to the iphone so it never occurred to me that the credentials could be wrong.

It is working perfectly now.
I wonder about that warning though.

On the other hand, yes, i registered both applications separatedly in the socket portal so each have its own key.

Thank you again.

Raciel