"Internal server error" without a `reason` when token expires

[ltroya-as]

Hi guys,

I am receiving an Internal server error when the token expires without any other useful message that helps me identify the error's cause.

E.g:

However, if I enable the "Enable GraphQL Debug Mode", it returns the cause (invalid-jwt) of the issue but there is a warning on that option not to allow that on the production environment.
Screenshot:

The status code is always 200 for both cases.

Is there anything I can do to receive the error on the production environment when sending an expired token?

[AVert]

Same

[alvarolog]

Hi, I have been struggling with the same problem and finally a found a possible solution, you can add an action to intercept the token error and send an UserError response instead a WP_Error, so you can read the response in the errors variable

add_action('graphql_before_resolve_field', function () {
    $token = \WPGraphQL\JWT_Authentication\Auth::validate_token();
    if (is_wp_error($token)) {
        throw new \GraphQL\Error\UserError($token->get_error_code());
    }
}, 0);

[fasteiner]

@alvarolog thanks for the workaround, however, it would be prudent to include a better error message into the built-in error handling, so that all integrations can properly react on a expired token. @jasonbahl