InterruptedException at com.firebase.ui.firestore.paging.FirestorePagingSource.lambda$loadSingle$0(FirestorePagingSource.java)

[marceh]

Hi! I hope I'm in the right place. I've posted my problem on stackoverflow but I'm wondering if there is a problem with the library or not. It might be my code, but it started to happen after updating to the latest FirebaseUI-Android.

Describe your environment

• Android device: 11 different Samsungs,
  motorola edge 20 pro, Lenovo TAB 2 A10-30
• Android OS version: 11, 10, 6.0.1
• Google Play Services version: com.google.android.gms:play-services-base:17.6.0
• Firebase/Play Services SDK version: com.google.firebase:firebase-firestore:23.0.4com.firebaseui:firebase-ui-firestore:8.0.0
• FirebaseUI version: com.firebaseui:firebase-ui-firestore:8.0.0

Step 3: Describe the problem:

I've posted my problem on stackoverflow.

Steps to reproduce:

I'm having lots of trouble reproducing the issue. It only happens to about 2 of 100 users and I don't know how to trigger a InterruptedException. Can't read in the documentation if and where I should catch it.

Observed Results:

I've posted all logs on stackoverflow

Also, if I skip the .setLifecycleOwner(mainActivity) (which says it's optional) the app crash with:
Attempt to invoke interface method 'androidx.lifecycle.Lifecycle androidx.lifecycle.LifecycleOwner.getLifecycle()' on a null object reference com.firebase.ui.firestore.paging.FirestorePagingOptions$Builder.setQuery (FirestorePagingOptions.java:168).

Expected Results:

Expected the code not to crash, worked fine before updating FirebaseUI-Android.

[shushant43]

Did you get a fix for this?

[marceh]

In the further reading, I found an example of an error handler. Not sure if we are expected to use this or if they will fix the InterruptedException in the future. Any how, I implemented it and I'm not receiving any crash reports on this matter any more.

If one decides to add a non-empty global error consumer, here is an example that manages the typical undeliverable exceptions based on whether they represent a likely bug or an ignorable application/network state:

RxJavaPlugins.setErrorHandler(e -> {
    if (e instanceof UndeliverableException) {
        e = e.getCause();
    }
    if ((e instanceof IOException) || (e instanceof SocketException)) {
        // fine, irrelevant network problem or API that throws on cancellation
        return;
    }
    if (e instanceof InterruptedException) {
        // fine, some blocking code was interrupted by a dispose call
        return;
    }
    if ((e instanceof NullPointerException) || (e instanceof IllegalArgumentException)) {
        // that's likely a bug in the application
        Thread.currentThread().getUncaughtExceptionHandler()
            .handleException(Thread.currentThread(), e);
        return;
    }
    if (e instanceof IllegalStateException) {
        // that's a bug in RxJava or in a custom operator
        Thread.currentThread().getUncaughtExceptionHandler()
            .handleException(Thread.currentThread(), e);
        return;
    }
    Log.warning("Undeliverable exception received, not sure what to do", e);
});

[prashant-flobiz]

@marceh Where exactly you added this code?

[marceh]

Just make sure the function is called before initializing the adapter. I made a service using Dagger, that calls this function, which I injected into the activity where the adapter is set up.