android-studio-3.0

When I use Android Studio 3.0 and I use the next version of Android Gradle Plugin in project/build.gradle : classpath 'com.android.tools.build:gradle:3.0.1' And it's work fine. After I update to Android Studio 3.1 , as result I update Android Gradle Plugin : classpath 'com.android.tools.build:gradle:3.1.0' And now I get error in my app/build.gradle : def releaseFileName = "${rootProject.name}_${defaultConfig.versionName}.apk" outputFileName = new File(rootProject.projectDir.absolutePath + "/release", releaseFileName.toLowerCase()) Error: Absolute path are not supported when setting an output

I recently noticed a new file generated at <module>/release/output.json by Android Studio 3 Canary 1 each time I run Build -> Generate Signed APK... , which has contents that look like following. Can anyone confirm seeing this behavior as well? Or is it due to some local configuration on my laptop? And can anyone explain the purpose of this file? Is it safe to add to .gitignore ? [{ "outputType": { "type": "APK" }, "apkInfo": { "type": "MAIN", "splits": [], "versionCode": 32 }, "outputFile": { "path": "/path/to/the/generated/release/filename.apk" }, "properties": { "packageId": "com.example

After upgrading Android Studio 3.0 Beta 1 getting the following error. When I downgraded the error disappeared. Studio Build: Android Studio 3.0 Beta 1 Version of Gradle Plugin: 'com.android.tools.build:gradle:3.0.0-beta1' Version of Gradle:.0.0-beta1 Version of Java: 8 OS: MacOSX java.lang.NoClassDefFoundError: Failed resolution of: Lcom/google/devtools/build/android/desugar/runtime/ThrowableExtension; at io.reactivex.plugins.RxJavaPlugins.onError(RxJavaPlugins.java:364) at io.reactivex.android.schedulers.HandlerScheduler$ScheduledRunnable.run(HandlerScheduler.java:113) at android.os.Handler

It's good to have a Updated Android Studio 3.0 . But I am facing a problem with Android Studio 3.0 , I just created a new project in Android Studio 3.0 . Then I got some error I solved these by changing dependencies to latest version and issues solved. But, when I added a dependency of facebook account-kit sdk com.facebook.android:account-kit-sdk:4.+ I am getting following errors-: Error:Unable to resolve dependency for ':app@debug/compileClasspath': Could not resolve com.facebook.android:account-kit-sdk:4.+. Open File Show Details build.gradle(app) apply plugin: 'com.android.application'

Using new android studio with new 3.0.0 Gradle pluging. When building some warning happened: registerResGeneratingTask is deprecated, use registerGeneratedFolders(FileCollection) From what I can tell, plugins added as classpath dependencies will give problems. I.e. Firebase had an issue with it. Spoon and Flutter as well. Doing this Google search reveals a lot of GitHub repos with an issue raised over the same thing, and all they have in common is the fact that it's a Gradle plugin. Fabric appears to be a cause as well, as mentioned by Mate * From what I can tell, the issue comes from a

AndroidStudio 3.0 / Android Gradle plugin 3.0 <vector> <path android:fillColor="@color/image_button_disabled"/> </vector> I get this error: references to other resources are not supported by build-time PNG generation Will it be possible to resolve it or is it a deprecated solution? mwa91 In your app build.gradle add the following line: defaultConfig{ vectorDrawables.useSupportLibrary = true } See Android Developers: Vector Drawables Backward Compatibility Solution for details. you need to use the hex code directly not referring to a resource. <vector <path android:fillColor="#FFF"/></vector>

I try to publish my Android instant app to Google Play; I link the app, which is named helloinstantapp.instantapp.examples.chrisyttang.org to the domain https://csytang.github.io . It has been verified by Android Studio as you can see in the following image; However, when I try to publish my app into Google Play with Google Play Console, I get the error that "the site csytang.github.io has not been linked through the DAL protocol to your app." Why this happen? Did you by any chance enable Google Play App Signing ? If yes, then you need to use the fingerprint provided by the Play Console,