Getting error says - "Entry name 'res/layout/test_toolbar.xml' collided" while creating signed apk

Question

I have updated my android studio from 3.5.x to 3.6 today and getting an error while generating signed apk for build variant showing the following message - Entry name 'res/layout/test_toolbar.xml' collided I don't have any layout named like this one in the whole project at all. I have a custom build variant named "stage" and whenever I am trying to build a signed apk, it always fails. I count find any solution yet. Please help me with this issue. Thanks

Update: The same issue can occur with these following messages too (As I found it in AS - 3.6.1 - Continues with 4.x.x sometimes). So don't worry about these kinds of unknown and not resolvable messages. So far I found two new types of messages while generating signed apk:

Entry name 'kotlin/collections/MapWithDefault.kotlin_metadata' collided
Access Denied

The result is the same. Sometimes you may need to Invalidate Cache and Restart your AS for this.

Just delete that file, and rebuild. – Eric Apr 01 '23 at 18:12 — Eric, Apr 01 '23 at 18:12

score 151 · Accepted Answer · edited Jul 23 '21 at 14:57

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:

delete projectFolder\build
delete projectFolder\debug*
delete projectFolder\release*
delete projectFolder\app\build
delete projectFolder\app\build\debug*
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:

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

score 70 · Answer 2 · edited Jul 23 '21 at 14:57

70

I deleted the previous build outputs for the build variant, including the APK file. That's what helped me

edited Jul 23 '21 at 14:57

Federico Navarrete

3,069
5
41
76

answered Feb 26 '20 at 14:05

Vladislav Vatrushkin

801
5
3

2

I tried deleting the `build` directory as a whole, still got the same issue. Can you elaborate what you did in full? – Pusparaj Feb 26 '20 at 14:22
Are you delete build directory in root of the project and app/build directory too? In my project output path of apk is changed and I simply delete previous apk file where it was located. – Vladislav Vatrushkin Feb 26 '20 at 14:55

score 54 · Answer 3 · edited Oct 27 '22 at 13:45

54

Problems encountered when upgrading to the latest Android Studio 3.6.1. Clearing the cache, clean the project, and deleting the build folder did not solve the problem.

Just delete the apk generated by the previous compilation.

edited Oct 27 '22 at 13:45

Ryan M

18,333
31
67
74

answered May 09 '20 at 05:14

Suraj Gupta

879
7
6

score 24 · Answer 4 · answered Feb 27 '20 at 12:35

24

While generating the apk, check for the destination folder, from which delete output.json and app-debug.apk from debug folder. Try building the same after this. AFAIK, it is a bug for android studio, hope they might fix this soon :)

answered Feb 27 '20 at 12:35

Ameena Shafeer

626
3
18

score 23 · Answer 5 · edited Jul 23 '21 at 14:57

23

After updating to Android Studio 4.1 I faced similar issues, for me it was "entry name 'classes.dex' collided". The error arose when building the app using the option 'Generate Signed Bundle/APK'.

The solution was simple: make sure Android Studio is not running the app when building (stop running and then try again).

edited Jul 23 '21 at 14:57

Federico Navarrete

3,069
5
41
76

answered Oct 15 '20 at 07:41

Lars

371
3
8

4

Thanks for the tips ;-) For me, it was just that the phone was connected – Ludo Nov 01 '20 at 22:02
2

This worked most of the time for me (AVD instead of phone connected) but sometimes needed an additional restart of Android Studio. – spc-mrn Jan 13 '21 at 10:34

score 14 · Answer 6 · edited Jul 23 '21 at 14:58

14

This issue is resolved by deleting APKs generated by the previous builds existing in release and debug folders.

Invalidating cache and rebuild would not help if you have not deleted previously generated APKs

edited Jul 23 '21 at 14:58

Federico Navarrete

3,069
5
41
76

answered Sep 17 '20 at 17:30

Akhilesh

196
3
5

score 12 · Answer 7 · edited Oct 27 '22 at 13:46

12

I had the same error after updating Android Studio.

I fixed the problem by only cleaning the project (Build > Clean Project)

edited Oct 27 '22 at 13:46

Ryan M

18,333
31
67
74

answered Apr 11 '20 at 18:55

Agathe Casgrain-Cyr

129
2

score 6 · Answer 8 · answered Aug 25 '20 at 10:42

6

I just delete all debug APKs in myProject\app\build\outputs\apk\debug directory and it worked for me.

answered Aug 25 '20 at 10:42

Gk Mohammad Emon

6,084
3
42
42

score 5 · Answer 9 · answered Jul 27 '20 at 15:11

5

This may have been overkill but I:

Delete project/build folder
Delete project/app/build folder
File > Invalidate Caches / Restart
Clean Project

answered Jul 27 '20 at 15:11

syntakks

121
1
6

score 3 · Answer 10 · edited Jul 23 '21 at 14:59

It happen when you used auto viewBinding, Binding using Kotlin, or viewBinding feature of 3.6.

In case, you are adding files whose elements share the same IDs, ViewBinding confuses and creates such an error.

Let me help you by example Adapter class which has two layout file separating by view Type :

import kotlinx.android.synthetic.main.frag_subscription_recommend.view.*


override fun onCreateViewHolder(parent: ViewGroup, viewType: Int): ViewHolder {
   return ViewHolder(
        LayoutInflater.from(parent.context).inflate(
            if (viewType == 1) {
                R.layout.frag_subscription_recommend
            } else
                R.layout.frag_subscription_common,
            parent,
            false
        )
    )
}

onBinding(){
  holder.itemView.id_button_submit.setOnClickListener {}
}


 // which in case confusing which resource or layout full fill the requirement bcoz both have same ids of button.

in case you have to use :

 onBinding(){
  holder.itemView.findViewById<Button>(R.id.id_button_submit).setOnClickListener {}
}

which enables the old implementation.

Let me know if this working on your side?

Sorry, but the problem was with the build, debug and release directories. including output json file. Anyways, thhanks for your reply — A S M Sayem, Mar 04 '20 at 05:35

score 3 · Answer 11 · edited Oct 27 '22 at 13:27

3

It's due to updated configuration changes in the Gradle.

So just try File -> File > Invalidate Caches / Restart

edited Oct 27 '22 at 13:27

Ryan M

18,333
31
67
74

answered Aug 04 '20 at 07:18

Codemaker2015

12,190
6
97
81

score 1 · Answer 12 · edited Jul 23 '21 at 14:59

1

Delete "ProjectFolder/build" folder of your project. Make sure you Have Closed Android Studio, otherwise you would unable to delete it.

edited Jul 23 '21 at 14:59

Federico Navarrete

3,069
5
41
76

answered May 05 '20 at 07:07

riishiiraz

31
2

score 1 · Answer 13 · answered Feb 14 '21 at 22:26

1

To do a clean via the CLI, run ./gradlew clean on the /android directory

That worked for me.

answered Feb 14 '21 at 22:26

Felix Too

11,614
5
24
25

score 1 · Answer 14 · answered Aug 08 '22 at 12:48

1

Build 
  |-----> Clean project 
  |-----> Rebuild project

This worked for me.

answered Aug 08 '22 at 12:48

AllwiN

693
2
12
26

score 0 · Answer 15 · edited Oct 27 '22 at 13:42

0

I had entry name 'classes.dex' collided

I just unplugged at the computer all four of the devices that I have been testing on.

Then the build succeeded.

edited Oct 27 '22 at 13:42

Ryan M

18,333
31
67
74

answered Feb 09 '21 at 04:29

Mick

663
1
9
18

I simply rebuilt a project and `Entry name 'classes.dex' collided` disappeared. – CoolMind Feb 15 '21 at 08:34

score 0 · Answer 16 · edited Jul 23 '21 at 15:00

0

I had the same issue. At issue' comments, I got the link to another issue, then I got a solution, which works for me.

Our project has the following lines at build.gradle(:app) specially for TeamCity

applicationVariants.all { variant ->
    variant.outputs.all {
        outputFileName = "../../" + outputFileName
    }
}

But it crashes the local build process.

So I just add condition and fix the issue!

applicationVariants.all { variant ->
    variant.outputs.all {
        if (rootProject.hasProperty("teamcity"))
            outputFileName = "../../" + outputFileName
    }
}

edited Jul 23 '21 at 15:00

Federico Navarrete

3,069
5
41
76

answered Jul 23 '21 at 14:48

GSD.Aaz

178
2
6

How this fix is working? Which string is to be used as property here? – Alexey Ozerov Aug 25 '21 at 07:01
The fix help me to build project on TeamCity, but local build stops with error. I add the condition and apply fix only if build process is running on TeamCity. – GSD.Aaz Nov 24 '21 at 15:13

Getting error says - "Entry name 'res/layout/test_toolbar.xml' collided" while creating signed apk

16 Answers16

Linked