build(Android): Re-enabled AAPT2 as xamarin has fixed LogicalName val…#3514
build(Android): Re-enabled AAPT2 as xamarin has fixed LogicalName val…#3514jeromelaban merged 1 commit intomasterfrom
Conversation
|
The build 17087 found UI Test snapshots differences.
|
|
The build 17087 found UI Test snapshots differences.
|
|
The build 17087 found UI Test snapshots differences.
|
|
The build 17087 found UI Test snapshots differences.
|
| <AndroidResgenFile>Resources\Resource.Designer.cs</AndroidResgenFile> | ||
| <!-- AndroidUseAapt2 is disabled until https://github.com/unoplatform/uno/issues/1382 is resolved --> | ||
| <AndroidUseAapt2>false</AndroidUseAapt2> | ||
| <!-- AndroidUseAapt2 re-enabled since https://github.com/xamarin/xamarin-android/pull/3327 got resolved --> |
There was a problem hiding this comment.
No need to keep this comment now.
| <AndroidResgenFile>Resources\Resource.Designer.cs</AndroidResgenFile> | ||
| <!-- AndroidUseAapt2 is disabled until https://github.com/unoplatform/uno/issues/1382 is resolved --> | ||
| <AndroidUseAapt2>false</AndroidUseAapt2> | ||
| <!-- AndroidUseAapt2 re-enabled since https://github.com/xamarin/xamarin-android/pull/3327 got resolved --> |
…idation for resource files
f4bdf94 to
d50a31b
Compare
|
The build 17128 found UI Test snapshots differences.
|
|
The build 17128 found UI Test snapshots differences.
|
…idation for resource files
GitHub Issue (If applicable): closes #1382
PR Type
What kind of change does this PR introduce?
What is the current behavior?
AAPT2 is disabled as it used to cause build issues when file names are invalid.
What is the new behavior?
Re-enabled AAPT2 for android. Building will now check resource files' LogicalName.
Note: This means a file with "content" build action with an invalid name will still fail the build.
PR Checklist
Please check if your PR fulfills the following requirements:
Screenshots Compare Test Runresults.Other information
Internal Issue (If applicable):