Fixed
Status Update
Comments
al...@google.com <al...@google.com>
ap...@google.com <ap...@google.com> #2
I had the same problem today, and this could be related to https://code.google.com/p/android/issues/detail?id=67376
As a temporary fix, I changed the build.gradle from
dependencies {
classpath 'com.android.tools.build:gradle:0.9.+'
}
to:
dependencies {
classpath 'com.android.tools.build:gradle:0.9.0'
}
As a temporary fix, I changed the build.gradle from
dependencies {
classpath 'com.android.tools.build:gradle:0.9.+'
}
to:
dependencies {
classpath 'com.android.tools.build:gradle:0.9.0'
}
pa...@126.com <pa...@126.com> #3
That seems to have worked around the problem - thank you very much.
Maybe this should be merged into 67376?
Maybe this should be merged into 67376?
Description
We should replace all of our null checks with the "official"
Objects.requireNonNull
which throws the correct exception.