-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Conversation
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
API 21 is failing |
Will this ever be merged? Android release builds are broken right now as linking fails. "Mono.Cecil.ResolutionException: Failed to resolve AndroidX.Core.View.Accessibiity.AccessibilityNodeInfoCompat" <-- notice the misspelling. #13969 was closed but it appears as this hasn't been merged yet so I don't think it's fixed. Also, imagine new people starting to use XF and builds just won't work for them, wouldn't it make sense to merge this in soon and make a new release? I think that the ability to produce builds is an important feature. Thank you. |
This PR will be included in the next Release. |
Fantastic, thank you!! |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Can we align this with the Community Toolkit & Xamarin.Essentials. |
@mattleibow @jfversluis @jsuarezruiz ? FYI this PR is pinning AndroidX upper versions |
Why are the dependencies now restricted in Xamarin.Forms 5.0.0.2083? |
The commit that introduced that says just “fix versioning”: fbb37d9 Maybe create a bug report for better visibility? |
I created an issue for this. |
* Bump a few Android X projects to fix incompatibilities * Update DualScreen.Android.csproj * - pin androidx versions * - fix versioning * - workaround fragment life cycle changes * - remove content from page before re-using * - fix accessibility namespaces * - bump browser and pin Navigation.UI
Description of Change
Bump to latest Android X nugets
Pinned upper bounds of Android X Nugets we've tested against
Users have hit a lot of issues (#13843) upgrading to newer androidx packages that had incompatible APIs from previous versions, so to reduce our maintenance burden we're pinning the upper bounds. We'll continue to bump these up as we release SR's
For example, the latest fragment packages completely broke shell and the new material packages completely broke material
So the range just represents a tested/verified range of packages
If you need to force to higher versions you can modify your csproj file and add them explicitly
Issues Resolved
Platforms Affected
PR Checklist