New Root‎ > ‎

Known Issues

Gradle Sync Failed: Broken Pipe

The issue is that the Gradle daemon is trying to use IPv4 instead of IPv6.
Workaround 1: On Linux, put the following in your ~/.profile or ~/.bash_profile: export _JAVA_OPTIONS=""
Workaround 2: in Android Studio's vmoptions file, change the line to 
More details: Networking IPv6 User Guide

Spurious Render Exception

The specific render error message is:
The following classes could not be found:

Despite the error message, the layout preview is correct and the message can be safely ignored. The issue has already been fixed in 2.0 preview. See bug 192102 for more details.

Frozen Keyboard Input: "iBus" Problems on Linux

There are some known interactions between the iBus daemon on Linux and Android Studio. This is discussed more in this document: Android Studio & ibus-daemon interactions.

Difficulties Loading Older Gradle Projects

Please see the migration document.

JUnit tests missing resources in classpath when run from Studio

Issue: If you have specific resource folders in your Java modules, then those resources won't be found when running tests from the IDE. Running tests using Gradle from the command line will work. Executing the gradle check task from the IDE will also work. See Issue 64887 for more details.

This issue happens because as of IntelliJ 13, you can only have a single folder as the classpath. IntelliJ's builder copies all resources into that build folder. But Gradle doesn't copy over the resources.

You can use any of the following workarounds until then:
 - Run the gradle check task from the IDE rather than running a unit test
 - Or update your build script to manually copy resources into the build folder. See comment #13.

Running JUnit tests compiles the code twice

When creating a new project, the template JUnit configuration may be created with two "Before launch" steps: Make and Gradle-aware Make. This is then propagated to all created JUnit run configurations. To fix the issue, go to Run -> Edit Configurations and change the default JUnit configuration to only include the Gradle-aware Make step. To fix this for all future projects, close the current project (File -> Close Project) to get to the welcome screen, select Configure -> Project Defaults -> Run Configurations and make the same change.

Some test run configurations don't work

Not all run configurations that are available when right-clicking a test method are valid. Specifically:
  • Gradle run configurations (ones with Gradle logo as the icon) don't work.
  • JUnit run configurations (icon without a green android) don't apply to instrumentation tests, which can't be run on the local JVM.
Additional problem is that Android Studio remembers the run configuration created in a given context (e.g. right-clicking a given class/method) and will not offer to run a different one in the future. To fix this, go to Run > Edit Configurations and remove the incorrectly created configurations.

Linux and the Awesome WM

In Android Studio 0.8.3+:
Studio 0.8.3 does not work properly on Linux with the "Awesome WM" window manager version 3.4. It's supposed to work with 3.5.

Ubuntu and JAyatana

JAyatana allows Java Swing applications to integrate with the global menu in Ubuntu's Unity graphical shell. We have reports of Studio running into a NullPointerException under Unity:
    at com.jarego.jayatana.swing.SwingGlobalMenu.getSwingGlobalMenuWindowController(
    at com.jarego.jayatana.swing.SwingGlobalMenu.installLockParentGlobalMenu(
    at ...
There are two possible workarounds:
  • unset the JAVA_TOOL_OPTIONS environment variable when running Studio;
  • uninstall JAyatana. 
Newer Ubuntu versions are also disabling JAyatana by default because of these unintended interactions with Java applications.

Can't Update to Latest Version

On Windows, files that are in use by a process cannot be deleted. 

When you attempt to use the built-in update mechanism in the IDE, it sometimes refuses to install the update, usually providing an error message like "Can't delete C:\some\path\file".
To work around this, open the task manager and attempt to kill processes that may be using the file, such as any gradle daemons.