It looks like there might be instances where Google's BillingClient.startConnection simply never finishes, and that's where the connection would entirely fail.

This is nearly impossible to reproduce artificially, sadly, but we're trying to think about solutions.

It seems from Google's docs (or the closest thing to it, sadly) that this should only happen in fairly rare causes, if the Google Play Store self-upgrades or is force closed.

Does the volume you're seeing seem to match up with that?

Originally posted by @aboedo in #524 (comment)

We have a value to report now that adoption is at its peak. It is close to 400 counts in the last 7 days for only two versions. I believe you should revisit this with your team to see if they can find a workaround.