Getting error says – “Entry name ‘res/layout/test_toolbar.xml’ collided” while creating signed apk

by

Before reading the solution below, please read my update from 01.04.2020, the problem is deeper and it is in your code.

I’ve got the same problem after this 3.6 update.

The fast solution is:

  1. delete projectFolder\build
  2. delete projectFolder\debug*
  3. delete projectFolder\release*
  4. delete projectFolder\app\build
  5. delete projectFolder\app\build\debug*
  6. delete projectFolder\app\build\release*

So you need to delete all of the builds, debug and release directories.

Note that you may be not able to delete whole debug and release directories, but you can delete all of its contents.

UPDATE:

I think they have fixed this bug today:
enter image description here

UPDATE 03.03.2020:
Unfortunately, the bug doesn’t fix.

UPDATE 01.04.2020:
(Not 1st April joke:) )

Since month I worked with Android Studio developers and today I was told to use JDK instead of using JRE, because one of deep errors in logs said It.

After setting JDK (File->Project Structure->SDK Location->JDK Location) instead of JRE, I’ve got some other errors that were not shown in “build output” so I run Analyze -> Inspect Code and got EIGHTEEN errors such as referring to wrong view id in layouts, errors with orientation (hi to tools:ignore="MissingDefaultResource") and errors in manifest also with orientation: I read that this is some new update in 3.6.1 – about landscape or portrait screenOrientation, fixed fast by Studio with this:
<activity tools:ignore="LockedOrientationActivity" />

When all of the errors were fixed with Analyze -> Inspect Code, I have successfully generated a signed APK using JDK and then using JRE (just for test).

So in summary, this bug caused because of deep errors which you can find out only with Inspect Code tool.

I think AS will not think that this is a bug, I think they will say that this is a new feature for improving your code.
Also, I think you should try to inspect your code even without setting JDK instead of JRE.

Additional recommendation from AS support:

BTW when exporting a release build, we also run lintVital which does some extra checks and has some errors marked as fatal. This check is expensive so it does not happen in debug builds

More Related Contents:

  1. How to debug why a Gradle build failed?
  2. Building and running app via Gradle and Android Studio is slower than via Eclipse
  3. Android Studio gradle takes too long to build
  4. Gradle: Execution failed for task ‘:processDebugManifest’
  5. Adding local .aar files to Gradle build using “flatDirs” is not working
  6. android studio 0.4.2: Gradle project sync failed error
  7. Why are there two build.gradle files in an Android Studio project?
  8. Execution failed for task ‘:app:compileDebugAidl’: aidl is missing
  9. Gradle error: Minimum supported Gradle version is 3.3. Current version is 3.2
  10. libpng error: Not a PNG file Error Showing In Android Studio
  11. Android Studio Gradle issue upgrading to version 0.5.0 – Gradle Migrating From 0.8 to 0.9 – Also Android Studio upgrade to 0.8.1
  12. Gradle and Multi-Project structure
  13. Could not find com.android.tools.build:gradle:4.0.1 ( or any version )
  14. DELETE_FAILED_INTERNAL_ERROR Error while Installing APK
  15. How to include a library module dependency in an Android Studio project?
  16. build.gradle and project libs
  17. Android Studio – Error:Program type already present
  18. Difference between build.gradle (Project) and build.gradle (Module)
  19. Android studio 3.2.1 ArtifactResolveException: Could not resolve all artifacts for configuration ‘:classpath’
  20. Error:Execution failed for task ‘:ProjectName:mergeDebugResources’. > Crunching Cruncher *some file* failed, see logs
  21. Allow insecure protocols, android gradle
  22. How to replace a string for a buildvariant with gradle in android studio?
  23. Android Studio: Re-download dependencies and sync project
  24. Gradle failed to sync with ‘unable to find optional library’
  25. Could not find property ‘outputFile’ on com.android.build.gradle.internal.api.ApplicationVariantImpl
  26. Build variants in Gradle for a Library Project in Android
  27. Android build gradle is too slow (Dependency Resolution)
  28. commons-logging defines classes that conflict with classes now provided by Android after Android Studio Update
  29. Android Studio could not find any version that matches com.android.support:appcompat-v7:+
  30. How to test android apps in a real device with Android Studio?

Leave a Comment