-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MAUI project with non-ASCII project name cannot release to my Android phone #83203
Comments
This likely to be a tool chain problem with android publishing, I had difficulty publishing with Japanese project name when I worked with Xamarin but it worked out some how (long ago) I suggest renaming the project with the name you want instead of creating the project with the name you wanted note |
I tried reproducing on the Mac and it seems to work fine there, so it is probably a Windows-specific issue: The only thing I noticed is that the non-ASCII characters in the .apk/.aab filename were replaced with underscores but I don't know whether that is an expected behavior from the Android toolchain @dellis1972 The app on the device has the correct title and everything. |
@vargaz @lambdageek @SamMonoRT this seems relevant related to what we discussed for #82187, it seems using non-ASCII in general works with the AOT compiler at least on the Mac. |
The underscores thing is an android tool chain issue I think, its not relatd to this issue. |
@lambdageek - this is a Windows only issue, not sure about the priority for 8.0? |
@SamMonoRT It's the AOT compiler running on Windows (ie: someone is using VS on Windows to develop an Android app). It's pretty high priority |
This doesn't seem to be a regression. We do have some issues with handling of non-ascii characters in file names that easily fixable. The problem is that we need to compile some files with such characters and the compiler toolchain behind (some llvm tools) don't have support for wide chars. I'm not sure if this is intentional, will submit an issue on the llvm project to figure out if we can have a fix on their side. An alternative fix would be to rename all files so they can be processed by the toolchain, but that seems like a hack and rather risky this late in the release. Either way, seems like this issue should be left for net-9.0. |
@BrzVlad - please can you add a link to the issue created on llvm project here for tracking. Moving this to 9.0 and will validate once llvm project owners have a suggestion. |
After further investigation it seems like llvm tools work as expected. We actually have a wrapper around |
There is also a related issue upstream in the aapt2 tool https://issuetracker.google.com/issues/188679588 |
cc @ilonatommy who is investigating somewhat related WASM tooling issue |
Thanks, for us it's AOT/relink case on Windows caused by emscripten not respecting wide chars: #83497. The fix for it seems to be on its way. |
I'm expecting this to be fixed starting in .net 9 Preview 2 |
Description
Context https://i.azdo.io/1714603
When a user tries to use certain non-ascii characters for the project name AOT fails with the following error
Reproduction Steps
Expected behavior
The application should build without any errors.
Actual behavior
The following error is raised
Regression?
Not sure if this is a regression, however the same
dotnet new console -o 随机生成器
app will work correctly.Known Workarounds
The only known workaround is to only use ASCII characters for project names.
Configuration
This can be re-produced on .net 7.0.200
Other information
No response
The text was updated successfully, but these errors were encountered: