Updated gtm session fetcher to allow for exponential backoff #10777
Conversation
There was a problem hiding this comment.
If Storage is not using any new GTMSessionFetcher APIs, I'm not sure we should start requiring GTMSessionFetcher 3.1. Anyone who wants the new capability can already get it by updating and those that have other dependencies requiring earlier GTM versions won't be impacted.
|
@paulb777 - the main reason for the upgrade is to fix situations when exponential backoff is required. For example, if there's an issue with an intermediary Google Cloud service, without this fix, we will just keep hitting the server infinitely, draining resources on people's machines. |
|
Context: google/gtm-session-fetcher#323 |
|
There is nothing stopping developers from updating GTMSessonFetcher now to 3.1 if they can. I'd prefer to avoid breaking interoperability with SDKs like ARCore until a major release, when we have a process to engage with other SDK teams on dependency changes. |
|
Marked for the next breaking change of Firebase 11 to update the minimum allowed version of GTMSessionFetcher. |
|
Please close, merge, or comment. We plan to close stale PRs on November 28, 2023. |
No description provided.