AndroidX compatibility adjustments (backport #23097)

[mergify]

AndroidX.Core 1.17.0 reshaped AccessibilityNodeInfoCompat.setChecked from setChecked(boolean) to setChecked(int) (CHECKED_STATE_FALSE/TRUE/PARTIAL). The corresponding Xamarin.AndroidX binding therefore exposes Checked as an int-typed property in Xamarin.AndroidX.AppCompat >= 1.7.1.x, while the previous binding shipped a bool setter. The Uno assemblies were compiled against the older binding, so on Android the Skia canvas view threw a MissingMethodException whenever it received accessibility focus (non-crashing but silently broken).

PR Type

• Bugfix

What is the current behavior?

UnoExploreByTouchHelper.OnPopulateNodeForVirtualView writes node.Checked = bool, which no longer exists in AndroidX.Core >= 1.17.0:

System.MissingMethodException: Method not found: void AndroidX.Core.View.Accessibility.AccessibilityNodeInfoCompat.set_Checked(bool)

This reproduces whenever a consumer pulls Xamarin.AndroidX.Core >= 1.17.0 transitively (for example, via Sentry.Bindings.Android >= 6.3.0).

What is the new behavior?

This is not a one-line rename — the property name stayed Checked, but its type changed from bool to int. The fix has two parts:

1. Code change in src/Uno.UI.Runtime.Skia.Android/Accessibility/UnoExploreByTouchHelper.cs: write the new int checked-state, mapping IToggleProvider.ToggleState to CHECKED_STATE_FALSE (0), CHECKED_STATE_TRUE (1), or CHECKED_STATE_PARTIAL (2) via named local constants.

- node.Checked = peer is IToggleProvider toggleProvider && toggleProvider.ToggleState == ToggleState.On;
+ node.Checked = peer switch
+ {
+     IToggleProvider { ToggleState: ToggleState.On } => CheckedStateTrue,
+     IToggleProvider { ToggleState: ToggleState.Indeterminate } => CheckedStatePartial,
+     _ => CheckedStateFalse,
+ };

2. Dependency alignment so the binding the Uno assemblies are compiled against matches what consumers restore at runtime — without this, an app that doesn't transitively pull a newer AppCompat would hit the inverse MissingMethodException on set_Checked(int). Xamarin.AndroidX.AppCompat is now pinned to 1.7.1.2 everywhere it ships from this repo:
   • src/Directory.Build.targets for both net9.0-android and net10.0-android.
   • src/Uno.Sdk/packages.json (base and net10.0 override both 1.7.1.2).
   • build/nuget/Uno.WinUI.nuspec for both net9.0-android30.0 and net10.0-android36.0 groups.

Affects both net9.0-android and net10.0-android consumers.

Dependency cascade

Pinning AppCompat 1.7.1.2 is not a standalone change — it inherits the floor and transitive constraints of the AndroidX 1.17 release train. The following bumps are all required to keep the dependency graph internally consistent; reverting any of them re-introduces restore conflicts or a binding-vs-manifest mismatch on Android:

• minSdk / SupportedOSPlatformVersion raised to API 23. AndroidX 1.17 defaults to minSdk 23, so pinning AppCompat 1.7.1.2 commits us to that floor. Applied to:
  • src/Uno.Sdk/targets/Uno.Common.Android.targets — the default SupportedOSPlatformVersion for all Uno.Sdk Android consumers (21.0 → 23.0).
  • src/SamplesApp/SamplesApp.netcoremobile/SamplesApp.netcoremobile.csproj and src/SamplesApp/SamplesApp.Skia.netcoremobile/SamplesApp.Skia.netcoremobile.csproj — the Android branch of the multi-targeted SamplesApps (10.0 → 23.0).
  • src/SamplesApp/SamplesApp.netcoremobile/Android/AndroidManifest.xml and src/SamplesApp/SamplesApp.Skia.netcoremobile/Android/AndroidManifest.xml — android:minSdkVersion 21 → 23. The manifest is shared across both Android TFMs of each SamplesApp, and both TFMs now ship against AppCompat 1.7.1.2, so a per-TFM 23/21 split would only desync the manifest from the bound API.
• Transitive AndroidX bumps on net10.0-android to satisfy AppCompat 1.7.1.2:
  • Xamarin.AndroidX.Activity 1.10.1.x → 1.12.4.1 in src/Directory.Build.targets and src/Uno.Sdk/packages.json (commit 920057d6: fix(android): Bump AndroidX.Activity to satisfy AppCompat 1.7.1.2).
  • Xamarin.AndroidX.Lifecycle.LiveData 2.8.7.4 → 2.10.0.2 in src/Directory.Build.targets.
• Xamarin.Google.Android.Play.Core 1.10.3.18 → 1.10.3.21 on net10.0-android (in src/AddIns/Uno.UI.GooglePlay/Uno.UI.GooglePlay.netcoremobile.csproj) to remain compatible with the newer AndroidX dependency graph on net10.

API 21–22 device coverage is dropped on Android as a consequence of the AndroidX 1.17 floor. This is unavoidable once Uno targets the new binding, since AccessibilityNodeInfoCompat.setChecked(int) only ships in Core 1.17+.

PR Checklist

• Commits follow Conventional Commits.
• Added Runtime tests / UI tests / a manual test sample for the changes (not added — accessibility node population is hard to assert in runtime tests; verified manually via TalkBack against SamplesApp).
• Docs added / updated.
• Validated PR Screenshots Compare Test Run results.
• Contains NO breaking changes for consumers (the public Uno API surface is unchanged; only the AndroidX binding contract Uno targets is bumped, and the minSdk floor is raised from 21 to 23 to match the AndroidX 1.17 default).

Other information

The related issue is the MissingMethodException reported when AndroidX.Core 1.17+ is on the restore graph. After this PR, both the build-time binding and the runtime binding are aligned at AppCompat 1.7.1.2 / Core 1.17.x, and the minSdk floor matches AndroidX 1.17's default of API 23.

---

This is an automatic backport of pull request #23097 done by Mergify.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ MartinZikmund
❌ Copilot
_{You have signed the CLA already but the status is still pending? Let us recheck it.}