Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
2018.1.0a5
2018.1.0a6
Issue ID
973706
Regression
Yes
[Android] Having android:icon="@drawable/app_icon" AndroidManifest.xml causes building to fail
If one uses AndroidManifest.xml file in the project, which was created with older version (2017.3 and below) and has "android:icon="@drawable/app_icon" in it, building the project fails. It fails as it doesn't find where to look for icon because new icons system was introduced in 2018.1.0a5.
To reproduce:
1. Open attached project
2. Build
Expected result: The project builds successfully, or the error should clearly indicate what's wrong and how to fix it.
Actual result: Building player failed with errors
error: "CommandInvokationFailure: Failed to re-package resources.
D:\Android\Sdk\build-tools\27.0.1\aapt.exe package --auto-add-overlay -v -f -m -J "gen" -M "AndroidManifest.xml" -S "res" -I "D:/Android/Sdk\platforms\android-27\android.jar" -F bin/resources.ap_ "
Note: Deleting the android:icon="@drawable/app_icon" part from AndroidManifest.xml makes it to build correctly.
Note: In best case, this part should just upgrade when upgrading the project to a version which uses the new icons system. Otherwise, the error should be at least informative.
Reproduced on: 2018.1.0a5, 2018.1.0a6,
Does not reproduce on: 2017.3.0f1, 2018.1.0a4
Comments (2)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Scene View doesn't select the Canvas when it's clicked with the View Tool
- Transform fields are impossible to edit when Inspector window is resized
- Actions in UI Builder Preview mode are not fully reset after exiting the Preview mode
- Transform field values are no longer visible when Inspector window is resized
- [Android] "Adding null Transform to TransformAccessArray will result in degraded performance" warnings printed when loading and unloading scenes with 2D animated characters
GameJob2017
Jun 18, 2018 15:18
Correction from my last statement : I have just seen this issue in Unity 2017.3.1f1 (and NOT Unity 2017.3.0f1).
GameJob2017
Jun 18, 2018 14:48
I have just seen this issue in Unity 2017.3.0f, which is the latest version of Unity 2017 as of June 18, 2018. Would anyone please take a look and fix it for Unity 2017 ?
Thanks.