-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[Bug] SR4 conflicts with most of the latest nugets like Xamarin.Firebase.Ads #14417
Comments
Yeah something is not right or intended not sure |
I also see this when following the advice to add AndroidX nugets directly
|
You can manually force the libraries by editing your head android project. Edit in the following: <PackageReference Include="Xamarin.Forms" Version="5.0.0.2083" />
<PackageReference Include="Xamarin.AndroidX.Core" Version="1.6.0" />
<PackageReference Include="Xamarin.AndroidX.Lifecycle.LiveData" Version="2.3.1" /> This allows you to break the upper bound version enforcement (add any other libs that may have been missed). I've been doing this for months to keep pushing forward with other AndroidX libraries and XF hasn't had an issue that I can see from the updates. |
Thank you @aritchie |
Any movement? It's beyond annoying to not be able to update Xamarin.Forms. It was always a fools hope, but every once in a while I dream of doing package updates and getting fixes to long-standing bugs. |
Simply add packages this way:
to skip the NU1608 warning. The only package you need to limit to 1.3 is the Google Material, 1.4 has breaking changes |
It looks like some/most/all of these issues are getting resolved thanks to #14506. It's listed to be in the latest service release, but I cannot find it on nuget.org yet. @jsuarezruiz Hey sorry to ping you, but is 5.0.0-sr5 still coming to nuget.org? I checked for whether there might just be some CD automation still running, but I haven't been able to find any. |
Same question, sr5 is not on nuget but listed on the releases here, is there a reason for it? |
5.0.0.2125 is available on NuGet now and fixes this issue for me. |
Description
I just upgraded to SR4, however most upgrades leads to conflicts with the Android dependencies.
Just an example:
@PureWeen
Could this be caused by this PR?
#14101
Some plugins needed amarin.AndroidX.Lifecycle.LiveData > 2.3.0 which I've tried so far.
Workarround
See this comment: #14417 (comment)
The text was updated successfully, but these errors were encountered: