quickstart-android: E/RunLoop: Uncaught exception in Firebase runloop (3.0.0)

Strange error! what is the issue behind this? Recently only, I’m seeing this error 😦

compile ‘com.google.firebase:firebase-database:9.0.2’ compile "‘om.google.firebase:firebase-auth:9.0.2’

E/RunLoop: Uncaught exception in Firebase runloop (3.0.0). Please report to support@firebase.com                                                
 java.lang.NullPointerException: Attempt to invoke virtual method 'void com.google.android.gms.internal.zzafg.zzg(com.google.android.gms.internal.zzafa, com.google.android.gms.internal.zzahu)' on a null object reference
                                                                   at com.google.android.gms.internal.zzafc.zzb(Unknown Source)
                                                                   at com.google.android.gms.internal.zzafc.zzat(Unknown Source)
                                                                   at com.google.firebase.database.connection.idl.IPersistentConnectionImpl$3.zzJ(Unknown Source)
                                                                   at com.google.firebase.database.connection.idl.zzi$zza.onTransact(Unknown Source)
                                                                   at android.os.Binder.transact(Binder.java:387)
                                                                   at alx.a(:com.google.android.gms.DynamiteModulesC:211)
                                                                   at amb.a(:com.google.android.gms.DynamiteModulesC:339)
                                                                   at akf.a(:com.google.android.gms.DynamiteModulesC:6851)
                                                                   at ajt.a(:com.google.android.gms.DynamiteModulesC:5191)
                                                                   at akw.b(:com.google.android.gms.DynamiteModulesC:226)
                                                                   at akw.a(:com.google.android.gms.DynamiteModulesC:271)
                                                                   at ald.run(:com.google.android.gms.DynamiteModulesC:1020)
                                                                   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:423)
                                                                   at java.util.concurrent.FutureTask.run(FutureTask.java:237)
                                                                   at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:269)
                                                                   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
                                                                   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
                                                                   at java.lang.Thread.run(Thread.java:818)

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 29 (5 by maintainers)

Most upvoted comments

The same problem is happening with equalTo() method. Is there any usage of startAt/endAt inside equalTo?

rafaelperatello on Sep 7, 2016

@samtstern - I have tried the new SDK 9.4.0 and the issue still persist. It arose when we used startAt() and endAt() for the first time. Our app is not multiprocess one (checked via the methods provided on StackOverflow) and we do not use the crash SDK.

There seems to be no progress on the mailing list, StackOverflow or this issue for a long time. Has it been tracked somewhere at Google? Have you got a chance to reproduce it? And why the issue is closed?

curiousily on Aug 2, 2016

I still see this issue while using transaction with version 9.0.8.

irfaan008 on Apr 2, 2017

@samtstern Thank you for the response. That is all ok. Where can we (as users) track the progress on the fix?

curiousily on Sep 8, 2016

@samtstern can you at least mark the issue as open, please?

curiousily on Sep 6, 2016

@samtstern will there be a fix for the multi process problem or a fix for the startAt and endAt stuff? My app crashes all the time during development because of the dirty offline cache state. I can’t release it in this state

RichardGottschalk on Sep 4, 2016

Here is an excerpt from a response from the Firebase support team:

Apologies for any inconvenience this might have caused your development. We are already aware of this issue, wherein queries with integer startAt / endAt values could get written multiple times to persistence causing tracked queries to be corrupt, leading to a crash. However, I cannot give you any timeline for the release. Rest assured that we are actively working hard to address this issue.

In the meantime, try to avoid having queries with endAt or startAt when data persistence is enabled. Keep an eye on our release notes for further update. Again, sorry for the inconvenience.

curiousily on Aug 3, 2016