Exception thrown when client specified an invalid argument. Note that this differs from FailedPreconditionException. This exception indicates arguments that are problematic regardless
of the state of the system (e.g., a malformed file name).
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-01 UTC."],[[["The latest version of the documentation provided is 2.63.1, and this page contains information on the `InvalidArgumentException` across a range of versions, from 2.63.1 down to 2.7.1."],["`InvalidArgumentException` is thrown when a client provides an invalid argument, differing from `FailedPreconditionException` as it highlights problems that exist regardless of the system's state."],["This exception is an extension of `ApiException`, inheriting various methods such as `getDomain()`, `getErrorDetails()`, and `getStatusCode()`."],["There are three constructors available for creating an `InvalidArgumentException`, which includes parameters such as `message`, `cause`, `statusCode`, `retryable`, and `errorDetails`."]]],[]]
