android - 在 Android Studio 3.3 中分析失败

Question

我刚刚将 Android Studio 3.2 更新到 3.3。它将我项目中的 Gradle 插件从 3.2.1 更新到 3.3。现在在 Run/Debug configuration 中启用高级分析使我的应用程序崩溃。 Clean/Rebuild/Invalidate caches 没有帮助。

我找到了一种让它工作的方法:将插件回滚到 3.2.1(在项目 build.gradle 中)

dependencies {
    classpath 'com.android.tools.build:gradle:3.2.1'
}

还有其他办法吗？

01-15 13:38:31.527 6969-6969/? E/AndroidRuntime: FATAL EXCEPTION: main
    Process: com.appcard.androidterminal, PID: 6969
    java.lang.NoClassDefFoundError: Failed resolution of: Lcom/android/tools/profiler/support/ProfilerService;
        at com.appcard.androidterminal.AppContext.<init>(AppContext.java:53)
        at java.lang.reflect.Constructor.newInstance(Native Method)
        at java.lang.Class.newInstance(Class.java:1606)
        at android.app.Instrumentation.newApplication(Instrumentation.java:1000)
        at android.app.Instrumentation.newApplication(Instrumentation.java:985)
        at android.app.LoadedApk.makeApplication(LoadedApk.java:567)
        at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4837)
        at android.app.ActivityThread.access$1500(ActivityThread.java:178)
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1531)
        at android.os.Handler.dispatchMessage(Handler.java:111)
        at android.os.Looper.loop(Looper.java:194)
        at android.app.ActivityThread.main(ActivityThread.java:5643)
        at java.lang.reflect.Method.invoke(Native Method)
        at java.lang.reflect.Method.invoke(Method.java:372)
        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:960)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:755)
     Caused by: java.lang.ClassNotFoundException: Didn't find class "com.android.tools.profiler.support.ProfilerService" on path: DexPathList[[zip file "/data/app/com.appcard.androidterminal-1/base.apk"],nativeLibraryDirectories=[/data/app/com.appcard.androidterminal-1/lib/arm, /vendor/lib, /system/lib]]
        at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:56)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:511)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:469)
        at com.appcard.androidterminal.AppContext.<init>(AppContext.java:53) 
        at java.lang.reflect.Constructor.newInstance(Native Method) 
        at java.lang.Class.newInstance(Class.java:1606) 
        at android.app.Instrumentation.newApplication(Instrumentation.java:1000) 
        at android.app.Instrumentation.newApplication(Instrumentation.java:985) 
        at android.app.LoadedApk.makeApplication(LoadedApk.java:567) 
        at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4837) 
        at android.app.ActivityThread.access$1500(ActivityThread.java:178) 
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1531) 
        at android.os.Handler.dispatchMessage(Handler.java:111) 
        at android.os.Looper.loop(Looper.java:194) 
        at android.app.ActivityThread.main(ActivityThread.java:5643) 
        at java.lang.reflect.Method.invoke(Native Method) 
        at java.lang.reflect.Method.invoke(Method.java:372) 
        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:960) 
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:755) 
        Suppressed: java.lang.ClassNotFoundException: com.android.tools.profiler.support.ProfilerService
        at java.lang.Class.classForName(Native Method)
        at java.lang.BootClassLoader.findClass(ClassLoader.java:781)
        at java.lang.BootClassLoader.loadClass(ClassLoader.java:841)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:504)
                ... 17 more
     Caused by: java.lang.NoClassDefFoundError: Class not found using the boot class loader; no stack available

Answer 1

我填了一个错误，这是谷歌开发者的回应:

I was able to reproduce the issue with emulator API 25 and lower. Workaround is to use device/emulator API of 26 or higher.

https://issuetracker.google.com/issues/122944954#comment4

更新:

Yes, this has been fixed. The fix won't be in 3.3.1, but it will be in the following release.