Forum Xamarin.Android

System.Xml conflict between Version=4.0.0.0 and Version=2.0.5.0

jsagonjsagon BRMember

I have racked my brain all day long, but I can't figure out how to fix this conflict.

Message error: No way to resolve conflict between "System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" and "System.Xml, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e". Choosing "System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" arbitrarily.

This occurs only on release mode. I have tested it on debug mode and it works fine. However when I try it on release mode it doesn't work.

My project is using : Newtonsoft.Json, Xamarin.Android.Support.v4, Xamarin.Android.Support.v7.RecyclerView.
Everything is updated with the last version.

I've searched here and on Stackoverflow for solutions... there're some simulars questions, but the solutions didn't work for me. And I don't know how to change that Version described on the error.

Posts

  • SaifAsadSaifAsad USMember

    I am having the same issue, and it happens on both Debug and Release modes.

  • LeifHansLeifHans CAMember
    edited August 2016

    Same problem here. I am developing my Xamarin.Forms app on my Mac (Xamarin Studio) and everything is working fine.
    I just set up my new Windows 10 machine and cloned my forms project.
    After opening the project in Visual Studio 2015, I am getting the exact same error as you.

    No way to resolve conflict between "System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" and "System.Xml, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e". Choosing "System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" arbitrarily.

    My builds succeed for both Debug and Release but they wont deploy!

  • Same here...

    I think this is the reason why the following bug (that happens sometimes only) appears :

    Method 'System.Xml.XmlReader:get_DtdInfo ()' is inaccessible from method 'System.Xml.Linq.XContainer:ReadContentFrom (System.Xml.XmlReader,System.Xml.Linq.LoadOptions)'

  • GiyomuniceGiyomunice FRMember
    edited September 2016

    Hello, I have the same issue even when deploying a new blank app (Xamarin.Forms portable class).
    I can build/deploy on Windows platforms, and on the Android emulator, but not on my Android device.

    When I build, I get the same conflict errors and warnings. Here is my understanding up to now. If someone can help please…

    1st issue

    I first get this error. Indeed, whin I check the properties of the reference "System" in the Droid project, the version reads "2.5.0.0". I can right-click on "References"-> "add reference" to open the reference manager, where I browse to only find the System 2.5.0.0 version. However, when I double-click the reference, the Object Browser opens and I can see both System 2.5.0.0 and 4.0.0.0 versions. But I don’t know how to add the 4.0.0.0 to the project…

    No way to resolve conflict between "System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" and "System.Xml, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e". Choosing "System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" arbitrarily.
    Consider app.config remapping of assembly "System.Runtime, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" from Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Runtime\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Runtime.dll] to Version "4.1.0.0" [C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoAndroid\v1.0\Facades\System.Runtime.dll] to solve conflict and get rid of warning.

    2nd issue

    VS suggests to edit the app.config file with a long list of bindings like that: I tried but it does not work.

    C:\Program Files (x86)\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(2113,3): warning MSB3247: Found conflicts between different versions of the same dependent assembly. In Visual Studio, double-click this warning (or select it and press Enter) to fix the conflicts; otherwise, add the following binding redirects to the "runtime" node in the application configuration file: <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.Runtime" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" /><bindingRedirect oldVersion="0.0.0.0-4.1.0.0" newVersion="4.1.0.0" /></dependentAssembly>

    On Windows 10, I have :

    • VS 14.0.25425.01 update 3
    • Xamarin 4.2.0.628
    • Xamarin.Android 7.0.0.3

    The NuGet packages are up to:

    • Xamarin.Forms 2.3.1.114
    • Microsoft.NETCore.UniversalWindowsPlatform 5.2.2
    • Xamarin.Android.Support* classes to 23.3.0.
  • SeyyedSorooshSeyyedSoroosh USMember ✭✭

    ITNOA

    I have the same problem.

  • ChristianMuehleChristianMuehle DEUniversity

    Same here I´m getting crazy with this, has anybody an idea to solve it?

    I can debug
    I can build
    I can compile in release mode

    But I can´t publish, i just get a crash reported like:

    Package creation failed

    C:\Program Files (x86)\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(3,3): Error MSB4018: The "BuildApk" task failed unexpectedly. Xamarin.Tools.Zip.ZipException: Entry has been changed at Xamarin.Tools.Zip.ZipArchive.ReadEntry(UInt64 index) at Xamarin.Tools.Zip.ZipArchive.AddFile(String sourcePath, String archivePath, EntryPermissions permissions, CompressionMethod compressionMethod, Boolean overwriteExisting) at Xamarin.Android.Tasks.BuildApk.AddAssemblies(ZipArchive apk) at Xamarin.Android.Tasks.BuildApk.ExecuteWithAbi(String supportedAbis, String apkInputPath, String apkOutputPath) at Xamarin.Android.Tasks.BuildApk.Execute() at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute() at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__26.MoveNext() (MSB4018) (SBA.Droid)

  • ChristianMuehleChristianMuehle DEUniversity

    I want to report that the DLL from the comment 33 solved the issue for me.

    I can publish again, I still see some strange warnings but at least the APK is generated and working on our test devices

  • MathieuLeLutMathieuLeLut FRMember

    Hi, I'm still getting the same issue, does someone got a solution since this ticket was created ?

    I tried the DLL ChristianMuehle refered to, but it' only a more verbose dll for compiling.

    Automatic remaping app.config doesn't do anything, neither manual remapping.

    Here is my log behind :

    Impossible de résoudre le conflit entre "System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" et "System.Xml, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e". Choix arbitraire de "System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089".
    1>  Si possible, remappez app.config de l'assembly "System.Runtime, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" de la version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Runtime\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Runtime.dll] vers la version "4.1.0.0" [C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoAndroid\v1.0\Facades\System.Runtime.dll] pour résoudre le conflit et ne plus recevoir l'avertissement.
    1>  Si possible, remappez app.config de l'assembly "System.IO, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" de la version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.IO\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.IO.dll] vers la version "4.1.0.0" [C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoAndroid\v1.0\Facades\System.IO.dll] pour résoudre le conflit et ne plus recevoir l'avertissement.
    1>  Si possible, remappez app.config de l'assembly "System.Globalization, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" de la version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Globalization\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Globalization.dll] vers la version "4.0.10.0" [C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoAndroid\v1.0\Facades\System.Globalization.dll] pour résoudre le conflit et ne plus recevoir l'avertissement.
    1>  Si possible, remappez app.config de l'assembly "System.Diagnostics.Debug, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" de la version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Diagnostics.Debug\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Diagnostics.Debug.dll] vers la version "4.0.10.0" [C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoAndroid\v1.0\Facades\System.Diagnostics.Debug.dll] pour résoudre le conflit et ne plus recevoir l'avertissement.
    1>  Si possible, remappez app.config de l'assembly "System.Xml.ReaderWriter, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" de la version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Xml.ReaderWriter\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Xml.ReaderWriter.dll] vers la version "4.0.10.0" [C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoAndroid\v1.0\Facades\System.Xml.ReaderWriter.dll] pour résoudre le conflit et ne plus recevoir l'avertissement.
    1>  Si possible, remappez app.config de l'assembly "System.ObjectModel, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" de la version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.ObjectModel\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.ObjectModel.dll] vers la version "4.0.10.0" [C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoAndroid\v1.0\Facades\System.ObjectModel.dll] pour résoudre le conflit et ne plus recevoir l'avertissement.
    1>  Si possible, remappez app.config de l'assembly "System.Linq, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" de la version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Linq\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Linq.dll] vers la version "4.1.0.0" [C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoAndroid\v1.0\Facades\System.Linq.dll] pour résoudre le conflit et ne plus recevoir l'avertissement.
    1>  Si possible, remappez app.config de l'assembly "System.Runtime.Extensions, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" de la version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Runtime.Extensions\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Runtime.Extensions.dll] vers la version "4.1.0.0" [C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoAndroid\v1.0\Facades\System.Runtime.Extensions.dll] pour résoudre le conflit et ne plus recevoir l'avertissement.
    1>  Si possible, remappez app.config de l'assembly "System.Collections, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" de la version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Collections\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Collections.dll] vers la version "4.0.10.0" [C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoAndroid\v1.0\Facades\System.Collections.dll] pour résoudre le conflit et ne plus recevoir l'avertissement.
    1>  Si possible, remappez app.config de l'assembly "System.Threading, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" de la version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Threading\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Threading.dll] vers la version "4.0.10.0" [C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoAndroid\v1.0\Facades\System.Threading.dll] pour résoudre le conflit et ne plus recevoir l'avertissement.
    1>  Si possible, remappez app.config de l'assembly "System.Text.Encoding, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" de la version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Text.Encoding\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Text.Encoding.dll] vers la version "4.0.10.0" [C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoAndroid\v1.0\Facades\System.Text.Encoding.dll] pour résoudre le conflit et ne plus recevoir l'avertissement.
    1>  Si possible, remappez app.config de l'assembly "System.Reflection, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" de la version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Reflection\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Reflection.dll] vers la version "4.1.0.0" [C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoAndroid\v1.0\Facades\System.Reflection.dll] pour résoudre le conflit et ne plus recevoir l'avertissement.
    1>  Si possible, remappez app.config de l'assembly "System.Linq.Expressions, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" de la version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Linq.Expressions\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Linq.Expressions.dll] vers la version "4.1.0.0" [C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoAndroid\v1.0\Facades\System.Linq.Expressions.dll] pour résoudre le conflit et ne plus recevoir l'avertissement.
    1>  Si possible, remappez app.config de l'assembly "System.Text.RegularExpressions, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" de la version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Text.RegularExpressions\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Text.RegularExpressions.dll] vers la version "4.1.0.0" [C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoAndroid\v1.0\Facades\System.Text.RegularExpressions.dll] pour résoudre le conflit et ne plus recevoir l'avertissement.
    1>  Si possible, remappez app.config de l'assembly "System.Threading.Tasks, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" de la version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Threading.Tasks\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Threading.Tasks.dll] vers la version "4.0.10.0" [C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoAndroid\v1.0\Facades\System.Threading.Tasks.dll] pour résoudre le conflit et ne plus recevoir l'avertissement.
    1>  Si possible, remappez app.config de l'assembly "System.Dynamic.Runtime, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" de la version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Dynamic.Runtime\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Dynamic.Runtime.dll] vers la version "4.0.10.0" [C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoAndroid\v1.0\Facades\System.Dynamic.Runtime.dll] pour résoudre le conflit et ne plus recevoir l'avertissement.
    1>C:\Program Files (x86)\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(2113,3): warning MSB3247: des conflits entre différentes versions du même assembly dépendant ont été trouvés. Dans Visual Studio, double-cliquez sur cet avertissement (ou sélectionnez-le et appuyez sur Entrée) pour corriger les conflits ; sinon, ajoutez les redirections de liaison suivantes au nœud "runtime" dans le fichier de configuration de l'application : <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.Runtime" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" /><bindingRedirect oldVersion="0.0.0.0-4.1.0.0" newVersion="4.1.0.0" /></dependentAssembly></assemblyBinding><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.IO" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" /><bindingRedirect oldVersion="0.0.0.0-4.1.0.0" newVersion="4.1.0.0" /></dependentAssembly></assemblyBinding><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.Globalization" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" /><bindingRedirect oldVersion="0.0.0.0-4.0.10.0" newVersion="4.0.10.0" /></dependentAssembly></assemblyBinding><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.Diagnostics.Debug" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" /><bindingRedirect oldVersion="0.0.0.0-4.0.10.0" newVersion="4.0.10.0" /></dependentAssembly></assemblyBinding><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.Xml.ReaderWriter" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" /><bindingRedirect oldVersion="0.0.0.0-4.0.10.0" newVersion="4.0.10.0" /></dependentAssembly></assemblyBinding><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.ObjectModel" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" /><bindingRedirect oldVersion="0.0.0.0-4.0.10.0" newVersion="4.0.10.0" /></dependentAssembly></assemblyBinding><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.Linq" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" /><bindingRedirect oldVersion="0.0.0.0-4.1.0.0" newVersion="4.1.0.0" /></dependentAssembly></assemblyBinding><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.Runtime.Extensions" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" /><bindingRedirect oldVersion="0.0.0.0-4.1.0.0" newVersion="4.1.0.0" /></dependentAssembly></assemblyBinding><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.Collections" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" /><bindingRedirect oldVersion="0.0.0.0-4.0.10.0" newVersion="4.0.10.0" /></dependentAssembly></assemblyBinding><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.Threading" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" /><bindingRedirect oldVersion="0.0.0.0-4.0.10.0" newVersion="4.0.10.0" /></dependentAssembly></assemblyBinding><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.Text.Encoding" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" /><bindingRedirect oldVersion="0.0.0.0-4.0.10.0" newVersion="4.0.10.0" /></dependentAssembly></assemblyBinding><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.Reflection" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" /><bindingRedirect oldVersion="0.0.0.0-4.1.0.0" newVersion="4.1.0.0" /></dependentAssembly></assemblyBinding><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.Linq.Expressions" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" /><bindingRedirect oldVersion="0.0.0.0-4.1.0.0" newVersion="4.1.0.0" /></dependentAssembly></assemblyBinding><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.Text.RegularExpressions" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" /><bindingRedirect oldVersion="0.0.0.0-4.1.0.0" newVersion="4.1.0.0" /></dependentAssembly></assemblyBinding><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.Threading.Tasks" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" /><bindingRedirect oldVersion="0.0.0.0-4.0.10.0" newVersion="4.0.10.0" /></dependentAssembly></assemblyBinding><assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="System.Dynamic.Runtime" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" /><bindingRedirect oldVersion="0.0.0.0-4.0.10.0" newVersion="4.0.10.0" /></dependentAssembly></assemblyBinding>
    1>    Processing: C:\Users\Mathieu\git\my-project\my-project\my_project.Droid\obj\Debug\__library_projects__\ZXing.Net.Mobile.Forms.Android\library_project_imports\res\values\strings.xml
    1>    Processing: C:\Users\Mathieu\git\my-project\my-project\my_project.Droid\obj\Debug\__library_projects__\ZXingNetMobile\library_project_imports\res\layout\zxingscanneractivitylayout.xml
    1>    Processing: C:\Users\Mathieu\git\my-project\my-project\my_project.Droid\obj\Debug\__library_projects__\ZXingNetMobile\library_project_imports\res\layout\zxingscannerfragmentlayout.xml
    
  • AndreasSelleAndreasSelle DEBeta ✭✭

    I am getting exactly the same "No way to resolve conflict" warning every time. However, I just ignore it as I can still build a working APK.

  • ChristianMuehleChristianMuehle DEUniversity

    I can also just confirm that I´m able to build/generate the APK but I´m not able to solve the warning at all

  • JohnMillerJohnMiller USForum Administrator, Xamarin Team Xamurai

    Hey All,

    Would someone be able to upload a project that reproduces this message (Unable to resolve conflict...)? Please also include your version information. If you would prefer, feel free to PM me on the forums.

  • JohnMillerJohnMiller USForum Administrator, Xamarin Team Xamurai

    Hey All,

    I was able reproduce while looking at another bug. Please add any more information here: https://bugzilla.xamarin.com/show_bug.cgi?id=45130

  • ValgokuValgoku FRMember ✭✭

    MathieuLelut, did you solve your problem ? I exactly have the same problem...

  • IanChenIanChen USMember ✭✭

    Xamarin.Forms v2.3.2.127
    Visual Studio 2015 update Xamarin for stable last version
    have the same problem +1

  • TedRogersTedRogers USMember ✭✭✭✭

    Running into the same issue. I see the error as soon as I add the NuGet for Newtonsoft.Json to my project.

    Any resolution?

  • JohnBurrowsJohnBurrows USMember

    I'm getting the same issue
    Any resolution?

  • TedRogersTedRogers USMember ✭✭✭✭

    From looking at BugZilla it looks like this issue was fixed with " XVS 4.2.1.52". The question is when will that fix find its way to a build in the stable channel?

  • Same problem here,

    Have someone found the solution?

    In my case, this problem started after I updated Xamarin to the latest version. I'm not using any Nugget package

    thank you very much!

  • So, the solution I found to correct this problem was downgrade Xamarin for Visual Studio from Version 4.2 to Version 4.1.2

    https://store.xamarin.com/account/my/subscription/downloads

    Hope that helps

  • ajaxerajaxer AUMember ✭✭

    I have found an alternate solution that does not require downgrading XVS.

    Using the bug report from JohnMiller dated 7 October and the bugzilla bug he mentions, this leads to the fix that was implemented for an earlier bug that apparently was solved by a couple of tweaks to the build scripts for android only.
    Refer to the changes described by this commit:
    https://github.com/xamarin/xamarin-android/pull/273/files

    I modified my msbuild target files as described and all the System conflicts went away.

  • ClayBrinleeClayBrinlee USMember ✭✭

    Oct 2017 and I'm still seeing this.

  • DarshanJSDarshanJS USMember ✭✭✭✭

    @ClayBrinlee said:
    Oct 2017 and I'm still seeing this.

    Did you found solution for this

  • ClayBrinleeClayBrinlee USMember ✭✭

    @DarshanJS If you look at part of the error message it says: Choosing "System.Xml, Version=4.0.0.0 so it looks like it picks the most recent version anyway. The only reason I was even trying to resolve the issue was I was trying to troubleshoot something else and thought this might be the cause. Well, it wasn't the cause in the end anway. I don't think this is really much of an error that any of us should be worried about to be honest.

Sign In or Register to comment.