@kpalser Thanks. Interestingly, in my case the problem suddenly disappeared on February 25th. It wasn’t caused by an app update or any other changes on our end. Even more interestingly, at the exact same moment another minor, non-fatal issue disappeared - a Crashlytics remote config problem. So, they were definitely related. It could be that the SSL problem was caused by Crashlytics/remote config, or conversely, an SSL issue was causing troubles for Firebase. Anyway, I guess it’s worth checking on your end too. Cheers

Hello, @kpalser , I have exactly the same problem as you, did you found a solution already? I've two more observations, on top of the ones listed in your post. My app userbase is mostly in Poland, but it seems the problem never occurs for polish users. May be something related to mobile/cell configuration in other countries? (this one is not confirmed): I believe problem started after updating a number of third party libraries some time ago. So probably, something outside of the app itself is triggering it.. Unfortunately, it's not easy to downgrade all of the libs we update to verify it, without affecting the users.