Uno and .NET7 #10395

queequac · 2022-11-10T17:35:02Z

queequac
Nov 10, 2022

After updating to VS 17.4.0 and .NET7, my Android app does no longer compile for the release target.
Important things first: Debug builds still wor fine. On release builds I get a really long list of errors (hundreds of lines), such as the following excerpt:

1>C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\33.0.4\tools\Xamarin.Android.Common.targets(1476,3): error XA4215: The Java type `crc642579205336516b81.ListViewAdapter` is generated by more than one managed type. Please change the [Register] attribute so that the same Java type is not emitted.
1>C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\33.0.4\tools\Xamarin.Android.Common.targets(1476,3): error XA4215:   `crc642579205336516b81.ListViewAdapter` generated by: Uno.UI.Controls.Legacy.ListViewAdapter, Uno.UI, Version=255.255.255.255, Culture=neutral, PublicKeyToken=null
1>C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\33.0.4\tools\Xamarin.Android.Common.targets(1476,3): error XA4215:   `crc642579205336516b81.ListViewAdapter` generated by: Uno.UI.Controls.Legacy.ListViewAdapter, Uno.UI, Version=255.255.255.255, Culture=neutral, PublicKeyToken=null
1>C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\33.0.4\tools\Xamarin.Android.Common.targets(1476,3): error XA4215:   `crc642579205336516b81.ListViewAdapter` generated by: Uno.UI.Controls.Legacy.ListViewAdapter, Uno.UI, Version=255.255.255.255, Culture=neutral, PublicKeyToken=null
1>C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\33.0.4\tools\Xamarin.Android.Common.targets(1476,3): error XA4215: The Java type `crc642579205336516b81.ListViewFooter` is generated by more than one managed type. Please change the [Register] attribute so that the same Java type is not emitted.
1>C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\33.0.4\tools\Xamarin.Android.Common.targets(1476,3): error XA4215:   `crc642579205336516b81.ListViewFooter` generated by: Uno.UI.Controls.Legacy.ListViewFooter, Uno.UI, Version=255.255.255.255, Culture=neutral, PublicKeyToken=null
1>C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\33.0.4\tools\Xamarin.Android.Common.targets(1476,3): error XA4215:   `crc642579205336516b81.ListViewFooter` generated by: Uno.UI.Controls.Legacy.ListViewFooter, Uno.UI, Version=255.255.255.255, Culture=neutral, PublicKeyToken=null
1>C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\33.0.4\tools\Xamarin.Android.Common.targets(1476,3): error XA4215:   `crc642579205336516b81.ListViewFooter` generated by: Uno.UI.Controls.Legacy.ListViewFooter, Uno.UI, Version=255.255.255.255, Culture=neutral, PublicKeyToken=null

Any clue what's happening here?
I am using AOT without LLVM and trimming with r8.

jeromelaban · 2022-11-10T18:32:02Z

jeromelaban
Nov 10, 2022
Maintainer

This is a known issue in Xamarin.Android issue: #9513. There's no workaround at this time, unfortunately, but the .NET team is actively working on it.

The only way to build an Xamarin.ANdroid app at this point is either to disable AOT, or to use .NET 6 through a global.json file.

6 replies

queequac Nov 10, 2022
Author

And I downgraded to .NET 6 and the issue remains. So obviously something is broken on my side after upgrading to 17.4 :(

But the errros mention exclusively controls from Uno.UI.

It starts by the way with the following:

1>C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\32.0.476\tools\Xamarin.Android.Common.targets(1438,3): warning XA4214: The managed type `Microsoft.UI.Xaml.Controls.AnimatedIcon` exists in multiple assemblies: Uno.UI, Uno.UI, Uno.UI. Please refactor the managed type names in these assemblies so that they are not identical.
1>C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\32.0.476\tools\Xamarin.Android.Common.targets(1438,3): warning XA4214: References to the type `Microsoft.UI.Xaml.Controls.AnimatedIcon` will refer to `Microsoft.UI.Xaml.Controls.AnimatedIcon, Uno.UI`.
1>C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\32.0.476\tools\Xamarin.Android.Common.targets(1438,3): warning XA4214: The managed type `Microsoft.UI.Xaml.Controls.BreadcrumbBar` exists in multiple assemblies: Uno.UI, Uno.UI, Uno.UI. Please refactor the managed type names in these assemblies so that they are not identical.
1>C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\32.0.476\tools\Xamarin.Android.Common.targets(1438,3): warning XA4214: References to the type `Microsoft.UI.Xaml.Controls.BreadcrumbBar` will refer to `Microsoft.UI.Xaml.Controls.BreadcrumbBar, Uno.UI`.
1>C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\32.0.476\tools\Xamarin.Android.Common.targets(1438,3): warning XA4214: The managed type `Microsoft.UI.Xaml.Controls.BreadcrumbBarItem` exists in multiple assemblies: Uno.UI, Uno.UI, Uno.UI. Please refactor the managed type names in these assemblies so that they are not identical.
1>C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\32.0.476\tools\Xamarin.Android.Common.targets(1438,3): warning XA4214: References to the type `Microsoft.UI.Xaml.Controls.BreadcrumbBarItem` will refer to `Microsoft.UI.Xaml.Controls.BreadcrumbBarItem, Uno.UI`.
1>C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\32.0.476\tools\Xamarin.Android.Common.targets(1438,3): warning XA4214: The managed type `Microsoft.UI.Xaml.Controls.ColorPicker` exists in multiple assemblies: Uno.UI, Uno.UI, Uno.UI. Please refactor the managed type names in these assemblies so that they are not identical.
1>C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\32.0.476\tools\Xamarin.Android.Common.targets(1438,3): warning XA4214: References to the type `Microsoft.UI.Xaml.Controls.ColorPicker` will refer to `Microsoft.UI.Xaml.Controls.ColorPicker, Uno.UI`.
1>C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\32.0.476\tools\Xamarin.Android.Common.targets(1438,3): warning XA4214: The managed type `Microsoft.UI.Xaml.Controls.Expander` exists in multiple assemblies: Uno.UI, Uno.UI, Uno.UI. Please refactor the managed type names in these assemblies so that they are not identical.
1>C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\32.0.476\tools\Xamarin.Android.Common.targets(1438,3): warning XA4214: References to the type `Microsoft.UI.Xaml.Controls.Expander` will refer to `Microsoft.UI.Xaml.Controls.Expander, Uno.UI`.
1>C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\32.0.476\tools\Xamarin.Android.Common.targets(1438,3): warning XA4214: The managed type `Microsoft.UI.Xaml.Controls.ImageIcon` exists in multiple assemblies: Uno.UI, Uno.UI, Uno.UI. Please refactor the managed type names in these assemblies so that they are not identical.
1>C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\32.0.476\tools\Xamarin.Android.Common.targets(1438,3): warning XA4214: References to the type `Microsoft.UI.Xaml.Controls.ImageIcon` will refer to `Microsoft.UI.Xaml.Controls.ImageIcon, Uno.UI`.
1>C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\32.0.476\tools\Xamarin.Android.Common.targets(1438,3): warning XA4214: The managed type `Microsoft.UI.Xaml.Controls.InfoBadge` exists in multiple assemblies: Uno.UI, Uno.UI, Uno.UI. Please refactor the managed type names in these assemblies so that they are not identical.
1>C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\32.0.476\tools\Xamarin.Android.Common.targets(1438,3): warning XA4214: References to the type `Microsoft.UI.Xaml.Controls.InfoBadge` will refer to `Microsoft.UI.Xaml.Controls.InfoBadge, Uno.UI`.
1>C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\32.0.476\tools\Xamarin.Android.Common.targets(1438,3): warning XA4214: The managed type `Microsoft.UI.Xaml.Controls.InfoBar` exists in multiple assemblies: Uno.UI, Uno.UI, Uno.UI. Please refactor the managed type names in these assemblies so that they are not identical.
1>C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\32.0.476\tools\Xamarin.Android.Common.targets(1438,3): warning XA4214: References to the type `Microsoft.UI.Xaml.Controls.InfoBar` will refer to `Microsoft.UI.Xaml.Controls.InfoBar, Uno.UI`.
1>C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\32.0.476\tools\Xamarin.Android.Common.targets(1438,3): warning XA4214: The managed type `Microsoft.UI.Xaml.Controls.LayoutPanel` exists in multiple assemblies: Uno.UI, Uno.UI, Uno.UI. Please refactor the managed type names in these assemblies so that they are not identical.
1>C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\32.0.476\tools\Xamarin.Android.Common.targets(1438,3): warning XA4214: References to the type `Microsoft.UI.Xaml.Controls.LayoutPanel` will refer to `Microsoft.UI.Xaml.Controls.LayoutPanel, Uno.UI`.
1>C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\32.0.476\tools\Xamarin.Android.Common.targets(1438,3): warning XA4214: The managed type `Microsoft.UI.Xaml.Controls.NavigationView` exists in multiple assemblies: Uno.UI, Uno.UI, Uno.UI. Please refactor the managed type names in these assemblies so that they are not identical.
1>C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\32.0.476\tools\Xamarin.Android.Common.targets(1438,3): warning XA4214: References to the type `Microsoft.UI.Xaml.Controls.NavigationView` will refer to `Microsoft.UI.Xaml.Controls.NavigationView, Uno.UI`.
1>C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\32.0.476\tools\Xamarin.Android.Common.targets(1438,3): warning XA4214: The managed type `Microsoft.UI.Xaml.Controls.NavigationViewItem` exists in multiple assemblies: Uno.UI, Uno.UI, Uno.UI. Please refactor the managed type names in these assemblies so that they are not identical.
1>C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\32.0.476\tools\Xamarin.Android.Common.targets(1438,3): warning XA4214: References to the type `Microsoft.UI.Xaml.Controls.NavigationViewItem` will refer to `Microsoft.UI.Xaml.Controls.NavigationViewItem, Uno.UI`.
.....

It seems to see Uno.UI three times when building release... 🤔
The lines shown in the initial post are then the details on the generated classes.

queequac Nov 11, 2022
Author

@jeromelaban I am really not sure which issue of the ones you linked shall be the one similar to my issue.

And as I mentioned, the issue cannot be solved by turning off AOT or moving to .NET6, since it's always present in my case. Seems to be another default from the release target.
Anyway, I nailed it down to the root cause... you can see I have Uno.UI related things from source generators mentioned as duplicates exactly 3 times. I realized that I have 3 RuntimeIdentifiers (ARM, ARM64 and X86). If I don't specify identifiers expicitly, it is becoming 4 duplicates. And if I explicitly set only to exactly one identifier (e.g. android-x86), it compiles fine (AOT or not, does not matter).

I guess this is not Uno-related, since it still worked on 17.3.*, but it is quite annoying...🤔
@jonathanpeppers Anything related to VS17.4 that could lead to this behavior?

queequac Nov 12, 2022
Author

Obviously this is only related to generated Java-code... I can see the java file only once in obj folder for both, debug and release build. No clue why release builds are then seeing duplicates of these java classes for all the controls in use.

queequac Nov 12, 2022
Author

Thanks to the new rollback feature of Visual Studio I am back to 17.3.6 and everything works fine again. Hopefully this gets fixed very soon.😜

queequac Nov 13, 2022
Author

Thanks to Jonathan I finally found the related issue, which is not linked in the above reference to 17.4 issues.
dotnet/android#7473
Hopefully a .NET 7 service update is coming somehow soon.

ToddGlodek · 2022-11-11T17:02:33Z

ToddGlodek
Nov 11, 2022

I am having trouble with a cross platform library I created which prevents my project from building with net6/7. I tried to add net7 and net7.0-windows10.0.22000.0 as target frameworks - while maintaining net6.0; net6.0-windows10.0.22000.0 as well. The idea was to have 1-2 developers working on net7 compatibility while the rest of the devs kept working on 6.

I may be barking up the wrong tee - is this even allowed ??

<TargetFrameworks>net6.0; net6.0-windows10.0.18362;net7.0; net7.0-windows10.0.22000.0</TargetFrameworks>
...
<!--** NET 6 **-->
    <ItemGroup Condition="'$(TargetFramework)'=='net6.0-windows10.0.18362'">    
        <PackageReference Include="Microsoft.WindowsAppSDK" Version="1.1.2" />
        <FrameworkReference Update="Microsoft.Windows.SDK.NET.Ref" RuntimeFrameworkVersion="10.0.20348.18" />
        <FrameworkReference Update="Microsoft.Windows.SDK.NET.Ref" TargetingPackVersion="10.0.20348.18" />
  </ItemGroup>
  
  <!--** NET 7 **-->
    <ItemGroup Condition="'$(TargetFramework)'=='net7.0-windows10.0.22000.0'">
	    <PackageReference Include="Microsoft.WindowsAppSDK" Version="1.2.221109.1" />
	    <FrameworkReference Update="Microsoft.Windows.SDK.NET.Ref" RuntimeFrameworkVersion="10.0.20348.18" />
	    <FrameworkReference Update="Microsoft.Windows.SDK.NET.Ref" TargetingPackVersion="10.0.20348.18" />
    </ItemGroup>

But then I read FrameworkReference replaced with WindowsSdkPackageVersion for Windows SDK and thought adding it this way would fix it (but it didn't).

<!--** NET 6 **-->
    <PropertyGroup Condition="'$(TargetFramework)'=='net6.0-windows10.0.18362'" >
         <WindowsSdkPackageVersion>10.0.20348.18</WindowsSdkPackageVersion>
    </PropertyGroup>

    <ItemGroup Condition="'$(TargetFramework)'=='net6.0-windows10.0.18362'">    
        <PackageReference Include="Microsoft.WindowsAppSDK" Version="1.1.2" />
   </ItemGroup>
  
<!--** NET 7 **-->
    <ItemGroup Condition="'$(TargetFramework)'=='net7.0-windows10.0.22000.0'">
	    <PackageReference Include="Microsoft.WindowsAppSDK" Version="1.2.221109.1" />
    </ItemGroup>

    <PropertyGroup Condition="'$(TargetFramework)'=='net7.0-windows10.0.22000.0'" >
         <WindowsSdkPackageVersion>10.0.22000.25</WindowsSdkPackageVersion>
    </PropertyGroup>

Then because of New/Blank Control Library Produces Build Error (Duplicate 'Page' items were included build error) #8921, I also had this snippet which needed '$(TargetFramework)'!='net7.0-windows10.0.22000.0' to prevent more Duplicate 'Page' compile errors.

  <ItemGroup Condition=" '$(TargetFramework)'!='net6.0-windows10.0.18362'  And  '$(TargetFramework)'!='net7.0-windows10.0.22000.0' ">
     <Page Include="**\*.xaml" Exclude="bin\**\*.xaml;obj\**\*.xaml" />
     <Compile Update="**\*.xaml.cs">
       <DependentUpon>%(Filename)</DependentUpon>
     </Compile>
  </ItemGroup>

Anyway, can somebody point be towards the latest documentation that covers how I should be configuring a cross platform project library's CSPROJ file ? It seems like this is what cross-platform is for - but are we wasting our time doing this - should we just create a whole separate net7 branch ??

1 reply

jeromelaban Nov 14, 2022
Maintainer

Thanks. Can you provide any build errors you're getting?

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uno and .NET7 #10395

{{title}}

Replies: 2 comments 7 replies

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Uno and .NET7 #10395

queequac Nov 10, 2022

Replies: 2 comments · 7 replies

jeromelaban Nov 10, 2022 Maintainer

queequac Nov 10, 2022 Author

queequac Nov 11, 2022 Author

queequac Nov 12, 2022 Author

queequac Nov 12, 2022 Author

queequac Nov 13, 2022 Author

ToddGlodek Nov 11, 2022

jeromelaban Nov 14, 2022 Maintainer

queequac
Nov 10, 2022

Replies: 2 comments 7 replies

jeromelaban
Nov 10, 2022
Maintainer

queequac Nov 10, 2022
Author

queequac Nov 11, 2022
Author

queequac Nov 12, 2022
Author

queequac Nov 12, 2022
Author

queequac Nov 13, 2022
Author

ToddGlodek
Nov 11, 2022

jeromelaban Nov 14, 2022
Maintainer