Replies: 1 comment
-
This is most likely an implementation error. Please see some suggestions on debugging here: Feel free to share more info if you're unable to get things working, and please update here if you identify the problem. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the bug
Error Message displayed when trying to login new user with the /example project
Version
^0.13.0-alpha.0 (also tried 0.12.1)
To Reproduce
Steps to reproduce the behavior:
Error: Problem getting a refresh token: {"error":{"code":400,"message":"INVALID_CUSTOM_TOKEN","errors":[{"message":"INVALID_CUSTOM_TOKEN","domain":"global","reason":"invalid"}]}}
at /Users/davidcarter/work/next-firebase-auth/example/node_modules/next-firebase-auth/build/index.node.js:2:10542
at Generator.next ()
at asyncGeneratorStep (/Users/davidcarter/work/next-firebase-auth/example/node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:24)
at _next (/Users/davidcarter/work/next-firebase-auth/example/node_modules/@babel/runtime/helpers/asyncToGenerator.js:25:9)
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:97:5)
Expected behavior
I expect the user to login without an error.
Additional context
tried on Brave and Chrome
Beta Was this translation helpful? Give feedback.
All reactions