gRPC 3 INVALID_ARGUMENT vs 16 UNAUTHENTICATED
Both gRPC 3 (INVALID_ARGUMENT) and 16 (UNAUTHENTICATED) belong to the gRPC Status Codes category. 3 indicates that the client specified an invalid argument. This indicates arguments that are problematic regardless of the state of the system. Meanwhile, 16 means that the request does not have valid authentication credentials for the operation.
Descripción
The client specified an invalid argument. This indicates arguments that are problematic regardless of the state of the system.
Cuándo lo verás
A request field failed validation — for example, a negative page size, a malformed email, or a required field left empty.
Cómo solucionarlo
Inspect the request payload and fix the invalid field. Check the API documentation for expected formats and constraints.
Descripción
The request does not have valid authentication credentials for the operation.
Cuándo lo verás
No credentials were provided, or the provided token/certificate is expired or invalid. Different from PERMISSION_DENIED (code 7), which means authenticated but not authorized.
Cómo solucionarlo
Provide valid authentication credentials (e.g., refresh the OAuth token, regenerate the API key, or renew the client certificate).
Diferencias clave
gRPC 3: The client specified an invalid argument. This indicates arguments that are problematic regardless of the state of the system.
gRPC 16: The request does not have valid authentication credentials for the operation.
You encounter 3 when a request field failed validation — for example, a negative page size, a malformed email, or a required field left empty.
You encounter 16 when no credentials were provided, or the provided token/certificate is expired or invalid. Different from PERMISSION_DENIED (code 7), which means authenticated but not authorized.
Cuándo usar cada uno
For 3 (INVALID_ARGUMENT): Inspect the request payload and fix the invalid field. Check the API documentation for expected formats and constraints. For 16 (UNAUTHENTICATED): Provide valid authentication credentials (e.g., refresh the OAuth token, regenerate the API key, or renew the client certificate).