We have released Android Studio 3.0 Canary 8 to the Canary and Dev Channels. This release fixes the following issues:

Read more

We have released Android Studio 3.0 Canary 8 to the Canary and Dev Channels. This release fixes the following issues:

• Issue #63586454:  JavaUastLanguagePlugin may fail to translate a PsiMethod to a UMethod
• Issue #63562276:  Resizing widgets in LinearLayout has weird behavior
• Issue #38236114:  Edittext input type dialog does not fit screen
• Issue #63295952:  extractProguardFiles task is not incremental
• Issue #37334887:  Layout editor: some view properties have insufficient field height
• Issue #63623801:  ResourceNotFoundException thrown when deploying a Kotlin project to an AVD running API 16

Our primary focus at this stage is to stabilize Android Studio 3.0 to a beta quality release. Please keep sending your feedback by clicking Help > Submit Feedback.

We have released Android Studio 3.0 Canary 7 to the Canary and Dev Channels.

Read more

We have released Android Studio 3.0 Canary 7 to the Canary and Dev Channels.

Changes

• Specify matching build types. If a consumer (such as an app module) defines a build type that does not exist in a producer dependency (such as a library module), the variant-aware dependency resolution model won’t know which version of the producer to use and your build fails with the following error:
  
  Error:Failed to resolve: Could not resolve project :mylibrary.
  Required by:
     project :app

You can now specify an alternative build type the consumer should use from the producer using the android.buildTypeMatching property as shown below. The plugin uses the alternative build type only if a matching build type is not found.
android {
   …
   // Let’s say your app configures a ‘staging’ build type and a library module
   // it depends on does not. You can use the property below to tell the Android plugin
   // to use a library’s ‘debug’ build type instead.
   buildTypeMatching ‘staging’, ‘debug’
}
Fixes We had a number of fixes make it into this build a few reported by our external users include:

• 63623801 ResourceNotFoundException running Kotlin project on API 16 AVD after upgrading to Canary 6 
• 37111818 Layout Editor cannot edit widget margins in RelativeLayout
• 63252394 Android studio 3.0 canary build variants auto resolving error

Our primary focus at this stage is to stabilize Android Studio 3.0 to a beta quality release. Please keep sending your feedback by clicking Help > Submit Feedback.

We have released Android Studio 3.0 Canary 6 to the Canary and Dev Channels. This release fixes a variety of bugs, such as the following:

Read more

We have released Android Studio 3.0 Canary 6 to the Canary and Dev Channels. This release fixes a variety of bugs, such as the following:


Fixes

• Fixed an issue that caused java.io.IOException to be thrown due to broken R.txt.
• Fixed an issue that prevented you from updating the Kotlin IDE plugin. (issue #62697211)
• Fixed an issue that caused captured memory allocations to not display when using the Memory Profiler.
• Fixed an issue where you need to invoke Code > Convert Java to Kotlin twice before the IDE converts your code.

Known Issues

• IDE is not showing gradle upgrade plugin version dialog after close and reopen older plugin version project
• IDE error "Invalid file" while deleting kotlin or java class files
• Kotlin configure yellow ribbon does not show up until the file reopens after converting
• IDE fatal error "java.util.NoSuchElementException" while removing copy pasted code from kotlin
• IDE fatal error "Project is not yet initialized" while cloning desugar project
• Attaching to debugger fails while working the combination of c++,kotlin and instant app enabled
• Instant Run currently does not work with Gradle build cache. To use Instant Run, make sure you disable the build cache in your build.properties file: org.gradle.caching=false

Please keep sending your feedback by clicking Help > Submit Feedback.