由于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修复。