"No matching framework found" error for NuGet package

[carljohansen]

I have suddenly started getting this compilation error:

C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk.net9.0_18.5\18.5.9215\tools\msbuild\Xamarin.Shared.targets(158,3): error 

No matching framework found inside 'xxx\.nuget\packages\devexpress.maui.collectionview\24.1.12\lib\net8.0-ios15.4\DXCollectionView.i.resources\DXListView.xcframework'. 
SupportedPlatform: 'xxx\.nuget\packages\devexpress.maui.collectionview\24.1.12\lib\net8.0-ios15.4\DXCollectionView.i.resources\DXListView.xcframework', SupportedPlatformVariant: 'ios', SupportedArchitectures: ''.

I haven't touched that package. It was all working yesterday and now has suddenly stopped working. This error happens when I try to deploy to Android devices (even though it seems to be an iOS issue). The only thing that still works is debugging on Android emulators - not sure why that's not affected.

I have noticed that in the world of Android and iOS, platforms are declared obsolete about five minutes after they are released. I live in constant fear of things that are working perfectly well suddenly being deemed unusable (especially when the thing in question is a slightly old package that I depend on). Is that the issue here?

[rokmeglic71]

Is this similar bug reference? Can CoPilot answer help you?

[carljohansen]

Not really. There seems to be no rhyme or reason to it. Now I'm finding that I can debug against an Android device in VS, but if I right-click the same Maui project in VS and choose Deploy (Debug configuration), the compilation fails with the above error.

[rokmeglic71]

@carljohansen OK; so it is a configuration issue? Depending on your debug configuration, you get the error. Maybe you could check Properties and/or Edit Project file to test different combinations and try to find the combination that works. Check CoPilot updated answer based on your input.

[carljohansen]

As if to demonstrate how I have no idea what is going on... the problem seems to have something to do with this line:

<RuntimeIdentifier>ios-arm64</RuntimeIdentifier>

I have had that line for years (can't remember why). Now suddenly it seems to be causing this "No matching framework found" error. I say "causing" only because the error seems to go away when I remove that line. If removing that line breaks something else, well, I haven't found it yet.

[rokmeglic71]

Learning from here.

If a RuntimeIdentifier isn't specified when building remotely using Visual Studio on Windows, the IDE will detect the architecture of the remote Mac and set it accordingly. Overriding the default can be achieved by setting the $(ForceSimulatorX64ArchitectureInIDE) build property:

I think this is the case for you. You removed the RuntimeIdentifier and it started to work, because it was automatically detected. CoPilot AI has similar opinion.