Android - APT2000 build error when maui-blazor #7639

Activity

1. skoc10

   added

   Area: App+Library BuildIssues when building Library projects or Application projects.Issues when building Library projects or Application projects.

   needs-triageIssues that need to be assigned.Issues that need to be assigned.

   on Dec 15, 2022
2. skoc10

   assigned

   dellis1972

   and

   jonathanpeppers

   on Dec 15, 2022
3. dellis1972 commented on Dec 15, 2022

   

   dellis1972

   on Dec 15, 2022

   Contributor

   More actions

   @skoc10

   As per the other bug can you add the following to your project

   <AndroidAapt2LinkExtraArgs>$(AndroidAapt2LinkExtraArgs) -v</AndroidAapt2LinkExtraArgs>
   

   then build (from clean) on the command line again and post the logs? We need the binlog file
   so you need to run

   dotnet build MyCompanyName.MyProjectName.MauiBlazor.csproj -bl
   

   This will give us more verbose aapt2 output. It should help narrow down which file is causing the error.

   On a side note, the path you have D:\ci\Jenkins\workspace\abp-commercial-nightly\volo\abp\templates\app-pro\aspnet-core\src\MyCompanyName.MyProjectName.MauiBlazor\MyCompanyName.MyProjectName.MauiBlazor.csproj might cause some issues on windows. Windows has a max command line length which you might hit when building release builds with aot.
4. dellis1972

   added

   need-infoIssues that need more information from the author.Issues that need more information from the author.

   and removed

   needs-triageIssues that need to be assigned.Issues that need to be assigned.

   on Dec 15, 2022
6. dellis1972

   added this to the Under Consideration milestone on Dec 15, 2022
7. skoc10 commented on Dec 15, 2022

   

   skoc10

   on Dec 15, 2022

   Author

   More actions

   msbuild.binlog.zip
8. ghost removed

   need-infoIssues that need more information from the author.Issues that need more information from the author.

   on Dec 15, 2022
9. ghost added

   need-attentionA xamarin-android contributor needs to reviewA xamarin-android contributor needs to review

   on Dec 15, 2022
10. dellis1972 commented on Dec 15, 2022

    

    dellis1972

    on Dec 15, 2022

    Contributor

    More actions

    @skoc10

    I'm not seeing anyting obvious in the logs. aapt2 is raising that error, but its not reporting which file it cannot find.
    I will try to repo here (not luck so far).

    Are you getting this on a maui-blazor template? If so can you zip up the entire project and attach it to this issue please?
11. dellis1972

    added

    need-infoIssues that need more information from the author.Issues that need more information from the author.

    and removed

    need-attentionA xamarin-android contributor needs to reviewA xamarin-android contributor needs to review

    on Dec 15, 2022
13. ebicoglu commented on Dec 16, 2022

    

    ebicoglu

    on Dec 16, 2022

    Last edited by ebicoglu

    More actions

    this problem is related to Windows long path. but the error message that aapt2 is rasing is not clear. developers can easily fall into this issue, so we should find a way to expose this exception.

    👍React with 👍1Reacted by selman koc
14. ghost removed

    need-infoIssues that need more information from the author.Issues that need more information from the author.

    on Dec 16, 2022
15. ghost added

    need-attentionA xamarin-android contributor needs to reviewA xamarin-android contributor needs to review

    on Dec 16, 2022
16. dellis1972 commented on Dec 16, 2022

    

    dellis1972

    on Dec 16, 2022

    Contributor

    More actions

    It might also be worth looking at some of the suggestions in https://learn.microsoft.com/en-us/xamarin/android/troubleshooting/questions/path-too-long-exception and see if they work.

    Setting a shorter BaseIntermediateOutputPath (and leaving the project where it is) might also help.
    You will need to place this in a Directory.Build.props file next to your project/solution.

    <Project>
      <PropertyGroup>
          <BaseIntermediateOutputPath Condition=" '$(OS)' == 'Windows_NT' ">C:\Intermediate\$(ProjectName)</BaseIntermediateOutputPath>
          <BaseIntermediateOutputPath Condition=" '$(OS)' != 'Windows_NT' ">/tmp/Intermediate/$(ProjectName)</BaseIntermediateOutputPath>
      </PropertyGroup>
    </Project>
    
17. skoc10 commented on Dec 16, 2022

    

    skoc10

    on Dec 16, 2022

    Last edited by skoc10

    Author

    More actions

    It might also be worth looking at some of the suggestions in https://learn.microsoft.com/en-us/xamarin/android/troubleshooting/questions/path-too-long-exception and see if they work.

    Setting a shorter BaseIntermediateOutputPath (and leaving the project where it is) might also help. You will need to place this in a Directory.Build.props file next to your project/solution.

    <Project>
      <PropertyGroup>
          <BaseIntermediateOutputPath Condition=" '$(OS)' == 'Windows_NT' ">C:\Intermediate\$(ProjectName)</BaseIntermediateOutputPath>
          <BaseIntermediateOutputPath Condition=" '$(OS)' != 'Windows_NT' ">/tmp/Intermediate/$(ProjectName)</BaseIntermediateOutputPath>
      </PropertyGroup>
    </Project>
    

    Thanks. Directory.Build.props file worked!
18. dellis1972 commented on Dec 16, 2022

    

    dellis1972

    on Dec 16, 2022

    Contributor

    More actions

    Excelent.

    While we cannot fix the error in aapt2 I did open a PR which should improve the error messaging a bit #7644.

    👍React with 👍1Reacted by selman koc
19. skoc10

    closed this as completedon Dec 16, 2022
20. ghost locked as resolved and limited conversation to collaborators on Jan 15, 2023