android-studio-3.0

问题 I'm already to install android studio ,and when i want to download components like sdk manager etc, I'm stuck in here like this: 回答1: I had exactly the same issue I became frustrated after seeing these downloads repeatedly which is not descriptive. Also it took lot of time to download on high speed internet. Just wait it will be finished. 回答2: i had the same situation and i thought it was a problem but it's not. just wait until it finished . it needs hours to downmoad all components ! 来源：

问题 Getting Error: Error:Unable to resolve dependency for ':app@debugUnitTest/compileClasspath': Could not resolve com.googlecode.mp4parser:isoparser:1.1.22. Open File Show Details For Dependency: compile 'com.googlecode.mp4parser:isoparser:1.1.22' But for dependency: compile 'com.googlecode.mp4parser:isoparser:1.1.20' Gradle Sync Successfully. Tried using repository: repositories { mavenCentral() } Detailed Error: Unable to resolve dependency for ':app@StagingUnitTest/compileClasspath': Could

问题 When I try to list and download system images in AVD Manager, nothing shows up in the list. See below: None of the three tabs show the images, even after I hit refresh. I have made sure I have a working fast Internet connection. I have checked the SDK Manager also. Nothing related to system images is there for download. My list of SDK update sites is as follows (https://dl.google.com/android/repository/repository2-1.xml and a local repo on my system): 回答1: First remove Android settings

问题 I'm trying to add Spek testing framework to my Android Studio project. Following the instructions Here, I ended up adding the following to my module build.gradle : testCompile 'org.jetbrains.spek:spek-api:1.1.5' testCompile 'junit:junit:4.12' testCompile "org.junit.platform:junit-platform-runner:1.0.0" testRuntimeOnly 'org.jetbrains.spek:spek-junit-platform-engine:1.1.5' Then I annotated my test with @RunWith(JUnitPlatform::class) However, when I try to run the test, I get: org.junit.platform

问题 Having compilation error with the following build.gradle details : Top-Level build.gradle buildscript { repositories { google() jcenter() mavenCentral() } dependencies { classpath 'com.android.tools.build:gradle:3.0.0' } } allprojects { repositories { google() jcenter() mavenCentral() maven { url 'https://maven.google.com' } } } task clean(type: Delete) { delete rootProject.buildDir } App-Level build.gradle apply plugin: 'com.android.application' android { compileSdkVersion 27 defaultConfig {

问题 Every thing working fine before updating Android studio from 2.3 to 3.0. I had this error when running app in Android Studio, complile is pass. I can't understand why this error appears. And I found nothing in Internet. here is my gradle file. packagingOptions { exclude 'META-INF/DEPENDENCIES.txt' exclude 'META-INF/LICENSE.txt' exclude 'META-INF/NOTICE.txt' exclude 'META-INF/NOTICE' exclude 'META-INF/LICENSE' exclude 'META-INF/DEPENDENCIES' exclude 'META-INF/notice.txt' exclude 'META-INF

问题 I am using Dji-SDK. Recently i migrated the SDK from version 4.2 to 4.3.2. After changing the dji-sdk.aar in the libs folder i am not able to build because of the merge issues in the manifest. The merged manifest in build is getting created as follows. ... <uses-permission android:name="android.permission.USE_CREDENTIALS" /> <receiver android:name="dji.logic.receiver.DJIPilotStartupReceiver" android:exported="true" android:permission="dji.permission.sdk.wifi" > <intent-filter> <action android

问题 I'm trying to learn how to identify and treat memory leaks in my App. I'm reading this great article, but I'm a bit confused about how to apply that in the new "Android Profiler" tool, that came with Android Studio 3.0. I'have a test application and LeakCanary is pointing that my App has memory leaks. In fact, when I run the profiler and press "dump java heap" I can see that there are 4 instances of my MyCollectionActivity and, when I click on these instances, I can see the details: But the

问题 I have an application module, let's say "Test". The "Test" module depends on a sub-module B. Both enable databinding. In library module B, I create a simple activity using databinding, its purpose is for reusability, for example: I can create a base Login screen and use it in many apps later. Below is sample code in Package B. package com.test.packageb open class MainActivity : AppCompatActivity() { lateinit var binding : ActivityMainBinding override fun onCreate(savedInstanceState: Bundle?)

问题 After upgrading to Android Studio v3.0 the design view for all my layouts look like below, i.e. ActionBarOverlayLayout covers the whole design surface, and the app does not even use the actionbar. In the manifest the application element is: <application android:name=".MyAppName" android:allowBackup="true" android:icon="@mipmap/ic_launcher" android:label="@string/app_name" android:supportsRtl="true" android:theme="@style/AppTheme"> And AppTheme is defined in styles.xml like <style name=