You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our app users have reported an issue where the app is slow to start, sometimes taking around 1 minute to fully load. This problem occurs when their devices have no data left, even though mobile data is turned on. Interestingly, this issue does not happen when mobile data is turned off.
The app is built using Flutter. We suspect that this issue is caused by the Firebase Messaging SDK on Android, which assumes the connection will recover soon and thus runs a retry operation. This retry operation appears to occur after Firebase.initializeApp is called:
Hi @haizadvnet, thank you for reaching out. For context, SERVICE_NOT_AVAILABLE means one of the following issues:
The phone is offline.
The phone is online but it cannot reach Google servers.
The firebase messaging servers are temporarily unavailable.
Google Play services are not installed on the phone.
Google Play services are in an extremely bad state.
Currently, there is no way to disable the topic sync retry operation. Disabling topic synchronization means that your app will not receive updates to topics or topic subscriptions from the Firebase backend that might affect the apps that relies on topic-based messaging.
I'll mark this as a feature request to keep this under our radar. However, we can’t provide any timeline for this.
For folks who find this useful, adding an emoji thumbs up on the original post can help us prioritize adding this to the roadmap.
Our app users have reported an issue where the app is slow to start, sometimes taking around 1 minute to fully load. This problem occurs when their devices have no data left, even though mobile data is turned on. Interestingly, this issue does not happen when mobile data is turned off.
The app is built using Flutter. We suspect that this issue is caused by the Firebase Messaging SDK on Android, which assumes the connection will recover soon and thus runs a retry operation. This retry operation appears to occur after Firebase.initializeApp is called:
The log message after opening the app is as follows:
We want to disable the retry operation because we don't want the user to wait too long for the app to start. How can we achieve this?
The text was updated successfully, but these errors were encountered: