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?
gradle

add a comment |
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?
gradle

1
I run Android Studio 1.3.2 and none of the solutions work.
– Milan Babuškov
Jan 31 '16 at 12:00
3
sucki android studio demands such silly questions to be upvoted.. :)
– Siddharth
Apr 4 '18 at 6:55
maybe it's the idea of IDEA to hide errors ideally (SCNR)
– bebbo
Nov 18 '18 at 11:37
I have also same issue when i update plugin . I use Android Studio 3.4 Canary 6
– Saurabh Gaddelpalliwar
Dec 5 '18 at 12:53
add a comment |
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?
gradle

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?
gradle

gradle

edited Dec 16 '14 at 5:22


Pang
6,8611563101
6,8611563101
asked May 19 '13 at 11:05
ChaseTheSun
1,46921315
1,46921315
1
I run Android Studio 1.3.2 and none of the solutions work.
– Milan Babuškov
Jan 31 '16 at 12:00
3
sucki android studio demands such silly questions to be upvoted.. :)
– Siddharth
Apr 4 '18 at 6:55
maybe it's the idea of IDEA to hide errors ideally (SCNR)
– bebbo
Nov 18 '18 at 11:37
I have also same issue when i update plugin . I use Android Studio 3.4 Canary 6
– Saurabh Gaddelpalliwar
Dec 5 '18 at 12:53
add a comment |
1
I run Android Studio 1.3.2 and none of the solutions work.
– Milan Babuškov
Jan 31 '16 at 12:00
3
sucki android studio demands such silly questions to be upvoted.. :)
– Siddharth
Apr 4 '18 at 6:55
maybe it's the idea of IDEA to hide errors ideally (SCNR)
– bebbo
Nov 18 '18 at 11:37
I have also same issue when i update plugin . I use Android Studio 3.4 Canary 6
– Saurabh Gaddelpalliwar
Dec 5 '18 at 12:53
1
1
I run Android Studio 1.3.2 and none of the solutions work.
– Milan Babuškov
Jan 31 '16 at 12:00
I run Android Studio 1.3.2 and none of the solutions work.
– Milan Babuškov
Jan 31 '16 at 12:00
3
3
sucki android studio demands such silly questions to be upvoted.. :)
– Siddharth
Apr 4 '18 at 6:55
sucki android studio demands such silly questions to be upvoted.. :)
– Siddharth
Apr 4 '18 at 6:55
maybe it's the idea of IDEA to hide errors ideally (SCNR)
– bebbo
Nov 18 '18 at 11:37
maybe it's the idea of IDEA to hide errors ideally (SCNR)
– bebbo
Nov 18 '18 at 11:37
I have also same issue when i update plugin . I use Android Studio 3.4 Canary 6
– Saurabh Gaddelpalliwar
Dec 5 '18 at 12:53
I have also same issue when i update plugin . I use Android Studio 3.4 Canary 6
– Saurabh Gaddelpalliwar
Dec 5 '18 at 12:53
add a comment |
12 Answers
12
active
oldest
votes
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).
Uncheck "Use External build"
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
Unchecking "Use External Build" introduces two errors when I try to build my project:error: duplicate class: com.moberg.colorgame.BuildConfig
anderror: duplicate class: com.moberg.colorgame.R
– Moberg
Jun 14 '13 at 10:09
3
@Moberg Same problem here, I started a new question: stackoverflow.com/questions/17108393/…
– Waza_Be
Jun 14 '13 at 12:30
Ok, I'm going to see what happens and reply in the new question if I find something.
– Jorge Fuentes González
Jun 14 '13 at 21:11
6
I don't have that "messages make" panel... wtf?
– maxgalbu
Jun 20 '13 at 16:52
9
I do not see these options now. I am running Android Studio 1.2.1.1
– Andrew S
May 29 '15 at 6:27
|
show 3 more comments
For Android Studio 3.1, select the icon below the Build one in the Build window.
7
What Icon is that, I can't seem to find it, nor can I find a build window
– Jacob
Mar 15 '18 at 4:45
1
Why would they put this option here? thanks!!!
– jeff
Jun 21 '18 at 17:36
5
It's sad that I had to google and dig through stackoverflow to find out how to see the compiler output. Thank you @boiledwater
– spartygw
Jul 30 '18 at 13:21
2
Yo. The image link is broken. Please update it.
– shikhar bansal
Aug 7 '18 at 19:38
3
Android's IDE simply says "toggle view".. toggle view of what ? +1 for this answer. Google still doing their best to obscure workflow for developers
– giulio
Sep 13 '18 at 2:26
|
show 4 more comments
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.
9
beautiful! Now if only that output could be integrated into the Android Studio
– ChaseTheSun
May 19 '13 at 12:02
4
My thoughts exactly. An IDE without a window for compiler errors? I bet we are missing something, but this workaround should be enough until that's addressed.
– Hadi Kocabas
May 19 '13 at 13:09
4
"Are you on windows?" - This also works under Ubuntu Linux too! Thanks!/[folder-where-you-installed-the-android-studio]/sdk/tools/templates/gradle/wrapper/gradlew build
– geekQ
Jul 15 '13 at 12:37
I'm in the process of migrating a huge project from Eclipse to Android Studio. Best advise so far: get the command line gradle build working first, then worry about the new IDE.
– Jerry Brady
Oct 21 '13 at 20:19
add a comment |
It's really straightforward! Just go to the Compiler settings at Android Studio 2.2.3 and set the --stacktrace
command:
Then run the app again
add a comment |
In my case I prefer to open the Terminal window on the bottom left, and run gradlew build --info
:
1
bash: gradlew: command not found
– Occam's Razor
Jun 6 '16 at 13:54
4
@Pamblam Use ./gradlew
– Rhys
Aug 31 '16 at 17:25
add a comment |
You can also see the error in the Build window by clicking on the toggle button.
you the real hero bro
– Petro
Nov 14 '18 at 1:14
add a comment |
In android studio 2.2.3 you can find output in the gradle console as shown below
Exactly what I needed
– Андрій Ковальчук
May 4 '17 at 13:06
add a comment |
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
add a comment |
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:
- go to Settings > Build, Execution and Deployment > compiler
- add --stacktrace to the command line options, click apply and ok
- 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.
add a comment |
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.
add a comment |
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
add a comment |
need to add this in your build.gradle file
dependencies {
compile fileTree(dir: 'libs', include: '*.jar')
}
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f16633956%2fandroid-studio-where-is-the-compiler-error-output-window%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
12 Answers
12
active
oldest
votes
12 Answers
12
active
oldest
votes
active
oldest
votes
active
oldest
votes
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).
Uncheck "Use External build"
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
Unchecking "Use External Build" introduces two errors when I try to build my project:error: duplicate class: com.moberg.colorgame.BuildConfig
anderror: duplicate class: com.moberg.colorgame.R
– Moberg
Jun 14 '13 at 10:09
3
@Moberg Same problem here, I started a new question: stackoverflow.com/questions/17108393/…
– Waza_Be
Jun 14 '13 at 12:30
Ok, I'm going to see what happens and reply in the new question if I find something.
– Jorge Fuentes González
Jun 14 '13 at 21:11
6
I don't have that "messages make" panel... wtf?
– maxgalbu
Jun 20 '13 at 16:52
9
I do not see these options now. I am running Android Studio 1.2.1.1
– Andrew S
May 29 '15 at 6:27
|
show 3 more comments
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).
Uncheck "Use External build"
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
Unchecking "Use External Build" introduces two errors when I try to build my project:error: duplicate class: com.moberg.colorgame.BuildConfig
anderror: duplicate class: com.moberg.colorgame.R
– Moberg
Jun 14 '13 at 10:09
3
@Moberg Same problem here, I started a new question: stackoverflow.com/questions/17108393/…
– Waza_Be
Jun 14 '13 at 12:30
Ok, I'm going to see what happens and reply in the new question if I find something.
– Jorge Fuentes González
Jun 14 '13 at 21:11
6
I don't have that "messages make" panel... wtf?
– maxgalbu
Jun 20 '13 at 16:52
9
I do not see these options now. I am running Android Studio 1.2.1.1
– Andrew S
May 29 '15 at 6:27
|
show 3 more comments
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).
Uncheck "Use External build"
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
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).
Uncheck "Use External build"
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
edited Jul 27 '18 at 9:28
answered Jun 1 '13 at 20:32


Jorge Fuentes González
6,98322850
6,98322850
Unchecking "Use External Build" introduces two errors when I try to build my project:error: duplicate class: com.moberg.colorgame.BuildConfig
anderror: duplicate class: com.moberg.colorgame.R
– Moberg
Jun 14 '13 at 10:09
3
@Moberg Same problem here, I started a new question: stackoverflow.com/questions/17108393/…
– Waza_Be
Jun 14 '13 at 12:30
Ok, I'm going to see what happens and reply in the new question if I find something.
– Jorge Fuentes González
Jun 14 '13 at 21:11
6
I don't have that "messages make" panel... wtf?
– maxgalbu
Jun 20 '13 at 16:52
9
I do not see these options now. I am running Android Studio 1.2.1.1
– Andrew S
May 29 '15 at 6:27
|
show 3 more comments
Unchecking "Use External Build" introduces two errors when I try to build my project:error: duplicate class: com.moberg.colorgame.BuildConfig
anderror: duplicate class: com.moberg.colorgame.R
– Moberg
Jun 14 '13 at 10:09
3
@Moberg Same problem here, I started a new question: stackoverflow.com/questions/17108393/…
– Waza_Be
Jun 14 '13 at 12:30
Ok, I'm going to see what happens and reply in the new question if I find something.
– Jorge Fuentes González
Jun 14 '13 at 21:11
6
I don't have that "messages make" panel... wtf?
– maxgalbu
Jun 20 '13 at 16:52
9
I do not see these options now. I am running Android Studio 1.2.1.1
– Andrew S
May 29 '15 at 6:27
Unchecking "Use External Build" introduces two errors when I try to build my project:
error: duplicate class: com.moberg.colorgame.BuildConfig
and error: duplicate class: com.moberg.colorgame.R
– Moberg
Jun 14 '13 at 10:09
Unchecking "Use External Build" introduces two errors when I try to build my project:
error: duplicate class: com.moberg.colorgame.BuildConfig
and error: duplicate class: com.moberg.colorgame.R
– Moberg
Jun 14 '13 at 10:09
3
3
@Moberg Same problem here, I started a new question: stackoverflow.com/questions/17108393/…
– Waza_Be
Jun 14 '13 at 12:30
@Moberg Same problem here, I started a new question: stackoverflow.com/questions/17108393/…
– Waza_Be
Jun 14 '13 at 12:30
Ok, I'm going to see what happens and reply in the new question if I find something.
– Jorge Fuentes González
Jun 14 '13 at 21:11
Ok, I'm going to see what happens and reply in the new question if I find something.
– Jorge Fuentes González
Jun 14 '13 at 21:11
6
6
I don't have that "messages make" panel... wtf?
– maxgalbu
Jun 20 '13 at 16:52
I don't have that "messages make" panel... wtf?
– maxgalbu
Jun 20 '13 at 16:52
9
9
I do not see these options now. I am running Android Studio 1.2.1.1
– Andrew S
May 29 '15 at 6:27
I do not see these options now. I am running Android Studio 1.2.1.1
– Andrew S
May 29 '15 at 6:27
|
show 3 more comments
For Android Studio 3.1, select the icon below the Build one in the Build window.
7
What Icon is that, I can't seem to find it, nor can I find a build window
– Jacob
Mar 15 '18 at 4:45
1
Why would they put this option here? thanks!!!
– jeff
Jun 21 '18 at 17:36
5
It's sad that I had to google and dig through stackoverflow to find out how to see the compiler output. Thank you @boiledwater
– spartygw
Jul 30 '18 at 13:21
2
Yo. The image link is broken. Please update it.
– shikhar bansal
Aug 7 '18 at 19:38
3
Android's IDE simply says "toggle view".. toggle view of what ? +1 for this answer. Google still doing their best to obscure workflow for developers
– giulio
Sep 13 '18 at 2:26
|
show 4 more comments
For Android Studio 3.1, select the icon below the Build one in the Build window.
7
What Icon is that, I can't seem to find it, nor can I find a build window
– Jacob
Mar 15 '18 at 4:45
1
Why would they put this option here? thanks!!!
– jeff
Jun 21 '18 at 17:36
5
It's sad that I had to google and dig through stackoverflow to find out how to see the compiler output. Thank you @boiledwater
– spartygw
Jul 30 '18 at 13:21
2
Yo. The image link is broken. Please update it.
– shikhar bansal
Aug 7 '18 at 19:38
3
Android's IDE simply says "toggle view".. toggle view of what ? +1 for this answer. Google still doing their best to obscure workflow for developers
– giulio
Sep 13 '18 at 2:26
|
show 4 more comments
For Android Studio 3.1, select the icon below the Build one in the Build window.
For Android Studio 3.1, select the icon below the Build one in the Build window.
edited Dec 6 '18 at 12:40


Adinia
3,53953152
3,53953152
answered Dec 28 '17 at 10:04
boiledwater
7,30532435
7,30532435
7
What Icon is that, I can't seem to find it, nor can I find a build window
– Jacob
Mar 15 '18 at 4:45
1
Why would they put this option here? thanks!!!
– jeff
Jun 21 '18 at 17:36
5
It's sad that I had to google and dig through stackoverflow to find out how to see the compiler output. Thank you @boiledwater
– spartygw
Jul 30 '18 at 13:21
2
Yo. The image link is broken. Please update it.
– shikhar bansal
Aug 7 '18 at 19:38
3
Android's IDE simply says "toggle view".. toggle view of what ? +1 for this answer. Google still doing their best to obscure workflow for developers
– giulio
Sep 13 '18 at 2:26
|
show 4 more comments
7
What Icon is that, I can't seem to find it, nor can I find a build window
– Jacob
Mar 15 '18 at 4:45
1
Why would they put this option here? thanks!!!
– jeff
Jun 21 '18 at 17:36
5
It's sad that I had to google and dig through stackoverflow to find out how to see the compiler output. Thank you @boiledwater
– spartygw
Jul 30 '18 at 13:21
2
Yo. The image link is broken. Please update it.
– shikhar bansal
Aug 7 '18 at 19:38
3
Android's IDE simply says "toggle view".. toggle view of what ? +1 for this answer. Google still doing their best to obscure workflow for developers
– giulio
Sep 13 '18 at 2:26
7
7
What Icon is that, I can't seem to find it, nor can I find a build window
– Jacob
Mar 15 '18 at 4:45
What Icon is that, I can't seem to find it, nor can I find a build window
– Jacob
Mar 15 '18 at 4:45
1
1
Why would they put this option here? thanks!!!
– jeff
Jun 21 '18 at 17:36
Why would they put this option here? thanks!!!
– jeff
Jun 21 '18 at 17:36
5
5
It's sad that I had to google and dig through stackoverflow to find out how to see the compiler output. Thank you @boiledwater
– spartygw
Jul 30 '18 at 13:21
It's sad that I had to google and dig through stackoverflow to find out how to see the compiler output. Thank you @boiledwater
– spartygw
Jul 30 '18 at 13:21
2
2
Yo. The image link is broken. Please update it.
– shikhar bansal
Aug 7 '18 at 19:38
Yo. The image link is broken. Please update it.
– shikhar bansal
Aug 7 '18 at 19:38
3
3
Android's IDE simply says "toggle view".. toggle view of what ? +1 for this answer. Google still doing their best to obscure workflow for developers
– giulio
Sep 13 '18 at 2:26
Android's IDE simply says "toggle view".. toggle view of what ? +1 for this answer. Google still doing their best to obscure workflow for developers
– giulio
Sep 13 '18 at 2:26
|
show 4 more comments
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.
9
beautiful! Now if only that output could be integrated into the Android Studio
– ChaseTheSun
May 19 '13 at 12:02
4
My thoughts exactly. An IDE without a window for compiler errors? I bet we are missing something, but this workaround should be enough until that's addressed.
– Hadi Kocabas
May 19 '13 at 13:09
4
"Are you on windows?" - This also works under Ubuntu Linux too! Thanks!/[folder-where-you-installed-the-android-studio]/sdk/tools/templates/gradle/wrapper/gradlew build
– geekQ
Jul 15 '13 at 12:37
I'm in the process of migrating a huge project from Eclipse to Android Studio. Best advise so far: get the command line gradle build working first, then worry about the new IDE.
– Jerry Brady
Oct 21 '13 at 20:19
add a comment |
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.
9
beautiful! Now if only that output could be integrated into the Android Studio
– ChaseTheSun
May 19 '13 at 12:02
4
My thoughts exactly. An IDE without a window for compiler errors? I bet we are missing something, but this workaround should be enough until that's addressed.
– Hadi Kocabas
May 19 '13 at 13:09
4
"Are you on windows?" - This also works under Ubuntu Linux too! Thanks!/[folder-where-you-installed-the-android-studio]/sdk/tools/templates/gradle/wrapper/gradlew build
– geekQ
Jul 15 '13 at 12:37
I'm in the process of migrating a huge project from Eclipse to Android Studio. Best advise so far: get the command line gradle build working first, then worry about the new IDE.
– Jerry Brady
Oct 21 '13 at 20:19
add a comment |
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.
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.
answered May 19 '13 at 11:46
Hadi Kocabas
41934
41934
9
beautiful! Now if only that output could be integrated into the Android Studio
– ChaseTheSun
May 19 '13 at 12:02
4
My thoughts exactly. An IDE without a window for compiler errors? I bet we are missing something, but this workaround should be enough until that's addressed.
– Hadi Kocabas
May 19 '13 at 13:09
4
"Are you on windows?" - This also works under Ubuntu Linux too! Thanks!/[folder-where-you-installed-the-android-studio]/sdk/tools/templates/gradle/wrapper/gradlew build
– geekQ
Jul 15 '13 at 12:37
I'm in the process of migrating a huge project from Eclipse to Android Studio. Best advise so far: get the command line gradle build working first, then worry about the new IDE.
– Jerry Brady
Oct 21 '13 at 20:19
add a comment |
9
beautiful! Now if only that output could be integrated into the Android Studio
– ChaseTheSun
May 19 '13 at 12:02
4
My thoughts exactly. An IDE without a window for compiler errors? I bet we are missing something, but this workaround should be enough until that's addressed.
– Hadi Kocabas
May 19 '13 at 13:09
4
"Are you on windows?" - This also works under Ubuntu Linux too! Thanks!/[folder-where-you-installed-the-android-studio]/sdk/tools/templates/gradle/wrapper/gradlew build
– geekQ
Jul 15 '13 at 12:37
I'm in the process of migrating a huge project from Eclipse to Android Studio. Best advise so far: get the command line gradle build working first, then worry about the new IDE.
– Jerry Brady
Oct 21 '13 at 20:19
9
9
beautiful! Now if only that output could be integrated into the Android Studio
– ChaseTheSun
May 19 '13 at 12:02
beautiful! Now if only that output could be integrated into the Android Studio
– ChaseTheSun
May 19 '13 at 12:02
4
4
My thoughts exactly. An IDE without a window for compiler errors? I bet we are missing something, but this workaround should be enough until that's addressed.
– Hadi Kocabas
May 19 '13 at 13:09
My thoughts exactly. An IDE without a window for compiler errors? I bet we are missing something, but this workaround should be enough until that's addressed.
– Hadi Kocabas
May 19 '13 at 13:09
4
4
"Are you on windows?" - This also works under Ubuntu Linux too! Thanks!
/[folder-where-you-installed-the-android-studio]/sdk/tools/templates/gradle/wrapper/gradlew build
– geekQ
Jul 15 '13 at 12:37
"Are you on windows?" - This also works under Ubuntu Linux too! Thanks!
/[folder-where-you-installed-the-android-studio]/sdk/tools/templates/gradle/wrapper/gradlew build
– geekQ
Jul 15 '13 at 12:37
I'm in the process of migrating a huge project from Eclipse to Android Studio. Best advise so far: get the command line gradle build working first, then worry about the new IDE.
– Jerry Brady
Oct 21 '13 at 20:19
I'm in the process of migrating a huge project from Eclipse to Android Studio. Best advise so far: get the command line gradle build working first, then worry about the new IDE.
– Jerry Brady
Oct 21 '13 at 20:19
add a comment |
It's really straightforward! Just go to the Compiler settings at Android Studio 2.2.3 and set the --stacktrace
command:
Then run the app again
add a comment |
It's really straightforward! Just go to the Compiler settings at Android Studio 2.2.3 and set the --stacktrace
command:
Then run the app again
add a comment |
It's really straightforward! Just go to the Compiler settings at Android Studio 2.2.3 and set the --stacktrace
command:
Then run the app again
It's really straightforward! Just go to the Compiler settings at Android Studio 2.2.3 and set the --stacktrace
command:
Then run the app again
edited Mar 4 '17 at 18:22
answered Jan 26 '17 at 17:31


Antonio
6,71542141
6,71542141
add a comment |
add a comment |
In my case I prefer to open the Terminal window on the bottom left, and run gradlew build --info
:
1
bash: gradlew: command not found
– Occam's Razor
Jun 6 '16 at 13:54
4
@Pamblam Use ./gradlew
– Rhys
Aug 31 '16 at 17:25
add a comment |
In my case I prefer to open the Terminal window on the bottom left, and run gradlew build --info
:
1
bash: gradlew: command not found
– Occam's Razor
Jun 6 '16 at 13:54
4
@Pamblam Use ./gradlew
– Rhys
Aug 31 '16 at 17:25
add a comment |
In my case I prefer to open the Terminal window on the bottom left, and run gradlew build --info
:
In my case I prefer to open the Terminal window on the bottom left, and run gradlew build --info
:
answered May 19 '16 at 1:00


RominaV
2,0141945
2,0141945
1
bash: gradlew: command not found
– Occam's Razor
Jun 6 '16 at 13:54
4
@Pamblam Use ./gradlew
– Rhys
Aug 31 '16 at 17:25
add a comment |
1
bash: gradlew: command not found
– Occam's Razor
Jun 6 '16 at 13:54
4
@Pamblam Use ./gradlew
– Rhys
Aug 31 '16 at 17:25
1
1
bash: gradlew: command not found
– Occam's Razor
Jun 6 '16 at 13:54
bash: gradlew: command not found
– Occam's Razor
Jun 6 '16 at 13:54
4
4
@Pamblam Use ./gradlew
– Rhys
Aug 31 '16 at 17:25
@Pamblam Use ./gradlew
– Rhys
Aug 31 '16 at 17:25
add a comment |
You can also see the error in the Build window by clicking on the toggle button.
you the real hero bro
– Petro
Nov 14 '18 at 1:14
add a comment |
You can also see the error in the Build window by clicking on the toggle button.
you the real hero bro
– Petro
Nov 14 '18 at 1:14
add a comment |
You can also see the error in the Build window by clicking on the toggle button.
You can also see the error in the Build window by clicking on the toggle button.
answered Jul 7 '18 at 13:16
live-love
16.1k88173
16.1k88173
you the real hero bro
– Petro
Nov 14 '18 at 1:14
add a comment |
you the real hero bro
– Petro
Nov 14 '18 at 1:14
you the real hero bro
– Petro
Nov 14 '18 at 1:14
you the real hero bro
– Petro
Nov 14 '18 at 1:14
add a comment |
In android studio 2.2.3 you can find output in the gradle console as shown below
Exactly what I needed
– Андрій Ковальчук
May 4 '17 at 13:06
add a comment |
In android studio 2.2.3 you can find output in the gradle console as shown below
Exactly what I needed
– Андрій Ковальчук
May 4 '17 at 13:06
add a comment |
In android studio 2.2.3 you can find output in the gradle console as shown below
In android studio 2.2.3 you can find output in the gradle console as shown below
answered Dec 9 '16 at 8:22


cahit beyaz
2,5621719
2,5621719
Exactly what I needed
– Андрій Ковальчук
May 4 '17 at 13:06
add a comment |
Exactly what I needed
– Андрій Ковальчук
May 4 '17 at 13:06
Exactly what I needed
– Андрій Ковальчук
May 4 '17 at 13:06
Exactly what I needed
– Андрій Ковальчук
May 4 '17 at 13:06
add a comment |
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
add a comment |
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
add a comment |
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
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
answered Feb 6 '16 at 7:08
jai
16828
16828
add a comment |
add a comment |
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:
- go to Settings > Build, Execution and Deployment > compiler
- add --stacktrace to the command line options, click apply and ok
- 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.
add a comment |
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:
- go to Settings > Build, Execution and Deployment > compiler
- add --stacktrace to the command line options, click apply and ok
- 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.
add a comment |
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:
- go to Settings > Build, Execution and Deployment > compiler
- add --stacktrace to the command line options, click apply and ok
- 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.
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:
- go to Settings > Build, Execution and Deployment > compiler
- add --stacktrace to the command line options, click apply and ok
- 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.
answered May 5 '18 at 10:00


Peterstev Uremgba
10910
10910
add a comment |
add a comment |
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.
add a comment |
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.
add a comment |
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.
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.
answered Apr 3 '18 at 15:01


Logesh R
8612
8612
add a comment |
add a comment |
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
add a comment |
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
add a comment |
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
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
answered Dec 27 '18 at 22:16


iraqi eagle
263
263
add a comment |
add a comment |
need to add this in your build.gradle file
dependencies {
compile fileTree(dir: 'libs', include: '*.jar')
}
add a comment |
need to add this in your build.gradle file
dependencies {
compile fileTree(dir: 'libs', include: '*.jar')
}
add a comment |
need to add this in your build.gradle file
dependencies {
compile fileTree(dir: 'libs', include: '*.jar')
}
need to add this in your build.gradle file
dependencies {
compile fileTree(dir: 'libs', include: '*.jar')
}
edited Dec 24 '13 at 14:56


Mohsen Safari
4,85133052
4,85133052
answered Jul 31 '13 at 13:17
Koushik
334
334
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f16633956%2fandroid-studio-where-is-the-compiler-error-output-window%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
I run Android Studio 1.3.2 and none of the solutions work.
– Milan Babuškov
Jan 31 '16 at 12:00
3
sucki android studio demands such silly questions to be upvoted.. :)
– Siddharth
Apr 4 '18 at 6:55
maybe it's the idea of IDEA to hide errors ideally (SCNR)
– bebbo
Nov 18 '18 at 11:37
I have also same issue when i update plugin . I use Android Studio 3.4 Canary 6
– Saurabh Gaddelpalliwar
Dec 5 '18 at 12:53