AI-generated Key Takeaways
- 
          
This document describes the possible errors that can occur with media bundles.
 - 
          
Errors can range from issues with the request or server to problems with the media bundle file itself, its contents, or specific features used.
 - 
          
Some specific types of media bundles or creation tools are not supported.
 - 
          
The table provides a comprehensive list of these potential errors with brief descriptions.
 
Enum describing possible media bundle errors.
| Enums | |
|---|---|
 | 
                Enum unspecified. | 
 | 
                The received error code is not known in this version. | 
 | 
                There was a problem with the request. | 
 | 
                HTML5 ads using DoubleClick Studio created ZIP files are not supported. | 
 | 
                Cannot reference URL external to the media bundle. | 
 | 
                Media bundle file is too large. | 
 | 
                ZIP file from Google Web Designer is not published. | 
 | 
                Input was invalid. | 
 | 
                There was a problem with the media bundle. | 
 | 
                There was a problem with one or more of the media bundle entries. | 
 | 
                The media bundle contains a file with an unknown mime type | 
 | 
                The media bundle contain an invalid asset path. | 
 | 
                HTML5 ad is trying to reference an asset not in .ZIP file | 
 | 
                Media data is too large. | 
 | 
                The media bundle contains no primary entry. | 
 | 
                There was an error on the server. | 
 | 
                The image could not be stored. | 
 | 
                Media bundle created with the Swiffy tool is not allowed. | 
 | 
                The media bundle contains too many files. | 
 | 
                The media bundle is not of legal dimensions. | 
 | 
                Google Web Designer not created for "Google Ads" environment. | 
 | 
                Unsupported HTML5 feature in HTML5 asset. | 
 | 
                URL in HTML5 entry is not ssl compliant. | 
 | 
                Custom exits not allowed in HTML5 entry. |