Discussion about X-Goog-Firebase-Installations-Auth #25
Conversation
This file contains 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
Added some information about a common behavior.
|
Hi @jjfeldcher this is very interesting. |
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.
I noticed that you don't have to decompile a iOS application to figure out these two values as you can just decode the JWT value in the X-Goog-Firebase-Installations-Auth and look for the API key in the requests. However I cannot find any valid sources to back up my claims as there is nothing from Google itself stating how X-Goog-Firebase-Installations-Auth works.
Before we pull this request in we should discuss if this is correct undocumented behavior which will can use to speed up testing as we don't have to decompile if we can reliability assume these values by looking at the requests.