Michael Lehenbauer

I'm running into this as well. In case it's of any help, I think the issue may only occur when you are using the "spawn" start method of multiprocessing (i.e....

I had the same issue. It turns out I was using `dataLength` wrong. I thought it was supposed to be the total length of items that _could_ be displayed, but...

@girlslearningcodeyul Ah, bummer. You may have a different issue than me then. In my case I was setting `dataLength` to be a number much greater than the number of children...

@girlslearningcodeyul Yay! 🎉 Glad it's working. Strangely, I ended up doing something different. If I had 48 items, then on first load, I'd set `dataLength` to 20, and then on...

@nardocesar Hah, glad it helped but no need to buy me coffee! Feel free to send that goodwill towards somebody else you run across who could use it. Have a...

@tgangso Thanks for the feedback! (and sorry it didn't work out for you). We'll discuss to see if we can do anything about the performance. In the meantime, were you...

@tgangso Thanks very much for the data. We'll plan to keep the option around unless the problem stops happening or we devices a better solution (like automatic fallback).

@tgangso FYI- There was a backend change that should cut down on the number of network requests when using this option. Would you be interested in trying it again and...

@rodrigoreis22 Not super easily. But you can call `firebase.app().delete()` and then call `firebase.initializeApp(...)` again, and then `firebase.firestore()` will return a brand new instance which you can call `.settings({experimentalForceLongPolling: true})` on......

@bhar4t Thanks for the report. `experimentalForceLongPolling` is meant to work around a specific "broken" network configuration that's unrelated to your connection speed. So I wouldn't expect it to have an...