A parsed copy of the field path. For example, the field path "operations[1].operand"
corresponds to this list: {FieldPathElement(field = "operations", index = 1),
FieldPathElement(field = "operand", index = null)}.
trigger
xsd:string
The data that caused the error.
errorString
xsd:string
A simple string representation of the error and reason.
[[["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 2024-11-19 UTC."],[[["The `MobileApplicationService` relates to managing mobile applications within the Google Ad Manager platform."],["This service outlines potential errors (e.g., `MobileApplicationError`, `ApiError`) that can occur during mobile application operations."],["These errors are categorized and provide specific reasons for the error, like invalid app IDs, internal errors, or exceeding application limits."],["The service includes details on the error's context, such as the field path and the data that triggered it, to aid in troubleshooting."],["Developers can use this information to understand and handle errors effectively when interacting with the MobileApplicationService."]]],["The `MobileApplicationService` details errors that can occur with `MobileApplication` objects. These errors, extending from `ApiError`, include issues like invalid app IDs, exchange partner settings, and exceeding active app limits. It defines various reasons for `MobileApplicationError`, such as `INVALID_APP_ID`, `NAME_OR_STORE_ID_MUST_BE_SET`, or `PUBLISHER_HAS_TOO_MANY_ACTIVE_APPS`. Additionally, there are specific errors related to app store IDs, such as invalid formats, missing entries, and non-unique IDs within the same platform.\n"]]
