.NET MAUI
A Microsoft open-source framework for building native device applications spanning mobile, tablet, and desktop.
3,410 questions
How do I fix APT206 - failed linking file resources and APT2259 'textEnd' is incompatible with attribute iconGravity errors?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(80, 80%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGB%3C/text%3E%3C/svg%3E)
Gorimar, Behzad
5
Reputation points
I have a Xamarin Forms application that I am migrating to MAUI and I am getting the following 2 errors during compilation.
APT2259 'textEnd' is incompatible with attribute iconGravity (attr) flags [start=1, textStart=2].
APT2061 failed linking file resources.
Based on a previous similar post, I have performed the recommended actions such as:
Ensure all SDKs are up-to-date, close VS 2022 and delete the bin and obj directories and rebuild but this has not worked
I'm not sure if this error is indicating a missing or not compatible Xamarin library.
The APT2259 is occurring in a file called "mtrl_calendar_month_navigation.xml" on line 33 (style="?attr/materialCalendarYearNavigationButton")
The APT2061 is occurring on line 156 in the Xamarin build tools (outside the project) C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\33.0.26\tools\Xamarin.Android.Aapt2.targets
Here is a list of packages for the project
Thank you in advance.
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(22.400000000000002, 3%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EWZ%3C/text%3E%3C/svg%3E)
Wenyan Zhang (Shanghai Wicresoft Co,.Ltd.) 30,666 Reputation points Microsoft Vendor2023-03-21T07:10:15.53+00:00 This error is thrown from the Android SDK, I'm not sure which line of code causing this error, could you determine the detailed resources? And share some code snippets?
-
Gorimar, Behzad 5 Reputation points
2023-03-21T23:40:35.5133333+00:00 Thanks Wenyan, I have updated the original question with more details. I haven't been able to reproduce this error in the small scale. When I looked for similar posts, I found one where the solution for APT2061 was to uncheck Aapt2 target in the project file but this option is not allowed for MAUI. When I disable it, i get the following error:
XA1026 Using AAPT is not supported in Xamarin.Android projects that target .NET 6 or higher. Please enable 'Use incremental Android packaging system (aapt2)' in the Visual Studio project property pages or edit the project file in a text editor and set the 'AndroidUseAapt2' MSBuild property to 'true'.
Thanks for your help.
-
Wenyan Zhang (Shanghai Wicresoft Co,.Ltd.) 30,666 Reputation points Microsoft Vendor
2023-03-22T03:06:35.2066667+00:00 I search for a related issue that points to AndroidX problem, but AndroidX is a part of MAUI currently. Does your project support AndroidX?
Besides, I'm confused about the
Xamarin.Communitytookit.MarkupandXamarin.CommunityToolkit.MauiCompatpackages, you can try to check if the error still exists after removing the packages. (There are some third-party packages in your project, you can check if they support .net-android. And I search for the NuGet packages you are using, some are for .net6, some are for .net7, you can check if they can be compiled with your project)As summarize at the announce - Introducing .NET MAUI Compatibility for the Xamarin Community Toolkit (microsoft.com), the
MauiCompatlibraries have been deprecated and they have been migrated to .NET MAUI Toolkit.For more details, you can see .NET MAUI Community Toolkit documentation - .NET Community Toolkit | Microsoft Learn
-
Gorimar, Behzad 5 Reputation points
2023-03-22T06:07:25.59+00:00 Thanks for the suggestions. I could not find any settings in the MAUI project properties that allows me to opt in/out of AndroidX. I think it is now part of MAUI.
The app has a lot of legacy Xamarin.Communitytoolkit code that is not compatible with the new .NET MAUI Toolkit.
I was getting thousands of errors using the new MAUI toolkit until I followed the instructions in the following article and the errors came down to just the 2 mentioned here.
This is the article I followed.
As for the new MAUI toolkit, it still does not have a like for like setup compared to the Xamarin toolkit.
The following is just one code example where the new MAUI toolkit does not work. The StateView in the new toolkit has changed.
using System.Diagnostics.CodeAnalysis; using Xamarin.CommunityToolkit.UI.Views; namespace Mobile.Features { public class PanelState : StateView { public static BindableProperty StateProperty = BindableProperty.Create(nameof(State), typeof(PanelViewState), typeof(PanelState), defaultValue: (PanelViewState)99); public PanelState() { StateKey = LayoutState.Custom; SetBinding(CustomStateKeyProperty, new Binding(nameof(State), stringFormat: "{0}", source: this)); } public PanelViewState State { get => (PanelViewState)GetValue(StateProperty); set => SetValue(StateProperty, value); } } } -
Wenyan Zhang (Shanghai Wicresoft Co,.Ltd.) 30,666 Reputation points Microsoft Vendor
2023-03-23T07:56:11.4533333+00:00 AndroidX can be automatic migration in Xamarin.Forms, please see AndroidX Migration in Xamarin.Forms - Xamarin | Microsoft Learn And AndroidX is a part of MAUI currently.
For the MAUI toolkit issue, you can create new issue at https://github.com/CommunityToolkit/Maui/issuesBesides, I'm not sure the 2 mentioned issues are related to MAUI toolkit or not. Can you create a new Xamarin project without Community toolkit then migrate to MAUI? And check if the error still exists?
-
Wenyan Zhang (Shanghai Wicresoft Co,.Ltd.) 30,666 Reputation points Microsoft Vendor
2023-03-24T01:47:34.41+00:00 Besides, you can try to delete the Resource.designer.cs generated file from the Android project.
-
Gorimar, Behzad 5 Reputation points
2023-03-29T22:02:19.86+00:00 You are right about the issue not being related to MAUI compat toolkit. I replaced it with the new toolkit (commenting out the stuff that doesn't work with the new toolkit) and have the same issue.
The Resource.designer.cs gets deleted when I do a clean build by manually deleting the bin and obj directories. I have tried the clean build approach many times with no luck.
-
Wenyan Zhang (Shanghai Wicresoft Co,.Ltd.) 30,666 Reputation points Microsoft Vendor
2023-03-30T04:16:32.2733333+00:00 How did you migrate your Xamarin project to MAUI? with the .NET Upgrade Assistant? And I tested an android layout with MAUI project, the style on line 33 cannot be found. You could try to remove that style or use
style="?attr/materialCalendarFullscreenTheme"to check if it works. -
Gorimar, Behzad 5 Reputation points
2023-04-03T05:39:42.53+00:00 Thank you for taking the time to test the Android layout.
After using the upgrade assistant, I followed the manual steps specified in the upgrade guide. The material theme dependency is automatically installed, and any modifications require scripting into the build pipeline. If I can't find a more straightforward solution, I may have to reconsider this recommendation.
At the moment, I've made headway by starting with a fresh solution and gradually transferring over the XAML, .cs files, and dependencies. Although this method produces errors, they are easy to understand and fix.
This approach is somewhat laborious and time-consuming. I'll keep you posted on the outcome.
-
Wenyan Zhang (Shanghai Wicresoft Co,.Ltd.) 30,666 Reputation points Microsoft Vendor
2023-04-03T09:38:51.65+00:00 OK, you could try to create an empty project and transfer the files. If you have any other issues, please feel free to post here.
Sign in to comment
Sign in to answer