Known Issues

    Tools 22.6

    The command line lint script (tools\lint.bat on Windows platforms, tools/lint on other platforms) and the lint target on ant builds fail with the following error:

    Exception in thread "main" java.lang.NoClassDefFoundError: lombok/ast/AstVisitor

    As a temporary workaround, rename the file tools\lib\lombok-ast-0.2.2.jar to tools\lib\lombok-ast.jar. We will release an updated version of the tools with a fix for this issue as soon as possible.

    Android Studio 0.5.1

    Creating a new blank file does not work (New > File). Other types of files are not affected -- New Java class, package, Android resource file works. We'll fix this in 0.5.2.
    https://code.google.com/p/android/issues/detail?id=66818

    Android Studio 0.5.0

    If you are on Mac OSX, and you are trying to use Java 7 to run Android Studio, the IDE may not start. There are two possible workarounds:

    1. Invoke /Applications/Android Studio.app/Contents/MacOS/studio directly
    2. Switch back to Java 6 on OSX. (NOTE: You do not need to run Android Studio with Java 7 in order to use Android 4.4 language features; the IDE can use a different JDK than the one associated with your project.)
      Edit your Android Studio.app/Contents/Info.plist file back to using <string>1.6*</string>
    Android Studio 0.4.6 & 0.5.0

    The "build" directory in Java-only project modules (non-Android) is being excluded, causing ClassNotFoundExceptions in the layout preview/editor if you use these library classes from custom views. A workaround is to open the .iml file in the module and remove the line:

    <excludeFolder url="file://$MODULE_DIR$/build" />


    Android Studio 0.4.1

    There is a bug which prevents building the project from working sometimes (see issue 64607). We've fixed this issue in 0.4.2 which is now available; please upgrade.


    Android Studio 0.4.0 & Gradle 1.10

    Note: You must use Gradle 1.9 with Gradle 0.4.0. Gradle 1.10 will not work.


    Android Gradle Plugin 0.6.2

    The Android Gradle plugin 0.6.2 was published with incorrect dependencies. There isn't a way to delete it, so we have instead release 0.6.3 which fixes the problems. Just switch your version from 0.6.+ to 0.6.3, or run gradlew with --refresh-dependencies to force Gradle to look for an update.

        dependencies {
            classpath 'com.android.tools.build:gradle:0.6.+'
        }

    instead of
        dependencies {
            classpath 'com.android.tools.build:gradle:0.6.3'
        }

    Android Studio 0.3 / 

    Using JDK 6 on Linux
    On some Linux systems, Studio fails with this error message: "The window must use a translucency-compatible graphics configuration". To work around this, use JDK 7 instead. This is bug http://youtrack.jetbrains.com/issue/IDEA-114626 which will be fixed in the next version of Studio.

    0.5.0 Upgrade

    As noted in Android Studio 0.2.0 Released, you will need to update your projects to the gradle plugin 0.5; without that, project import and sync will not work in the IDE. 

    If you prefer to make this change by hand, you basically need to find 
    dependencies {
        classpath 'com.android.tools.build:gradle:0.4.0'
    }

    and replace it with

    dependencies {
        classpath 'com.android.tools.build:gradle:0.5.+'
    }

    (You can use "0.5.1" instead of "0.5.+" if you prefer; the latter will basically automatically adapt to 0.5.2, 0.5.3 etc as they are released.)

    NOTE: You should not use 0.5.0; use 0.5.1 if you do not want to use the + syntax. We've released a new version to fix a bug in 0.5.0. Search for "VariantDependencies" in this document to see the relevant troubleshooting section.

    Bundled Maven Repository

    If for some reason you are using a different SDK than the bundled one, you may run into the following gradle build error if your project depends on the v4 support library:

    FAILURE: Build failed with an exception.

    * What went wrong:
    A problem occurred configuring project ':MyApplication'.
    > Failed to notify project evaluation listener.
       > Could not resolve all dependencies for configuration ':MyApplication:_DebugCompile'.
          > Could not find any version that matches com.android.support:support-v4:13.0.+.
            Required by:
                MyApplicationProject:MyApplication:unspecified

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

    BUILD FAILED

    To fix this, open the SDK manager, and make sure that the "Android Support Repository" (not just Android Support Library) is installed:

    Corrupted Install on Windows

    There are some reports that on Windows, running the installer will simply install 0.2.0 in place on top of 0.1.9. And apparently that can lead to problems. 

    One symptom of this is the following error message:

    6:40:33 PM ClassCastException: cannot assign instance of com.android.build.gradle.internal.model.DependenciesImpl to field com.android.build.gradle.internal.model.ArtifactInfoImpl.dependencies of type com.android.builder.model.Dependencies in instance of com.android.build.gradle.internal.model.ArtifactInfoImpl: cannot assign instance of com.android.build.gradle.internal.model.DependenciesImpl to field com.android.build.gradle.internal.model.ArtifactInfoImpl.dependencies of type com.android.builder.model.Dependencies in instance of com.android.build.gradle.internal.model.ArtifactInfoImpl

    To fix this, move the older installation out of the way before running the 0.2.0 installer (or alternatively, uninstall it first).

    Task 'assemble' not found

    If you get the following error message:

    Gradle: 
    FAILURE: Could not determine which tasks to execute.

    * What went wrong:
    Task 'assemble' not found in root project 'MyProject'.

    * Try:
    Run gradle tasks to get a list of available tasks.


    The real problem is that previous version of Android Studio misconfigured the IDEA file (e.g. MyProject.iml) -- it added an extra "<component name="FacetManager">" XML element that shouldn't be present. In the case above, the solution is to edit "MyProject.iml" and to remove the "<component name="FacetManager">" part as shown here:

    <?xml version="1.0" encoding="UTF-8"?>
    <module external.system.id="GRADLE" type="JAVA_MODULE" version="4">
      <component name="FacetManager">
        ...remove this element and everything inside such as <facet> elements...
      </component>
      <component name="NewModuleRootManager" inherit-compiler-output="true">
        ...keep this part...
      </component>
    </module>

    Alternatively you could remove the project's .idea folder and iml files and re-import your sources into a new Android Studio project.

    In the next release we'll fix this -- there will be a "fix this" button to do that fix automatically for you.

    No such property: type for class: com.android.build.gradle.internal.dependency.VariantDependencies

    If you run into the following compilation error:

    > No such property: type for class: com.android.build.gradle.internal.dependency.VariantDependencies
      Possible solutions: name
    ...
    Caused by: groovy.lang.MissingPropertyException: No such property: type for class: com.android.build.gradle.internal.dependency.VariantDependencies
    Possible solutions: name
    at com.android.build.gradle.internal.dependency.DependencyChecker.getConfigName(DependencyChecker.groovy:81)
    at com.android.build.gradle.internal.dependency.DependencyChecker.excluded(DependencyChecker.groovy:53)
    at com.android.build.gradle.internal.dependency.DependencyChecker$excluded.call(Unknown Source)

    This is a bug in the gradle plugin version 0.5.0. We released a new version, 0.5.1, which fixes this.

    If you are using this dependency:
    dependencies {
        classpath 'com.android.tools.build:gradle:0.5.0'
    }

    you should replace it with 0.5.+ or 0.5.1:

    dependencies {
        classpath 'com.android.tools.build:gradle:0.5.+'
    }

    If you are already using 0.5.+, it may not immediately detect that there is a better version than 0.5.0 available, because gradle does not connect for every build; it checks for updates at a regular interval, perhaps a day.
    You can run with --refresh-dependencies to force gradle to check for new versions in its dependencies.

    Windows: Application doesn't launch [fixed in 0.1.1]
    We have 2 possible issues:
    • On some systems the launcher script does not find where Java is installed. Workaround is to set a variable indicating the location of Java [b/55281]:
      • Open Start menu > computer > System Properties >  Advanced System Properties
      • In the Advanced tab > Environment Variables, add new system variable JAVA_HOME that points to your JDK folder, for example C:\Program Files\Java\jdk1.7.0_21.
    • Another issue we found is that the launcher script uses an option that is unknown to Java on some system [b/55267]
      • Open the installation folder of Android Studio (e.g. C:\Programs Files\Android\android-studio, or C:\Users\<username>\AppData\Local\Android\android-studio) and find the "bin" directory in there.
      • Open a "cmd.exe" (command prompt), cd to the android-studio\bin folder and run "studio.bat". You will most likely see an error: for example  b/55267 is about the option -XX:+UseCodeCacheFlushing not being recognized. Report the error, remove the line from the studio.exe.vmoptions or studio64.exe.vmoptions and it should now work.
    Apologies for this weak launcher.
    We know 0.1 is pretty rough and we're working actively on getting things better.


    Tools R20

    SDK Manager
    • If you have Tools 20.0.1 and don't see the latest 20.0.3 update, a simple solution is to open SDK Manager Tools 20.0.1 and use the menu Packages > Reload. You will then see the Tools 20.0.3 update.
    • Explanation: The SDK Manager in Tools 20.0.0 now has a cache mechanism -- it keeps a local copy of small manifest XML files to perform a faster start when opened. There's also a mechanism to automatically update the cache. However in Tools 20.0.0 and 20.0.1, that refresh is broken and in some conditions the manager will not show new tools that are available unless a reload is performed. Clearing the SDK Manager cache or manually forcing a reload forces the manager to get the latest manifest.

    Tools R15

    SDK Manager
    • When using the command-line interface to install packages, system-images are not installed. [See issue for a workaround: 21880]

    Tools R14


    Emulator
    • Fixed in r15. Wipe data is broken. Manually remove userdata-qemu.img from the AVD folder under .android/avd/<avdname>.avd/ (Mac/Linux: in ~, Windows XP: C:\Documents and settings\<user>\, Windows Vista/7: C:\Users\<user>).
    • Snapshot support is not completely working for Android 4.0 system image for now. After loading a snapshot, some hardware features (sensors, gps, camera) will be broken.
    • Loading earlier snapshots (created with tools version < 14) is broken. Symptoms include emulator failing to boot or crashing. We will improve version detections to more gracefully handle incompatible snapshot format, but for now, you’ll need to delete them and recreate them.
    • Fixed in r15. Some linux users are reporting crashes when launching the emulator and have figured out that trying to access the webcam is the culprit. [Issue: 20952]
    You can disable the webcam by editing the AVD ini file and adding hw.webcam.count=0 in it.
    Note that you can also add this through the AVD Manager. Edit the AVD and in the hardware section, click add, find "Number of emulated web cameras" in the drop down and add it to your AVD.

    Build System
    • Fixed in r15. Project not building with error
      [2011-10-20 23:32:04 - MyApp] Dx UNEXPECTED TOP-LEVEL EXCEPTION:<class>: already added: <class>
    This is due to a failure to remove previous library source folders from the main project. Incidentally, the fragility around those linked source folders is one of the reason we are moving away from this mechanism (see more info at http://tools.android.com/recent/buildchangesinrevision14).
    The solution is to remove those <libraryname>_src source folders from your projects. Just right click them and choose Build Path > Remove from Build Path. You should also be prompted to remove the linked folder which you should do. If you're not prompted, remove it manually.
    You can see some screenshot of the problem in this great post: http://android.foxykeep.com/dev/fix-the-conversion-to-dalvik-format-failed-with-error-1-with-adt-14
    • 9-patch issue in Library. If the 9-patches located in library don't look like 9-patch (they appear as stretched bitmap) in your application, try to refresh the library project and do a clean build of the application. Changing your workspace to refresh automatically will help as well (in Preferences under General > Workspace). We will be improving this to not require forced refreshes.
    • Fixed in r15. Renderscript fails to compile application targeting 11-13. This is due to the build system passing older headers to the compiler. [Issue 21006]
      Workaround: Replace <SDK>/platforms/android-[11|12|13]/renderscript with the version located at <SDK>/platforms/android-14/renderscript

    • AAPT crashes on Windows in some cases when the build output is set to verbose.
      The workaround is to set Eclipse>Preferences>Android>Build>Build Output to less than Verbose, e.g. Normal.
      We have a fix, which will be available in tools 16. [Issue 20395]

    • AAPT crashes when a <style> (in a resource XML file) contain an <item> with a "+@id/..." reference.
      AAPT should either ignore this or report an error since this is not the place to create a new id.
      The workaround is to not use the +, write the reference as "@id/...". [Issue 20479]

    DDMS/ADT LogCat View
    Fixed in r15. On certain machines, the logcat view will stop scrolling to show the latest received log message. Moving the scroll bar manually to the end should trigger the view to auto scroll, but it stops again after a short time.

    SDK Manager
    When updating Platforms Tools, the log displays an error: 'adb kill-server' failed -- run manually if needed’. The error is benign, please ignore it -- in fact it just means ADB isn't running, so it can't be stopped. [Issue: 18868]

    AVD Manager
    Fixed in r15. Crash when creating an AVD for the GoogleTV addon [Issue 20963].
    Workaround is available at http://stackoverflow.com/questions/7824203/android-sdk-14-cant-create-gtv-device/7843608#7843608


    ADT
    • Projects don't show the Project Libraries container with the library jar files.
      This can happen when starting Eclipse. Closing and opening the offending project should properly populate it again with the library jar files.
    • Fixed in r15. The SDK Manager and the AVD Manager windows cannot be resized. On Linux, behavior is a bit odd -- the window can be shrunk but not expanded. [Issue: 20939]

    Testing
    Fixed in r15. ant test fails with Syntax error: Bad substitution.
    A last minute change introduced this error in the Ant rules file. The workaround is to edit <SDK>/tools/ant/build.xml, line 318 and to change ${manifest.package} with ${tested.manifest.package}
    . [Issue 20979]

    Tools
    Fastboot.exe is missing from the tools folder. It will be added later in tools 16. In the meantime it can be found in the tools 13 windows archive. [Issue 21115]



    Tools R13

    SDK Manager
    • "Help, I'm using the SDK Manager and don't see any old SDK, I can't update anything except SDK Tools 14".

    This is expected if you're using the SDK Manager from ADT 13 or earlier, or the tools 13 or earlier. We had to change the XML schema used by the download site to support some new features. Please first update the tools to Tools 14, or your ADT to version 14. You'll be then able to install all the SDK platforms and packages as usual.
    • On Windows, updating the tools may result in the following error:
    Updating SDK Manager.exe
    Error: The process cannot access the file because it is being used by another process.

    There are 2 easy workarounds:
    - Open an Explorer on the SDK tools folder and manually launch android.bat from there.
    - Open a cmd.exe, cd to your SDK and type "tools\android.bat".
    [Issue 11989]