Possible console errors
Stay organized with collections
Save and categorize content based on your preferences.
All messages printed to the console will have the prefix [Ad Placement API]:
You can only set preloadAdBreaks once:
adConfig() was already called to set preloadAdBreaks with value <VALUE>
Tried to call adBreak() while another call to adBreak() was still in process
(ensure that you are not triggering ads from other workers, and that you are not
calling adBreak() from within a callback function):
Cannot show ad while another ad is already visible.
Failures when executing any callback you have provided:
<CALLBACK NAME> callback threw an error: <ERROR>
Errors in tagging parameters:
Invalid data-ad-frequency-hint value: '<VALUE>'. It must be in format 'Xs'
where X is a number.Unsupported data-adbreak-test value '<VALUE>'. Supported values: 'on'.
adConfig() argument validation errors:
Invalid ad config: <ERROR>. Where <ERROR> can be:
preloadAdBreaks must be one of ['auto', 'on']sound must be one of ['on', 'off']onReady must be a function
adBreak() argument validation errors:
Invalid placement config: <ERROR>. Where <ERROR> can be:
missing required properties <LIST OF PROPERTIES><CALLBACK NAME> must be a function<PROPERTY NAME> must be one of <LIST OF VALID VALUES>the following properties are not used for the given ad type:
<LIST OF PROPERTIES>
Renamed callbacks in adBreak() (beforeBreak, afterBreak, and adComplete
have been renamed to beforeAd, afterAd and adViewed respectively. They
still function in exactly the same way):
Placement config: <OLD> has been renamed to <NEW>. Please update your code.Invalid placement config: <OLD> has been renamed to <NEW>. Cannot pass both
fields. Please use <NEW> only.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2023-12-05 UTC.
[null,null,["Last updated 2023-12-05 UTC."],[[["\u003cp\u003eThe Ad Placement API uses the prefix \u003ccode\u003e[Ad Placement API]\u003c/code\u003e for all console messages and allows preloading ad breaks only once using \u003ccode\u003eadConfig()\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers should avoid calling \u003ccode\u003eadBreak()\u003c/code\u003e while another ad is displaying and ensure proper tagging parameters like \u003ccode\u003edata-ad-frequency-hint\u003c/code\u003e and \u003ccode\u003edata-adbreak-test\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eadConfig()\u003c/code\u003e and \u003ccode\u003eadBreak()\u003c/code\u003e require specific arguments, including callbacks, and will generate errors if invalid values are provided.\u003c/p\u003e\n"],["\u003cp\u003eCallbacks in \u003ccode\u003eadBreak()\u003c/code\u003e have been renamed (\u003ccode\u003ebeforeBreak\u003c/code\u003e to \u003ccode\u003ebeforeAd\u003c/code\u003e, \u003ccode\u003eafterBreak\u003c/code\u003e to \u003ccode\u003eafterAd\u003c/code\u003e, and \u003ccode\u003eadComplete\u003c/code\u003e to \u003ccode\u003eadViewed\u003c/code\u003e) and using the old names will result in errors.\u003c/p\u003e\n"],["\u003cp\u003eThe API provides detailed error messages for troubleshooting, including specific reasons for failures and invalid configurations.\u003c/p\u003e\n"]]],[],null,["# Possible console errors\n\nAll messages printed to the console will have the prefix `[Ad Placement API]`:\n\nYou can only set preloadAdBreaks once:\n\n- `adConfig()` was already called to set `preloadAdBreaks` with value `\u003cVALUE\u003e`\n\nTried to call `adBreak()` while another call to `adBreak()` was still in process\n(ensure that you are not triggering ads from other workers, and that you are not\ncalling `adBreak()` from within a callback function):\n\n- `Cannot show ad while another ad is already visible.`\n\nFailures when executing any callback you have provided:\n\n- `\u003cCALLBACK NAME\u003e callback threw an error: \u003cERROR\u003e`\n\nErrors in tagging parameters:\n\n- `Invalid data-ad-frequency-hint value: '\u003cVALUE\u003e'. It must be in format 'Xs'\n where X is a number.`\n- `Unsupported data-adbreak-test value '\u003cVALUE\u003e'. Supported values: 'on'.`\n\n`adConfig()` argument validation errors:\n\n- `Invalid ad config: \u003cERROR\u003e.` Where `\u003cERROR\u003e` can be:\n - `preloadAdBreaks must be one of ['auto', 'on']`\n - `sound must be one of ['on', 'off']`\n - `onReady` must be a function\n\n`adBreak()` argument validation errors:\n\n- `Invalid placement config: \u003cERROR\u003e`. Where `\u003cERROR\u003e` can be:\n - `missing required properties \u003cLIST OF PROPERTIES\u003e`\n - `\u003cCALLBACK NAME\u003e must be a function`\n - `\u003cPROPERTY NAME\u003e must be one of \u003cLIST OF VALID VALUES\u003e`\n - `the following properties are not used for the given ad type:\n \u003cLIST OF PROPERTIES\u003e`\n\nRenamed callbacks in `adBreak()` (`beforeBreak`, `afterBreak`, and `adComplete`\nhave been renamed to `beforeAd`, `afterAd` and `adViewed` respectively. They\nstill function in exactly the same way):\n\n- `Placement config: \u003cOLD\u003e has been renamed to \u003cNEW\u003e. Please update your code.`\n- `Invalid placement config: \u003cOLD\u003e has been renamed to \u003cNEW\u003e. Cannot pass both\n fields. Please use \u003cNEW\u003e only.`"]]