Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Android Studio: Where is the Compiler Error Output Window?

When I 'Run' my project in Android Studio, in the 'Messages' window, I get:

Gradle: 
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':play01:compileDebug'.
> Compilation failed; see the compiler error output for details.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

It says > Compilation failed; see the compiler error output for details. So where is the "compiler error output"? And/Or how do I run with --stacktrace option?

like image 259
ChaseTheSun Avatar asked May 19 '13 11:05

ChaseTheSun


People also ask

Where is the compiler error output?

You can display error output by click on Toggle view icon on left side of Build panel. Then you can walk through build errors and navigate to problematic parts of source code in Android Studio. Rating: 3.4/5. From 5 votes.

What is the compiler error?

Compilation error refers to a state when a compiler fails to compile a piece of computer program source code, either due to errors in the code, or, more unusually, due to errors in the compiler itself. A compilation error message often helps programmers debugging the source code.

Why am I getting a compiler error?

A compile error happens when the compiler reports something wrong with your program, and does not produce a machine-language translation. You will get compile errors. Everybody does. Don't let them bother you.


13 Answers

For Android Studio 3.1, select the icon below the Build one in the Build window.

Android Studio 3.1 raw log toggle button

By Android Studio 3.3 (possibly in 3.2.1), the icon has changed, though the location is the same:

Android Studio 3.3 raw log toggle button

The build window should open when you run a build action (e.g. from the Build menu). If you don't see it, you can try the "Build" button along the bottom of the window (also visible in the above screenshots), or through the menus View → Tool Windows → Build.

like image 77
boiledwater Avatar answered Nov 08 '22 19:11

boiledwater


This answer is outdated. For Android 3.1 Studio go to this answer

One thing you can do is deactivate the external build. To do so click on "compiler settings icon" in the "Messages Make" panel that appears when you have an error. You can also open the compiler settings by going to File -> Settings -> Compiler. (Thanx to @maxgalbu for this tip).

enter image description here

Uncheck "Use External build"

enter image description here

And you will see the errors in the console

EDIT: After returning to "internal build" again you may get some errors, you can solve them this way: Android Studio: disabling "External build" to display error output create duplicate class errors

like image 24
Jorge Fuentes González Avatar answered Nov 08 '22 18:11

Jorge Fuentes González


It's really straightforward to set up! Just go to the Compiler settings at Android Studio 2.2.3 and set the --stacktrace command:

Compiler settings to add --stacktrace command

Then run the app again

like image 31
Antonio Avatar answered Nov 08 '22 18:11

Antonio


Are you on Windows? Launch cmd, find your project folder and run "gradlew build". This should already give you more output than the IDE, you can also use --info, --stacktrace and --debug there.

like image 25
Hadi Kocabas Avatar answered Nov 08 '22 20:11

Hadi Kocabas


In my case I prefer to open the Terminal window on the bottom left, and run gradlew build --info :

enter image description here

like image 37
RominaV Avatar answered Nov 08 '22 18:11

RominaV


You can also see the error in the Build window by clicking on the toggle button.

enter image description here

like image 24
live-love Avatar answered Nov 08 '22 19:11

live-love


For Android Studio v4.0

As others have mentioned, the "Messages" window that was evidently present in AS 3.* no longer exists in 4.0 (or else it's hidden very, very well). After wasting far too much time on this, I've found another way to view those compile errors:

  1. Open your Gradle tool window. By default, it's on the right edge toward the top:

enter image description here

If you don't see it there, use View > Tool Windows > Gradle.

  1. In the Gradle window, open your app's root option and run Tasks > build > build:

enter image description here

  1. The Run tool window should open automatically, where you'll see details about the cause of the build error:

enter image description here

If it doesn't open automatically, you can access it through View > Tool Windows > Run.

Hopefully that gives you all the info you need. If not though, try:

  1. Go to File > Settings > Build, Execution, Deployment > Compiler. In the Command-line Options, add --scan.

enter image description here

Apply and OK, then try the Gradle build over again.

like image 45
kittykittybangbang Avatar answered Nov 08 '22 20:11

kittykittybangbang


In android studio 2.2.3 you can find output in the gradle console as shown below gradle console

like image 36
cahit beyaz Avatar answered Nov 08 '22 19:11

cahit beyaz


I am building on what Jorge recommended. Goto File->Settings->compiler.

Here you will see a field to add compiler options where you plug in --stacktrace

like image 40
jai Avatar answered Nov 08 '22 18:11

jai


Run

gradlew --stacktrace 

in a terminal to see the full report

for me it was

Task :app:compileDebugJavaWithJavac FAILED javacTask: source release 1.8 requires target release 1.8

so i added

 compileOptions {
    sourceCompatibility JavaVersion.VERSION_1_8
    targetCompatibility JavaVersion.VERSION_1_8
}

in app.gradle file / android and the build completed successfully

like image 42
Falah H. Abbas Avatar answered Nov 08 '22 18:11

Falah H. Abbas


Just click on the "Build" node in the Build Output

enter image description here

From some reason the "Compilation failed" node just started being automatically selected and for that the description window is very unhelpful.

like image 32
Jan Málek Avatar answered Nov 08 '22 18:11

Jan Málek


If you are in android studio 3.1, Verify if file->Project Structure -> Source compatibility is empty. it should not have 1.8 set.

then press ok, the project will sync and error will disappear.

like image 33
Logesh R Avatar answered Nov 08 '22 19:11

Logesh R


In my case i had a findViewById reference to a view i had deleted in xml

if you are running AS 3.1 and above:

  1. go to Settings > Build, Execution and Deployment > compiler
  2. add --stacktrace to the command line options, click apply and ok
  3. At the bottom of AS click on Console/Build(If you use the stable version 3.1.2 and above) expand the panel and run your app again.

you should see the full stacktrace in the expanded view and the specific error.

like image 39
Peterstev Uremgba Avatar answered Nov 08 '22 18:11

Peterstev Uremgba