Stay organized with collections
Save and categorize content based on your preferences.
Developer tools, such as Chrome DevTools
help Google Meet add-on developers debug and test an
add-on in Google Meet.
DevTools API
You can interact with the Meet add-on DevTools by
navigating to the console in Meet and entering
devtools.meet.addons.
This provides you with methods that you can use.
devtools.meet.addons.suppressHeartbeatTimeout
By default, heart-beating is enforced for an add-on.
However, while debugging you may want to suppress heart-beating so that the
Meet add-on doesn't keep timing out.
To do this, call the DevTools method suppressHeartbeatTimeout:
devtools.meet.addons.suppressHeartbeatTimeout();
devtools.meet.addons.setHeartbeatTimeout
Every page should instantiate a Meet add-on session
and complete navigation within 10 seconds. If you would like to modify this
timeout while testing you can set it here:
devtools.meet.addons.setHeartbeatTimeout(100);// Timeout in milliseconds.
devtools.meet.addons.resetHeartbeatTimeout
To reset any changes made to heart-beating in the same session you can use the
reset method:
devtools.meet.addons.resetHeartbeatTimeout();
devtools.meet.addons.setDarkMode
If you want to test how your add-ons look with their dark-mode
icon, you can set dark-mode for Meet with this method:
devtools.meet.addons.setDarkMode(true);
To set it back to normal in the same session, set it back to false:
[[["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-28 UTC."],[],[],null,["# Manage developer tools for Meet add-ons\n\nDeveloper tools, such as [Chrome DevTools](https://developer.chrome.com/docs/devtools)\nhelp Google Meet add-on developers debug and test an\nadd-on in Google Meet.\n\nDevTools API\n------------\n\nYou can interact with the Meet add-on DevTools by\nnavigating to the console in Meet and entering\n`devtools.meet.addons`.\nThis provides you with methods that you can use.\n\n### devtools.meet.addons.suppressHeartbeatTimeout\n\nBy default, heart-beating is enforced for an add-on.\nHowever, while debugging you may want to suppress heart-beating so that the\nMeet add-on doesn't keep timing out.\nTo do this, call the DevTools method `suppressHeartbeatTimeout`: \n\n devtools.meet.addons.suppressHeartbeatTimeout();\n\n### devtools.meet.addons.setHeartbeatTimeout\n\nEvery page should instantiate a Meet add-on session\nand complete navigation within 10 seconds. If you would like to modify this\ntimeout while testing you can set it here: \n\n devtools.meet.addons.setHeartbeatTimeout(100); // Timeout in milliseconds.\n\n### devtools.meet.addons.resetHeartbeatTimeout\n\nTo reset any changes made to heart-beating in the same session you can use the\nreset method: \n\n devtools.meet.addons.resetHeartbeatTimeout();\n\n### devtools.meet.addons.setDarkMode\n\nIf you want to test how your add-ons look with their dark-mode\nicon, you can set dark-mode for Meet with this method: \n\n devtools.meet.addons.setDarkMode(true);\n\nTo set it back to normal in the same session, set it back to false: \n\n devtools.meet.addons.setDarkMode(false);\n\nRelated topics\n--------------\n\n- [Deploy a Meet add-on](/workspace/meet/add-ons/guides/deploy-add-on)\n- [Best practices](/workspace/meet/add-ons/guides/best-practices)\n- [Add-on types](/apps-script/add-ons/concepts/types)"]]