-
Notifications
You must be signed in to change notification settings - Fork 564
MAUI project with non-ASCII project name cannot release to my Android phone #7710
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
Conversation
43c1333 to
fd4faf5
Compare
fa74273 to
519d497
Compare
151a91d to
0ee0602
Compare
a98eac2 to
1dcffb3
Compare
src/Xamarin.Android.Build.Tasks/Tests/Xamarin.Android.Build.Tests/AotTests.cs
Outdated
Show resolved
Hide resolved
c43c162 to
e2396eb
Compare
8b1f657 to
b5d6f8f
Compare
7d898d2 to
e3cacb1
Compare
a5ec2f1 to
0b53dc8
Compare
5aaff27 to
f1c8765
Compare
def258c to
105ea01
Compare
d734f2c to
8645de7
Compare
8645de7 to
06b658f
Compare
jonathanpeppers
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The overall code changes look good. 👍
14b6082 to
97caad8
Compare
… phone Context https://i.azdo.io/1714603 Context https://issuetracker.google.com/issues/188679588 There is a known issue with `aapt2`, `AndroidAsset` and non-ASCII paths/project names. `aapt2` has a bug where it cannot correctly traverse a directory which contains non-ASCII characters. We curently have no way to work around this issue. So the PR adds some more detail to the specific error message which `aapt2` raises in these cases. It suggests the user check their paths to make sure it does not contain non-ASCII characters. We also add some unit tests to cover this senario.
08a8a26 to
5c1347f
Compare
| proj.SetAndroidSupportedAbis ("armeabi-v7a", "arm64-v8a", "x86", "x86_64"); | ||
| using (var builder = CreateApkBuilder (Path.Combine (rootPath, proj.ProjectName))){ | ||
| builder.ThrowOnBuildFailure = false; | ||
| Assert.AreEqual (expectedResult, builder.Build (proj), "Build should have succeeded."); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this also verify the build error?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
* main: LEGO: Merge pull request 8343 [ci] Run more MSBuild tests on Linux (dotnet#8335) [Xamarin.Android.Build.Tasks] Improve aapt2 error messages for paths (dotnet#7710)
* main: Localized file check-in by OneLocBuild Task (dotnet#8350) [ci] Install signing plugin after building (dotnet#8346) Bump to dotnet/installer@e1fd7d9649 8.0.100-rc.2.23468.1 (dotnet#8330) Localized file check-in by OneLocBuild Task (dotnet#8341) LEGO: Merge pull request 8344 LEGO: Merge pull request 8343 [ci] Run more MSBuild tests on Linux (dotnet#8335) [Xamarin.Android.Build.Tasks] Improve aapt2 error messages for paths (dotnet#7710) Bump to dotnet/installer@a6b9030047 8.0.100-rc.2.23462.1 (dotnet#8327) Bump to dotnet/installer@476310d94a 8.0.100-rc.2.23456.6 (dotnet#8325)
Context https://i.azdo.io/1714603
Context https://issuetracker.google.com/issues/188679588
There is a known issue with
aapt2,AndroidAssetand non-ASCII paths/project names.aapt2has a bug where it cannot correctly traverse a directory which contains non-ASCIIcharacters. We curently have no way to work around this issue.
So the PR adds some more detail to the specific error message which
aapt2raises inthese cases. It suggests the user check their paths to make sure it does not contain
non-ASCII characters.
We also add some unit tests to cover this senario.