You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Doing a call to the signInMutation with jwtToken as part of the query now leads to an error 400 bad request with the following payload
{ "errors": [{ "message": "Cannot query field \"jwtToken\" on type \"CurrentUser\".", "locations": [{ "line": 6, "column": 27 }], "extensions": { "code": "GRAPHQL_VALIDATION_FAILED" } }] }
If I remove this from the mutation, the login works however, currentUser no longer returns the jwtToken required as part of the request header for following requests. Is this a bug on the development side?
The text was updated successfully, but these errors were encountered:
Doing a call to the signInMutation with jwtToken as part of the query now leads to an error 400 bad request with the following payload
{ "errors": [{ "message": "Cannot query field \"jwtToken\" on type \"CurrentUser\".", "locations": [{ "line": 6, "column": 27 }], "extensions": { "code": "GRAPHQL_VALIDATION_FAILED" } }] }
If I remove this from the mutation, the login works however, currentUser no longer returns the jwtToken required as part of the request header for following requests. Is this a bug on the development side?
The text was updated successfully, but these errors were encountered: