Bypass Firebase App-Check #234
Merged
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
|
@nilathedragon, this seems to work and thanks much!!! @samrum, could you please merge this PR ASAP? Thanks!!! |
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 would like to contribute the results of my research on OnStar's recent addition of Firebase App-Check.
As I explained in the issue (#233), each client credential pair likely has their own rules applied to them. This is the case for
the iOS credentials as well. They are configured in a way that Firebase App-Check is not required.
Simply switching to the iOS client credentials & user agent should make your library work again. In my local test I was able to run functional tests again.
This change also means that in the future, you would need to source your credential pair from the iOS app.