tsapeta commented 1 hour ago
Hi everyone,
I’m really sorry you’re encountering this issue on production apps — I can confirm it’s caused by an update to Google Play Services that we can’t really control. That’s a bit of a shame that Google is doing such things. Anyway, we will do our best to release this workaround to our builders. I intentionally don’t name it a fix, because we used the API correctly, according to the documentation.
Please give us some time to precisely test it before the release, we will keep you informed.