android-studio-3.0

Android Studio 3 - Constraint layout editor broken

僤鯓⒐⒋嵵緔 提交于 2019-11-30 21:45:56
问题 I'm using Android Studio 3.0 (updated to canary 4 today) on macOS for a side project and recently (not sure really when) the constraint layout editor stopped working properly. Now it just shows a grey window and the blueprint view isn't working at all. Even the properties editor on the right doesn't show the constraints anymore. Here how it looks for a simple layout with just 1 button: I'm using constraint layout 1.0.2 but it fails the same way on 1.1.0-beta1 . Any idea what could go wrong?

Error:(1, 0) Plugin with id 'kotlin-android-extensions' not found

懵懂的女人 提交于 2019-11-30 21:26:09
问题 apply plugin: 'kotlin-android-extensions'. When i add this extensions in android studio preview, give me this error "Error:(1, 0) Plugin with id 'kotlin-android-extensions' not found.". My build gradle apply plugin: 'com.android.application' android { compileSdkVersion 26 buildToolsVersion "26.0.1" defaultConfig { applicationId "com.example.mohamed_elbaz.myapplication" minSdkVersion 15 targetSdkVersion 26 versionCode 1 versionName "1.0" testInstrumentationRunner "android.support.test.runner

Why Android change 'compile' to 'implementation' configuration in Gradle dependencies?

纵饮孤独 提交于 2019-11-30 17:49:06
As seen in Android Studio 3.0 (canary 3.0), we now add depedencies by declaring implementation instead of compile configuration. // Before compile 'com.android.support:appcompat-v7:25.3.1' // Currently implementation 'com.android.support:appcompat-v7:25.3.1' We can still use compile , but I would like to understand: What is the difference between implementation and compile configuration? Why do Android Gradle build change to use implementation as default? It seems like compile has been deprecated and api or implementation should be used instead. According to The Java Library Plugin - Gradle

Gradle dependency configuration : implementation vs api vs runtimeonly vs compileonly

牧云@^-^@ 提交于 2019-11-30 15:35:37
问题 Unable to understand the latest gradle dependency configurations which are introduced in Android Studio 3.0 i.e. implementation, api , compileonly and runtimeonly. 回答1: Please refer the link : Android Studio 3.0 New Gradle Configuration available at android developers official site. Based on description mentioned in above link: Implementation: When your module configures an implementation dependency, it's letting Gradle know that the module does not want to leak the dependency to other

“Execution of compression failed” error when building project in Android Studio 3.1

喜夏-厌秋 提交于 2019-11-30 13:17:17
I'm trying to build https://github.com/neural-nuts/Cam2Caption in Android Studio 3.1 Preview, but either I use very old build.gradle, or it dies with Error:Execution failed for task ':Application:packageDebug'. Execution of compression failed. this happens after doing a project clean, or a rebuild. OSX, latest most-everything. I'm using what I think is a default latest-and-greatest build.gradle classpath 'com.android.tools.build:gradle:3.0.0' ... android { compileSdkVersion 26 defaultConfig { minSdkVersion 26 targetSdkVersion 26 } compileOptions { sourceCompatibility JavaVersion.VERSION_1_8

Android Studio 3.0 : canary 6 : android.content.res.Resources$NotFoundException inside Launching activity

早过忘川 提交于 2019-11-30 12:30:18
问题 I update android-studio 3.0 from canary 5 to canary 6 and suddenly My app gives crash on KitKat(API 19) with below stacktrace. The Main2Activity.java:10 line is the first line in my activity onCreate() method. 07-11 13:00:39.523 8913-8913/dcpl.com.myapplication E/AndroidRuntime: FATAL EXCEPTION: main Process: dcpl.com.myapplication, PID: 8913 java.lang.RuntimeException: Unable to start activity ComponentInfo{dcpl.com.myapplication/dcpl.com.myapplication.Main2Activity}: android.content.res

failed linking references after update of gradle Android Studio

做~自己de王妃 提交于 2019-11-30 11:46:45
问题 I got this error after update my Gradle (I have also added maven{jitpack.io} and geofirestore dependencies at the same of updating Gradle) : Android resource linking failed Output: C:\Users\Paul\AndroidStudioProjects\How2Ride2\app\build\intermediates\incremental\mergeDebugResources\merged.dir\values-v28\values-v28.xml:7: error: resource android:attr/dialogCornerRadius not found. C:\Users\Paul\AndroidStudioProjects\How2Ride2\app\build\intermediates\incremental\mergeDebugResources\merged.dir

Unable to compile under Android Studio 3.0 Canary 1

那年仲夏 提交于 2019-11-30 11:27:30
I attempt to compile my Android project under AS 3.0 Canary 1 (it works fine on AS 2.3.2 stable version) but failed with the following error: FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':app:packageInstantRunResourcesUatGoogleDebug'. > com.google.common.util.concurrent.MoreExecutors.directExecutor()Ljava/util/concurrent/Executor; * Try: Run with --info or --debug option to get more log output. * Exception is: org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':app:packageInstantRunResourcesUatGoogleDebug'. at org.gradle.api

Android Studio “error: failed to read metadata” after update to 3.0.0

巧了我就是萌 提交于 2019-11-30 09:58:55
I've updated Android Studio to v3.0.0 and now I cant build my project. Android Studio add .flat to resources file names on build and the build crash because it can't recognize the .flat extension. I've tried to clean the project and rebuild it but I still get this error. I don't have any idea of what could cause this. I hope someone can help me solve my problem cause since Studio can't do a successful build, it can't find my dependencies and I can't work. Gradle Console Output Executing tasks: [clean, :TP2A:assembleDebug, :TP2B:assembleDebug] Configuration on demand is an incubating feature.

Android Studio 3.0 migration AAPT2 error

跟風遠走 提交于 2019-11-30 09:12:33
问题 After migrating my existing project to Android Studio 3.0 , it is not compiling. Below are the log details: Error:java.util.concurrent.ExecutionException: java.util.concurrent.ExecutionException: com.android.tools.aapt2.Aapt2Exception: AAPT2 error: check logs for details Error:java.util.concurrent.ExecutionException: com.android.tools.aapt2.Aapt2Exception: AAPT2 error: check logs for details Error:com.android.tools.aapt2.Aapt2Exception: AAPT2 error: check logs for details Error:Execution