-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as off-topic.
This comment was marked as off-topic.
I am using the latest available version 5.0.0.2578 and I am getting below error. Can someone please update how to fix it!
|
@siddhant-maurya look a few comments up, that person had the same issue |
@jfversluis Thanks for the quick response. I tried adding Xamarin.AndroidX.AppCompat 1.6.1 but after many attempts I am still getting the same error. |
@siddhant-maurya you are using the wrong XF version. |
I am not able to find XF version 5.0.0.8491 in Nuget pkg manager or anywhere else can you please suggest how to get it. Iam using VS 2022 17.5.4 |
add this feed as nuget source: https://aka.ms/forms-prs/index.json to get the nugets for Pull Requests |
I have upgraded to XF version 5.0.0.8491 but now it's giving me some other errors -
|
remove this Scanbot.Xamarin.SDK.Dependencies and only use official AndroidX libs from Xamarin team |
got it removed the Scanbot SDK and worked ! Thanks a lot :) |
nice to hear this and build is green again 🥳 @jfversluis |
Yeah it seems like LiveData 2.6.1 is causing issues, so I think I will go with this for now |
ok, I tested 5.0.0.8503 and for me it works and I only get the now expected LiveData out of range warning |
It's weird that it let's you install the latest version though because I limit it through the nuspec. Is that not enforced anymore? Did that change? |
I don't configure that warnings are treated as errors, so this works. |
I created a complete new app in VS2022 without any additional androidx references, updated to 5.0.0.8503 and see those warnings:
|
Hm yeah I probably need to update the templates as well to use this new version directly. And maybe some blog post or something to explain what is going on here 😅 |
yes, this is a breaking change that should be tested and documented well. A bit offtopic, maybe also retarget Essentials to 13.0 to match the new XF version. |
How does one get this before it makes its way to NuGet? |
there are preview nugets packages on nuget.org |
@jfversluis when are we to expect a release version that includes these changes? the deadline for app submissions is looming... |
hello? @jfversluis @jamesmontemagno |
I suspect it takes some time for 3rd party control vendors to update their libs as they also need to rebuild their controls for MAUI. Syncfusion is known to always target old XF / MAUI versions and I guess they may need some time to test their controls against new AndroidX libs. |
This builds Xamarin.Forms with the MonoAndroid 13.0 target. With this we can now use the latest Android(X) packages again and should be more prepared for future Android versions and targets.
However, this change is pretty significant as also a lot of the dependencies got a good bump in their version numbers. Please test your code carefully!
Fixes #15668
Fixes #15678
Fixes #15677
Fixes #15714
Also see xamarin/Essentials#2087