Android studio broke up my build.gradle file after add a Fragment-ThrowExceptions

Exception or error:

Using Android Studio 2.0 over El Capitan like the next screenshot said:
Android Studio 2.0 on El Capitan

I found a bug that I can’t report:
After add a Fragment to my project, AS screw up my module build.gradle file. I mean, before add the fragment they file looks like this screenshot:
build.gradle dependence screenshot

but after add the Fragment AS screw it in this way:
build.gradle dependence screenshot 2

The way to reproduce it is like I’m showing in next screenshot:
enter image description here

I can fix it manually, but its so annoying doing it every single time that I add a Fragment. Is there anyway to fix it?

I’m on Mac OX with El Capitan.

How to solve:

It is a still open bug, you can monitor it’s state here

The bug is due to the comments in the dependencies section, a temporal fix could be to remove them from there. I placed the comments there for a reason too 🙂


Delete all comments in your gradle file


put your constraint-layout on the bottom, it will not scramble again (i don’t know why, but it works)

dependencies {
    compile fileTree(dir: 'libs', include: ['*.jar'])

    // support lib
    compile "$supportlib_version"

    // kotlin
    compile "org.jetbrains.kotlin:kotlin-stdlib-jre7:$kotlin_version"

    // ...

    compile ''
    testCompile 'junit:junit:4.12'


just reformat your project level gradle . It will work fine. These compile statement got dis-formatted. Just hit Enter before every “compile”
it should be like:

compile ''
compile ''
compile ''
compile ''
compile ''


Leave a Reply

Your email address will not be published. Required fields are marked *