Android build fails on GetCopyToOutputDirectoryItems when the project path contains non-ASCII chars

[wokhan]

Current behavior

When a Windows user's profile name contains accented or non-ASCII chars (at least in my case with "é" and "ô"), Android build fails every time with error APT2097 (but also APT0001 sometimes if I remember correctly):

GetCopyToOutputDirectoryItems cible :
_GetCopyToOutputDirectoryItemsFromTransitiveProjectReferences cible :
C:\Testéô....\obj\Debug\100\lp\78\jl\res : error APT2097: failed to open directory: Le fichier spécifié est introuvable. (2).
Note that it might be a script or file encoding issue (on my side?), my Android csproj file is properly UTF8-encoded though.

Expected behavior

UTF8 should be supported and build should succeed.

How to reproduce it (as minimally and precisely as possible)

Create a new project in a folder containing extended ASCII chars (or UTF8 ones) with the Android workload, launch build.

Workaround

Move the project in another folder with ASCII-only path (or create a symlink from an ASCII-only path pointing to the actual one).

Environment

Nuget Package:

• Uno.UI / Uno.UI.WebAssembly / Uno.UI.Skia
• Uno.WinUI / Uno.WinUI.WebAssembly / Uno.WinUI.Skia
• Uno.SourceGenerationTasks
• Uno.UI.RemoteControl / Uno.WinUI.RemoteControl
• Other:

Nuget Package Version(s): 3.6.6 (encountered before as well - since first version in fact)

Affected platform(s):

• iOS
• Android
• WebAssembly
• WebAssembly renderers for Xamarin.Forms
• macOS
• Skia
  • WPF
  • GTK (Linux)
  • Tizen
• Windows
• Build tasks
• Solution Templates

IDE:

• Visual Studio 2017 (version: )
• Visual Studio 2019 (version: 16.9.3)
• Visual Studio for Mac (version: )
• Rider Windows (version: )
• Rider macOS (version: )
• Visual Studio Code (version: )

Relevant plugins:

• Resharper (version: )

Anything else we need to know?

I encountered this a while ago so it's not a regression, but I never saw anyone else complain about this issue... Surprising.
Thanks!

[jeromelaban]

Thanks for the report.

Does a standard xamarin.android project work with the same path ?

[wokhan]

Hi @jeromelaban, tried right now and it also fails with a brand new Xamarin Android project...

[jeromelaban]

Thanks, this means that it would be an issue to open in the https://github.com/xamarin/xamarin-android repo, as we're not manipulating the xamarin.android tooling. When fixed, Uno is going to benefit from it indirectly.

GitHub

xamarin/xamarin-android

Xamarin.Android provides open-source bindings of the Android SDK for use with .NET managed languages such as C# - xamarin/xamarin-android

[wokhan]

Hi, it makes total sense, I'll open an issue on their side; sorry I didn't try with a Xamarin project directly before :)