fix: ApiClientUtils.getDefaultTransport() should return a cached instance to an ApacheHttp2Transport - #1059
Merged
jonathanedey merged 5 commits intoJan 23, 2025
Merged
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
…ance to an `ApacheHttp2Transport`
lahirumaramba
approved these changes
Jan 23, 2025
lahirumaramba
left a comment
Copy link
Copy Markdown
Member
There was a problem hiding this comment.
Thanks! LGTM!
Sorry, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This fixes an unintentional change in ApiClientUtils.getDefaultTransport() which caused firebaseOptions to create a new instance of the default transport on firebaseOptions build. This only affected developers who made multiple calls to FirebaseOptions.builder(...).build() or initialized multiple app instances.