-
Notifications
You must be signed in to change notification settings - Fork 309
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: set Content-Type header in the request to signBlob API to avoid Invalid JSON payload error #439
fix: set Content-Type header in the request to signBlob API to avoid Invalid JSON payload error #439
Conversation
de6ba94
to
632808a
Compare
…Invalid JSON payload error
632808a
to
431b0c3
Compare
I think this is a serious bug which makes it impossible to create a custom token using a service account ID with Firebase Admin Python SDK. |
I ended up using private key file. |
Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, or one of your required reviews was not approved. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot. |
auth.create_custom_token()
results in an error:I have confirmed setting
'Content-Type': 'application/json'
header resolves the problem.