Replies: 1 comment 1 reply
-
|
The only change in v3 is it requiring urql core v6 which you can see in the changelog |
Beta Was this translation helpful? Give feedback.
1 reply
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.
Uh oh!
There was an error while loading. Please reload this page.
-
First... is it weird that
exchange-authhas a 3.0.0 release on npm but there's no history of it in github releases?Back to the question...
After rolling back @urql/exchange-auth from v3.0.0 to v2.2.1, authentication works correctly.
With v3.0.0:
It's clearly not a suspended api key because rolling back to v2 works as expected with the same key.
Here's our clent code so you can see how we're doing the auth. But, the error is thrown by the last catch in
getAuthTokenwhich makes it seem like a firebase issue. Why would the version of exchange-auth influence firebase token acquisition?Thanks for any insights!
Beta Was this translation helpful? Give feedback.
All reactions