[Bug] Incorrect version of System.Numerics.Vectors is installed

[JanNepras]

Description

We are implementing our own internal nuget package using "Cross-Platform .NET Standard Library Plugin" template. In this project we would like to consume Xamarin.Essentials nuget package. Once Xamarin.Essentials is installed there is incorrect version of System.Numerics.Vectors (4.5.0 instead of 2.0.5.0) linked to project. When I try to retrieve data from accelerometer like this:

var x = e.Reading.Acceleration.X

I got the error: Error CS0012: The type 'Vector3' is defined in an assembly that is not referenced. You must add a reference to assembly 'System.Numerics, Version=2.0.5.0

I tried to install Xamarin.Essentials into Xamarin.Forms project and it installs correct version.

Steps to Reproduce

1. Create project using "Cross-Platform .NET Standard Library Plugin" template
2. Install Xamarin.Essentials into this project
3. Implement Accelerometer_ReadingChanged event in any .apple.cs class
4. Try to access coordinates in this event like this e.Reading.Accelration.X

Expected Behavior

The version of System.Numerics.Vectors should be 2.0.5.0

Actual Behavior

The version of System.Numerics.Vectors is 4.5.0

Basic Information

• Version with issue: I tried all versions of Xamarin.Essentials
• Last known good version: NA
• IDE: Visual Studio 2017 and 2019

Screenshots

[KatoNamus]

Running through a Microsoft Graph tutorial and got this warning. This issue breaks the tutorial as the app starts, can't do what it's supposed to and then closes immediately.

[mozesa]

I have the same problem with JetBrains Rider new Xamarin.Android project. Adding manually them as references solves the problem.

<Reference Include="System.Numerics" />
<Reference Include="System.Numerics.Vectors" />

[MrMacvos]

Issue still there, on macOS, but only when I build for iOS, I get this warning:

There was a conflict between "System.Numerics.Vectors, Version=2.0.5.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" and "System.Numerics.Vectors, Version=4.1.3.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a".
    "System.Numerics.Vectors, Version=2.0.5.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" was chosen because it was primary and "System.Numerics.Vectors, Version=4.1.3.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" was not.

What I don't understand is that the version number shown in the project is 4.5.0

I tried removing and re-adding the package, which didn't help.

[burrowj]

I just upgraded to latest version of a few things and now i get this. It seems to be a dependency of system.text.json

Reference Include="System.Numerics" Reference Include="System.Numerics.Vectors"

did not help

[jvannor]

VS2022; new mobile app (iOS, Android); blank template; build -> clean. Add package reference to IdentityModel.OidcClient (4.0.0); build -> system.numerics.vectors warnings

:(

[Chocopro713]

The problem just happened to me, after trying many things, I just found the solution.

I went to the project directory and deleted the bin and obj folders of each solution (project, project.Android and project.iOS)

I went back to VS 2019 for mac, I cleaned the project and rebuilt it, then I ran it and it worked for me

But the problem continues after the first run

:/

Although if you run it on your physical device it works 🥳

[vppetrov]

Problem still exists with Android today.

[sancilla]

Everything is updated and the error is still present. Are these "developers" really 12-years-old or what???

SOMEBODY GET UP FROM YOUR ASS AND FIX THIS (or at least hire a real programmer to do it)

[ivanrlg]

Hello I am getting the same error, any workaround?

[tomasfil]

Same issue

[KatoNamus]

Looks like it's sorted in Preview 3 (just out)

[vppetrov]

Preview 3 of what?

[KatoNamus]

Visual Studio 2022

[vppetrov]

This problem exists on Windows, VS 2022 has been released for Windows.

[rbottern]

Hello I am getting the same error, any workaround?

I removed the NuGet 'RestSharp' package which was referencing 'System.Numeric.Vectors' fro the Project, and that resolved the Error/Warning. 'System.Text.Json' seem to be another possible problem, but I did not have that one.

[JaimeSantosS]

This prevents me from creating the archive to publish my app on IOS. When I am debugging the problem doesn't appear, only when I am generating the archive.

I have been able to solve the problem twice but these methods worked for just 1 archive (the warning never disappeared), the first time I solved it by deleting all bin and debug files. The second time I updated all nugget Packages.

Is there any workaround to generate the archive?

[marwalsch]

@KatoNamus @vppetrov It's gone in the VS 2022 preview because it supports mobile development on .NET 6. The stable release, however, only supports .NET 5 as of now in which the issue is not resolved yet ᵃᶠᵗᵉʳ ᵃˡᵐᵒˢᵗ ᵗʰʳᵉᵉ ʸᵉᵃʳˢ

[Kalindu-Abeysinghe]

I still get the error in VS 2022 which uses .NET 6

[restorepro]

I am also getting this error using visual studio for mac. Its my Android project... Ughhh

[mikequ-taggysoft]

Same issue here. VS 2022. Every package up to date.

[m-schoder]

Same Issue here

[linda-dge]

Same Issue.

[jangarach]

Haven't been able to resolve this issue yet?

[rbottern]

I am not getting this anymore. I have:

• VS 2022 - 17.1.0
• netstandard2.1 Which includes: System.Numerics.Vectors 4.1.5.0
• RestSharp 106.15.0
• XamarinEssentials 1.7.0

I have been able to publish my App from Windows instance (via a Mac machine) to Apple Developer Site just fine.

[tangteng78]

I am not getting this anymore. I have:

• VS 2022 - 17.1.0
• netstandard2.1 Which includes: System.Numerics.Vectors 4.1.5.0
• RestSharp 106.15.0
• XamarinEssentials 1.7.0

I have been able to publish my App from Windows instance (via a Mac machine) to Apple Developer Site just fine.

Hi sir, How and where do you install the netstandard2.1? I'm seeing the same issue as the rest of the guys, been searching for the solution for weeks :(

Appreciate every help needed

[rbottern]

You set netstandard2.1 in your Project Properties:

Also, make sure to include the iTunes Package to be have a valid IPA file to upload.

That should do it. P.s. No need to "Archive" anymore! Just use the generated IPA File.

[tangteng78]

P.s. No need to "Archive" anymore! Just use the generated IPA File.

Hi sir, Few clarification: 1) Do you have the details of how to generate the IPA file and how to use it for publication for the iOS? Can't seem to be able to find these info from the internet :( 2) Even if the error, we can get the generated IPA (still seeing the error from my end)?

[rbottern]

The checkbox above "Build iTunes Package Archive (IPA)" is indicating that an IPA file will be generated in your Build Folder. Just search your Project Folder for it.

Note! Make sure to select 'Remote Device' when Building the Application (in 'Release' mode)

Then just use your Mac Machine to upload the File.

[rbottern]

Also, don't forget to define your info.plist

[tangteng78]

Oh man, still can't get rid of the same warning on PC, none an issue on Android, as it's able to be archived. However, it's error on Mac (I have a Mac machine as well) if to be archived thus it's a showstopper for publication.

PS: Weird that, it still works fine on direct deploy on iPhone though (it's just a warning during build)

Warning Found conflicts between different versions of "System.Numerics.Vectors" that could not be resolved. There was a conflict between "System.Numerics.Vectors, Version=2.0.5.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" and "System.Numerics.Vectors, Version=4.1.3.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a". "System.Numerics.Vectors, Version=2.0.5.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" was chosen because it was primary and "System.Numerics.Vectors, Version=4.1.3.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" was not. References which depend on "System.Numerics.Vectors, Version=2.0.5.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" [C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\ReferenceAssemblies\Microsoft\Framework\MonoAndroid\v1.0\System.Numerics.Vectors.dll].

Just curios if anyone has able to overcome this error ?

[mikequ-taggysoft]

I don't think this issue is limited to Xamarin.Essentials. It's the Xamarin base framework referencing some outdated/conflicting DLLs.

I can repro these warnings by creating a blank Xamarin.Forms project in VS 2022 (enable both iOS and Android), then add a nuget package such as System.Text.Json. Instant conflict.

This issue is basically mentioned all over MS sites/SO etc.

[tangteng78]

Just curios, if there is there any workaround on this error as of today? As it's a showstopper for the iOS publication :(

[marwalsch]

@tangteng78

if to be archived thus it's a showstopper for publication.

Have you tried this and can confirm this actually prevents publication? I'm building on a remote Mac on Visual Studio and warnings do not prevent me from creating the archive itself. Will it still be rejected if attempting to upload it to App Store Connect?

[tangteng78]

@tangteng78

if to be archived thus it's a showstopper for publication.

Have you tried this and can confirm this actually prevents publication? I'm building on a remote Mac on Visual Studio and warnings do not prevent me from creating the archive itself. Will it still be rejected if attempting to upload it to App Store Connect?

Hi sir, sorry for the confusion. What I meant was I can't archive it on my Mac due to this. It's an error when I tried to archive it.

[marwalsch]

@tangteng78

If that's the case and you have a windows machine I suggest attempting to connect Visual Studio for Windows to the Mac and build remotely. I never experienced this warning being an issue for archiving itself, at least not for Ad-hoc builds. I am merely asking how other individuals are experiencing this as a showstopper to publication and not just a really annoying warning since I haven't experienced the former yet. I already gave up on finding a work-around and am hoping it just disappears when migrating to .NET 6.

[tangteng78]

@marwalsch Oh that is a good tip, in fact I'm working on the code on my PC actually :) I'm already at wits' end trying to overcome this showstopper at Mac machine.

Reason why I tried building it on Mac as I can't seem to be able to find any guide or reference how to build, archive and publish to Apple Store on Windows machine.

Do you happen to have any website or link that has this step-by-step on how to publish to Apple Store via windows machine? That would be a super great help if you are able to point me to the right direction :)

[marwalsch]

@tangteng78

Do you happen to have any website or link that has this step-by-step on how to publish to Apple Store via windows machine?

You can't AFAIK, at least not directly. And since Visual Studio recently completely broke compatibility with Apple's developer API it even became a whole bit more complicated. I can only confirm that this works for Ad-hoc builds, but I suppose it works for App Store distribution as well. Just follow the improved and detailed work-around suggested in the thread. The general idea is as follows:

• Create your certs and profiles on Apple Developer;
• download them onto your Windows machine;
• add them through Visual Studio (this what Visual Studio would do for you via network if it weren't for the bug);
• ensure you are connected to your remote Mac build host;
• build your project as Ad-hoc (I assume release mode would be required for distribution);
• if you you followed all steps you should find the .ipa file on your output directory;
• i found the easiest way to upload it is to drag it onto the Mac and use the Transporter app.

I got up to the point where my archive was being validated inside App Store Connect, then it broke because of invalid entitlements (a framework related quirk). I don't know whether this merely works because i was distributing Ad-hoc (and validation is less strict) or because entitlement validation failed before other issues could surface.

My assumption/hope is that if you get as far as creating an archive, you are beyond the point where source-code related warnings affect the validations. If you or someone else could confirm/deny this I would be happy to hear.

EDIT: I can now confirm that publication works for internal Testflight builds, not seeing how the warning should be of any concern from that point on. It's still an absolute pest.

[rbottern]

The process outlined by "Marwalsch" is exactly what I am doing, although I don't have to use "Ad-Hoc", works fine for me with "Release".