Namespace conflicts since updating to 25.3.0.4

Avatar
barrysohl
Created

Since updating to Rider 25.3.0.4, we are unable to build on Android. There are dozens of errors for package namespace conflicts for nugets we have been using for a long time (see below). There were no such errors prior to 25.3.0.4. Is this a known issue? Any ideas for a workaround? Any advice would be greatly appreciated! We are dead in the water on Android right now.

Warning: Namespace 'com.foo.bar' is used in multiple modules and/or libraries: AndroidManifest.xml, AndroidManifest.xml. Please ensure that all modules and libraries have a unique namespace. For more information, See https://developer.android.com/studio/build/configure-app-module#set-namespace
 

Votes

0

Share

1 comment
Avatar
Anna Morozyuk
Created

Hello barrysohl .

The new Xamarin.Android 16.0.x tooling (shipped with .NET 10.0.1 and Rider 2025.3.0.4) has stricter AndroidManifest merger validation. It now fails when multiple AAR libraries have duplicate namespace declarations, which is the case with Firebase and Google Play Services NuGet packages.
Immediate Solution:
Add this property to your .csproj file to convert the namespace errors to warnings:
 

<PropertyGroup>
  <AndroidManifestMergerExtraArgs>--warn-only</AndroidManifestMergerExtraArgs>
</PropertyGroup>

This is a known regression in Xamarin.Android 16.0.x. The root cause is that Google’s AAR libraries wrapped in NuGet packages haven’t been updated with unique namespaces required by the new manifest merger.
Alternative: If the workaround doesn’t work, temporarily reverting to .NET 9.0.x SDK would allow you to build until Microsoft releases a fix.

Hope that helps. 

 

0

Please sign in to leave a comment.