Detected package version outside of dependency constraint: Xamarin.AndroidX.Activity.Ktx 1.10.1.3 requires Xamarin.AndroidX.Activity (>= 1.10.1.3 && < 1.10.2) but version Xamarin.AndroidX.Activity 1.11.0 was resolved.

Question

I changed my Android project´s target framework from .NET 9.0 to .NET 10.0 and then I installed all the NuGet package updates.

I can debug my Android project on my Google Pixel 8a (Android 16.0 - API 36) and I don´t get an error. But I get this warning:

Detected package version outside of dependency constraint: Xamarin.AndroidX.Activity.Ktx 1.10.1.3 requires Xamarin.AndroidX.Activity (>= 1.10.1.3 && < 1.10.2) but version Xamarin.AndroidX.Activity 1.11.0 was resolved.

In addition, after updating my NuGet packages many yellow triangles are displayed next to the packages, but no other package updates seem to be available:

Which package versions should I install to avoid the warnings?

I use Visual Studio Community 2026 Version: 18.1.0.

Answer 1

Hello @Kim Strasser ,

Don't worry. This happens pretty often with AndroidX libraries since they update frequently, and the binding packages don't always sync up right away.

If your app builds and runs fine on your Pixel 8a, you can safely keep working and wait for the next round of package updates. The warning is just letting you know about the version mismatch, but it won't necessarily break anything.

If you want to clear the warning now, you have a couple of options:

• You can downgrade Xamarin.AndroidX.Activity to version 1.10.1.3 to match what Activity.Ktx expects. Just add this to your .csproj file:

      <PackageReference Include="Xamarin. AndroidX.Activity" Version="1.10.1.3" />
  

  Then do a clean restore to make sure everything picks up the right version.
• Alternatively, check if there's a newer version of Xamarin.AndroidX.Activity.Ktx that supports Activity 1.11.0. Sometimes these updates roll out a few days apart.

Since you're on .NET 10.0 which is pretty new, some AndroidX bindings might still be catching up. When new updates do appear, try to keep the related package families aligned—so all your Activity packages (Activity, Activity.Ktx, Activity.Compose) and Lifecycle packages should ideally be on the same minor version.

If your build pipeline treats warnings as errors or you start seeing runtime issues, definitely address it. Otherwise, you can continue development and wait for the ecosystem to catch up.