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-08-20 UTC."],[[["`HtmlBundleProcessorError` identifies errors during HTML5 file processing within Google Ad Manager."],["Errors can range from file size and quantity limitations to issues with click tags, Flash files, and GWD components."],["The `reason` field provides specific details about the error encountered, categorized by an enum."],["HTML5 bundles are expected to have a primary HTML file (ideally named `index.html`) and adhere to size and file number restrictions."],["Google Web Designer (GWD) bundles have specific requirements for click tags and component usage."]]],["This content outlines error handling for ad management services, specifically focusing on `HtmlBundleProcessorError` and its association with other errors. Key actions involve processing HTML5 bundles, with detailed reasons for failure. These include issues like incorrect or missing click tags, unsupported Flash files, size or file number limits, missing primary HTML files, and GWD component issues. The `ApiError` class provides fields for error context like field path, trigger, and error string.\n"]]
