android-studio-3.0

Newly installed Android studio 3.1.3 is giving strange dependencies error when making a new project and compiling for very first time. A similar question that didn't help resolve the problem. Event Logs: Unable to resolve dependency for ':app@debug/compileClasspath': Could not resolve com.android.support:appcompat-v7:28.0.0-alpha3. Open File Show Details Unable to resolve dependency for ':app@debug/compileClasspath': Could not resolve com.android.support.constraint:constraint-layout:1.1.2. Open File Show Details Unable to resolve dependency for ':app@debugAndroidTest/compileClasspath': Could

I recently installed new stable version of Android Studio (v3.0). Then created a new project and there was not any problem. But saw there is no buildToolsVersion field in the app-level build.gradle file. Even I searched all project files ( Ctrl Shift F ), but didn't find anything! What does this mean? And how can I determine what is the version of Build Tools in my app module? build.gradle (Project): // Top-level build file where you can add configuration options common to all sub-projects/modules. buildscript { repositories { google() jcenter() } dependencies { classpath 'com.android.tools

I previously was using Android Studio v2.3 to Make Module and it was ok. Now I changed to Android Studio v3.0, when I trying to Make Module, it shows the error below: Error:Android Source Generator: Error: Can't find bundle for base name messages.AndroidJpsBundle, locale en_US java.util.MissingResourceException: Can't find bundle for base name messages.AndroidJpsBundle, locale en_US at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:1564) at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1387) at java.util.ResourceBundle.getBundle(ResourceBundle.java:773)

I recently installed the latest Canary build of Android Studio which is currently using the Android Gradle plugin 3.0.0-alpha4 . I now get a error: Error:Failed to resolve: Could not resolve project :MyLib. Required by: project :app I has read: Migrate dependency configurations for local modules dependencies { // This is the old method and no longer works for local // library modules: // debugCompile project(path: ':foo', configuration: 'debug') // releaseCompile project(path: ':foo', configuration: 'release') // Instead, simply use the following to take advantage of // variant-aware

I just updated my Android Studio to 3.0 canary 1. Now I am working on my existing project on Android Studio 3.0 canary 1. By default gradle:3.0.0-alpha1 is set in my project: gradle_file. So I changed my gradle version to 2.2.3 and now I'm getting this error: Error:Failed to complete Gradle execution. Cause: The version of Gradle you are using (3.3) does not support the forTasks() method on BuildActionExecuter. Support for this is available in Gradle 3.5 and all later versions. I attached my gradle file here // Top-level build file where you can add configuration options common to all sub

I am trying a sample with Room Persistence Library . I created an Entity: @Entity public class Agent { @PrimaryKey public String guid; public String name; public String email; public String password; public String phone; public String licence; } Created a DAO class: @Dao public interface AgentDao { @Query("SELECT COUNT(*) FROM Agent where email = :email OR phone = :phone OR licence = :licence") int agentsCount(String email, String phone, String licence); @Insert void insertAgent(Agent agent); } Created the Database class: @Database(entities = {Agent.class}, version = 1) public abstract class

So I'm reading Android 6 for Programmers: An App-Driven Approach and the first two app examples I had no issues with the examples, this time the FlagQuiz example when loaded in Android Studio 3.0 Canary-3 I'm getting this error which isn't letting me build the project: Error:Unsupported method: BaseConfig.getApplicationIdSuffix(). The version of Gradle you connect to does not support that method. To resolve the problem you can change/upgrade the target version of Gradle you connect to. Alternatively, you can ignore this exception and read other information from the model. You can download the