gRPC 3 INVALID_ARGUMENT vs 12 UNIMPLEMENTED
Both gRPC 3 (INVALID_ARGUMENT) and 12 (UNIMPLEMENTED) 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, 12 means that the operation is not implemented or is not supported/enabled in this service.
描述
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.
描述
The operation is not implemented or is not supported/enabled in this service.
何时出现
The client called an RPC method that the server does not implement. This often happens when the client uses a newer proto definition than the server supports.
如何修复
Verify the server version supports the method you're calling. Update the server to implement the missing method, or use an alternative endpoint.
主要区别
gRPC 3: The client specified an invalid argument. This indicates arguments that are problematic regardless of the state of the system.
gRPC 12: The operation is not implemented or is not supported/enabled in this service.
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 12 when the client called an RPC method that the server does not implement. This often happens when the client uses a newer proto definition than the server supports.
何时使用哪个
For 3 (INVALID_ARGUMENT): Inspect the request payload and fix the invalid field. Check the API documentation for expected formats and constraints. For 12 (UNIMPLEMENTED): Verify the server version supports the method you're calling. Update the server to implement the missing method, or use an alternative endpoint.