New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Paket doesn't properly respect MonoAndroid7.0 dependencies on Xamarin.Forms package #2762
Comments
@forki it seems like finally they got us ;) |
oh myy... |
what's the scoop? |
So I guess you don't want to build for MonoAndroid1? I guess you might be able to filter that with framework restrictions .. |
Paket by default/design tries to find a global solution of packages valid to compile for all frameworks. It will not (like Nuget) allow different versions of a single package. Paket tells you that such a solution doesn't exist for your specified dependencies... So you can either change your version or tell paket you don't care about monoandroid framework |
== on the other hand should work as well if applied to the correct packages, but you basically will have an unsound resolution in that case. |
Ah, so simple. Works :)
|
to make it very clear: This is abuse of the concept of a package. I wished MS would be more careful... |
Description
Xamarin.Forms >= 2.3.4 depends Xamarin.Android.Support.* packages >= 23.3, but for MonoAndroid1, it is pinned at exactly 23.3.
Paket always assumes it needs to be exactly 23.3
Repro steps
This paket.dependencies file will fail:
Expected behavior
Same as NuGet, both packages must install, as they're compatible
Actual behavior
Known workarounds
Event specifying
==
doesn't work, withnuget Xamarin.Android.Support.v7.AppCompat == 25.4.0.2
:Conflict detected: - Dependencies file requested package Xamarin.Android.Support.v7.AppCompat: == 25.4.0.2 - Xamarin.Android.Support.Design 25.4.0.2 requested package Xamarin.Android.Support.v7.AppCompat: 25.4.0.2 - Xamarin.Forms 2.3.4.231 requested package Xamarin.Android.Support.v7.AppCompat: 23.3
The text was updated successfully, but these errors were encountered: