gRPC 2 UNKNOWN vs 3 INVALID_ARGUMENT
Both gRPC 2 (UNKNOWN) and 3 (INVALID_ARGUMENT) belong to the gRPC Status Codes category. 2 indicates that an unknown error occurred. This may be returned when a server raises an exception that doesn't map to any known gRPC status code. Meanwhile, 3 means that the client specified an invalid argument. This indicates arguments that are problematic regardless of the state of the system.
説明
An unknown error occurred. This may be returned when a server raises an exception that doesn't map to any known gRPC status code.
このコードが表示される場合
The server threw an unhandled exception or returned an error that gRPC couldn't classify into a more specific status code.
解決方法
Check the server logs for the underlying exception. Wrap server-side errors with explicit gRPC status codes instead of letting them bubble up as UNKNOWN.
説明
The client specified an invalid argument. This indicates arguments that are problematic regardless of the state of the system.
このコードが表示される場合
A request field failed validation — for example, a negative page size, a malformed email, or a required field left empty.
解決方法
Inspect the request payload and fix the invalid field. Check the API documentation for expected formats and constraints.
主な違い
gRPC 2: An unknown error occurred. This may be returned when a server raises an exception that doesn't map to any known gRPC status code.
gRPC 3: The client specified an invalid argument. This indicates arguments that are problematic regardless of the state of the system.
You encounter 2 when the server threw an unhandled exception or returned an error that gRPC couldn't classify into a more specific status code.
You encounter 3 when a request field failed validation — for example, a negative page size, a malformed email, or a required field left empty.
どちらをいつ使うか
For 2 (UNKNOWN): Check the server logs for the underlying exception. Wrap server-side errors with explicit gRPC status codes instead of letting them bubble up as UNKNOWN. For 3 (INVALID_ARGUMENT): Inspect the request payload and fix the invalid field. Check the API documentation for expected formats and constraints.