gRPC 5 NOT_FOUND vs 16 UNAUTHENTICATED
Both gRPC 5 (NOT_FOUND) and 16 (UNAUTHENTICATED) belong to the gRPC Status Codes category. 5 indicates that some requested entity was not found. For example, a file or directory that the RPC was supposed to operate on does not exist. Meanwhile, 16 means that the request does not have valid authentication credentials for the operation.
설명
Some requested entity was not found. For example, a file or directory that the RPC was supposed to operate on does not exist.
이 코드를 보게 되는 경우
The resource referenced in the request doesn't exist — such as looking up a user by ID that has been deleted or never created.
해결 방법
Verify the resource identifier is correct. Ensure the resource was created before accessing it, or handle the not-found case gracefully in your client.
설명
The request does not have valid authentication credentials for the operation.
이 코드를 보게 되는 경우
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.
해결 방법
Provide valid authentication credentials (e.g., refresh the OAuth token, regenerate the API key, or renew the client certificate).
주요 차이점
gRPC 5: Some requested entity was not found. For example, a file or directory that the RPC was supposed to operate on does not exist.
gRPC 16: The request does not have valid authentication credentials for the operation.
You encounter 5 when the resource referenced in the request doesn't exist — such as looking up a user by ID that has been deleted or never created.
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.
언제 어떤 것을 사용할지
For 5 (NOT_FOUND): Verify the resource identifier is correct. Ensure the resource was created before accessing it, or handle the not-found case gracefully in your client. For 16 (UNAUTHENTICATED): Provide valid authentication credentials (e.g., refresh the OAuth token, regenerate the API key, or renew the client certificate).