由於Firebase（生產版本），Android應用無法啟動

Question

我有5個安裝了Firebase SDK的應用程序，它們現在無法正常工作。 目前有3個在市場上。 （ 我認為這是一個非常重要的問題。我正在考慮從所有應用程序中刪除Firebase ）

在Firebase網站上，眾所周知崩潰服務存在問題。 但這會殺死應用程序。 看來他們測試得不好。 這是它可能遇到的最嚴重的錯誤。

注意：

• 三星S4沒問題。 （Google Play服務版本9.4.52）
• 三星S6有此問題。 （Google Play服務版本9.6.80）

我不知道該怎么辦。 我之所以使用Google產品，是因為我信任它們，但這並不是我所期望的。 這是屬於此問題的ANR報告的副本部分：

"main" prio=5 tid=1 TimedWaiting
  | group="main" sCount=1 dsCount=0 obj=0x772656c8 self=0x7f83df4a00
  | sysTid=31731 nice=0 cgrp=default sched=0/0 handle=0x7f87e16fc8
  | state=S schedstat=( 0 0 0 ) utm=4 stm=3 core=7 HZ=100
  | stack=0x7fcb72d000-0x7fcb72f000 stackSize=8MB
  | held mutexes=
  at java.lang.Object.wait!(Native method)
  - waiting on <0x0b2c7b14> (a java.lang.Object)
  at java.lang.Thread.parkFor$(Thread.java:1220)
  - locked <0x0b2c7b14> (a java.lang.Object)
  at sun.misc.Unsafe.park(Unsafe.java:299)
  at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:198)
  at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2053)
  at java.util.concurrent.ArrayBlockingQueue.poll(ArrayBlockingQueue.java:372)
  at com.google.android.gms.chimera.container.GmsModuleFinder$StageFileApksResultReceiver.a(:com.google.android.gms:476)
  at com.google.android.gms.chimera.container.GmsModuleFinder.c(:com.google.android.gms:2458)
  at com.google.android.gms.chimera.container.DynamiteLoaderImpl.getModuleVersion2(:com.google.android.gms:42)
  at mgq.onTransact(:com.google.android.gms:83)
  at android.os.Binder.transact(Binder.java:387)
  at com.google.android.gms.internal.eo$a$a.a(unavailable:-1)
  at com.google.android.gms.internal.eg.a(unavailable:-1)
  at com.google.android.gms.internal.eh.a(unavailable:-1)
  at com.google.android.gms.internal.ei.a(unavailable:-1)
  at com.google.android.gms.internal.eg.a(unavailable:-1)
  at com.google.android.gms.internal.er.a(unavailable:-1)
  - locked <0x04e8afbd> (a com.google.android.gms.internal.er)
  at com.google.firebase.crash.internal.config.flag.Flags.a(unavailable:-1)
  at com.google.firebase.crash.FirebaseCrash.getInstance(unavailable:-1)
  at java.lang.reflect.Method.invoke!(Native method)
  at q.a.a(unavailable:-1)
  at q.a.a(unavailable:-1)
  at q.a.a(unavailable:-1)
  at com.google.firebase.provider.FirebaseInitProvider.onCreate(unavailable:-1)
  at android.content.ContentProvider.attachInfo(ContentProvider.java:1789)
  at android.content.ContentProvider.attachInfo(ContentProvider.java:1764)
  at com.google.firebase.provider.FirebaseInitProvider.attachInfo(unavailable:-1)
  at android.app.ActivityThread.installProvider(ActivityThread.java:6762)
  at android.app.ActivityThread.installContentProviders(ActivityThread.java:6357)
  at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6297)
  at android.app.ActivityThread.access$1800(ActivityThread.java:221)
  at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1860)
  at android.os.Handler.dispatchMessage(Handler.java:102)
  at android.os.Looper.loop(Looper.java:158)
  at android.app.ActivityThread.main(ActivityThread.java:7224)
  at java.lang.reflect.Method.invoke!(Native method)
  at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1230)
  at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1120)

Answer 1

我聯系了Firebase支持人員，這是他們的答案：

Hi David,

Thanks for reaching out to us, and sorry if you're having problem with this.

We're currently testing potential fix for this issue. This has been introduced with the Google Play Services 9.6.80, and affects all the apps using the Firebase Crash reporting.
For temporary workaround, you'll have to disable crash reporting on your app. You can remove its entry "com.google.firebase:firebase-crash:9.4.0" on your build.gradle file. 

As posted in our dashboard, all affected customers should expect a new version of Google Play services (9.6.83) by 9/17.
You can follow these links for further updates:
Firebase Status Dashboard
Google Group Discussion
Stack Overflow post
Again, apologies for the inconvenience here, David. 

Regards,
∞Allen

因此，明天應該有一個新版本的GPS修復。