[AOT] Failure when the path to the temp folder contains accentuated characters and/or spaces

[jeromelaban]

Android framework version

net8.0-android

Affected platform version

8.0.11

Description

On Windows, when building with AOT enabled, and the user home folder has an accentuated character and/or a space, the build fails with:

C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\34.0.145\targets\Microsoft.Android.Sdk.Aot.targets(109,5): Precompiling failed for E:\Net2022files\WinNavUno5\WinNavUno5\obj\Release\net8.0-android\android-x64\linked\_Microsoft.Android.Resource.Designer.dll with exit code 1.
The specified response file can not be read [E:\Net2022files\WinNavUno5\WinNavUno5\WinNavUno5.csproj]

Steps to Reproduce

Build an app with AOT enabled, with a user folder with accentuated characters and/or spaces.

Did you find any workaround?

Changing the user folder path to be without spaces and accentuated characters.

Relevant log output

binlog (14).zip

[dellis1972]

@jeromelaban very odd. So the temp folder path has an accented character in it :(

@akoeplinger any idea who works on the \mono-aot-cross.exe ? Looks like an issue in that area.

[WinNavUno5.dll] Running: C:\Program Files\dotnet\packs\Microsoft.NETCore.App.Runtime.AOT.win-x64.Cross.android-x64\8.0.11\Sdk\..\tools\mono-aot-cross.exe --response="C:\Users\Werner König\AppData\Local\Temp\tmp12E0.tmp"

[jeromelaban]

It is odd indeed.

I noticed this particular behavior when accounts are created using MS Entra Online-only (Azure AD) accounts, where the tooling does not "normalize" the folder to 7-bits ASCII and uses the user's original name instead of the SAMAccount field.

My own name has an accent in it, and it's also causing all sorts of issues which I avoid by changing the folder from the get-go...

[akoeplinger]

would you mind trying with dotnet 9? there were some related fixes in that area.