在 Android SDK 29 中将 "play-services-base" 17.1.0 更新为 17.2.0 后,应用程序不断崩溃

App keep crashing after update "play-services-base" 17.1.0 to 17.2.0 in Android SDK 29

我已将 Android SDK 28 更新为 29,并将 google 播放依赖项 "com.google.android.gms:play-services-base:17.1.0" 更新为 "com.google.android.gms:play-services-base:17.2.0"。 当我尝试 运行 应用程序时,它一直在崩溃。 但是如果我将版本更改为 17.1.0 那么它工作正常。 日志如下。 TIA.

2020-03-25 15:28:37.998 6632-6707/? E/AndroidRuntime: FATAL EXCEPTION: pool-16-thread-1
Process: com.shohoz.rides.stage, PID: 6632
java.lang.NoSuchMethodError: No static method isAtLeastR()Z in class Landroidx/core/os/BuildCompat; or its super classes (declaration of 'androidx.core.os.BuildCompat' appears in /data/app/com.shohoz.rides.stage-AaRQwnY2Dls36TLm52LoRw==/base.apk)
    at com.google.android.gms.common.util.PlatformVersion.isAtLeastR(com.google.android.gms:play-services-basement@@17.2.0:21)
    at com.google.android.gms.common.api.GoogleApi.zaa(com.google.android.gms:play-services-base@@17.2.0:128)
    at com.google.android.gms.common.api.GoogleApi.<init>(com.google.android.gms:play-services-base@@17.2.0:41)
    at com.google.android.gms.common.api.GoogleApi.<init>(com.google.android.gms:play-services-base@@17.2.0:56)
    at com.google.android.gms.internal.clearcut.zze.<init>(Unknown Source:8)
    at com.google.android.gms.internal.clearcut.zze.zzb(Unknown Source:2)
    at com.google.android.gms.clearcut.ClearcutLogger.anonymousLogger(Unknown Source:2)
    at com.google.firebase.perf.internal.zzf.zzbt(com.google.firebase:firebase-perf@@19.0.5:55)
    at com.google.firebase.perf.internal.zzf.zzc(com.google.firebase:firebase-perf@@19.0.5:195)
    at com.google.firebase.perf.internal.zze.run(com.google.firebase:firebase-perf@@19.0.5:2)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
    at java.lang.Thread.run(Thread.java:919)

这是 Google Play 服务新版本中的错误。注意崩溃方法 isAtLeastR - R 目前正在开发中 (API30) - 此崩溃仅发生在 Android 10 (Q, API29)

留在 17.1.0 并等待 17.2.1 或永远不会:)

编辑:您的问题是 ...