Tanto la aplicación como el dispositivo deben estar registrados en la misma cuenta de desarrollador para que puedas realizar la depuración.
Inicia la app del emisor y transmite al dispositivo Google Cast para cargar la app del receptor web y depurarla. Asegúrate de que el dispositivo del remitente y el del receptor web estén conectados a la misma red.
Existen dos maneras de conectarte a tu dispositivo para la depuración remota:
Inspector de Chrome
En el navegador Chrome, ingresa lo siguiente en el campo de dirección para ir al inspector de Chrome:
chrome://inspect
Aparecerá una lista de los dispositivos compatibles con Cast en esa red.
Haz clic en el vínculo Inspect para seleccionar el dispositivo de la app de Web Receiver que deseas depurar.
Se debería abrir una ventana del inspector, lo que te permitirá depurar de forma remota la app del receptor web.
Directamente al puerto 9222 del dispositivo
En el navegador Chrome, ingresa lo siguiente en el campo de dirección para ir directamente al dispositivo que estás depurando. Esto puede ser más rápido que el Inspector de Chrome si tienes muchos dispositivos en tu red:
<deviceIPaddress>:9222
Para encontrar la dirección IP del dispositivo, selecciónalo en la app de Google Home, ve a la configuración y busca en la sección Información.
Haz clic en el vínculo Remote Debugging de la sesión que deseas depurar para seleccionarla.
Si no se propaga el depurador remoto de Chrome, selecciona el ícono a la izquierda de la barra de direcciones y elige site settings.
Desplázate hasta la parte inferior de la configuración y cambia el parámetro Insecure content a Allow.
En la consola del depurador remoto de Chrome, habilita el registro de depuración. Para ello, ingresa lo siguiente:
Se admite la manipulación completa del DOM, así como la REPL de JavaScript de Chrome (consola), que te permitirá manipular la app del receptor web en ejecución.
Cuando se desmonte tu receptor web (final del ciclo de vida), el depurador se inhabilitará y aparecerá un mensaje de advertencia en la parte superior. En este punto, ya no puedes interactuar con el depurador. Para reiniciar la depuración, debes reiniciar la app del receptor web y, luego, volver a cargar el inspector.
Puntos de interrupción
Puedes agregar puntos de interrupción manuales a tu código con debugger; dentro del código del receptor web.
Almacenamiento en caché local
Usa window.location.reload(true); para realizar una recarga forzada que borre la caché de la aplicación del receptor web.
Cómo conservar registros entre sesiones
Para conservar los registros entre sesiones, haz clic en el ícono de ajustes dentro del depurador y marca la casilla junto a "Preserve log upon navigation".
[null,null,["Última actualización: 2025-07-25 (UTC)"],[[["\u003cp\u003eUse the Chrome Remote Debugger to debug your Cast Web Receiver application by inspecting it through \u003ccode\u003echrome://inspect\u003c/code\u003e or directly accessing the device's 9222 port.\u003c/p\u003e\n"],["\u003cp\u003eTo enable debugging, register your application and Cast device on the Google Cast SDK Developer Console, ensuring both are linked to the same developer account.\u003c/p\u003e\n"],["\u003cp\u003eInitiate a cast session from your sender app to the target Cast device to load the Web Receiver and allow the debugger to connect.\u003c/p\u003e\n"],["\u003cp\u003eLeverage the Chrome Remote Debugger's console for logging, DOM manipulation, and utilizing the JavaScript REPL for interacting with the running Web Receiver app.\u003c/p\u003e\n"],["\u003cp\u003eRemember to disable debug logging in production environments and avoid logging sensitive information.\u003c/p\u003e\n"]]],["To debug a Cast app using Chrome Remote Debugger, first register your app and device on the Google Cast SDK Developer Console. Then, start your sender app and cast to the device to load the Web Receiver app. Connect to the device via `chrome://inspect` or directly using `\u003cdevice IP address\u003e:9222`. Select the Web Receiver session to debug and enable debug logging with `cast.framework.CastReceiverContext.getInstance().setLoggerLevel(cast.framework.LoggerLevel.DEBUG);`. Use `debugger;` for breakpoints and `window.location.reload(true);` to flush the cache. Preserve logs between sessions in the settings.\n"],null,["# Chrome Remote Debugger\n\nUse the Chrome Remote Debugger to debug a Cast application.\n| **Caution:** Leaving the Remote Debugger attached for prolonged periods can exhaust resources on the Web Receiver and result in a failure.\n| **Note:** Second and third generation Chromecast devices running firmware version 1.49 may not be able to debug Cast sessions using the Chrome Remote Debugger. If you are not able to see your app in chrome://inspect, please try another Cast device or use the [Cast Debug Logger](/cast/docs/debugging/cast_debug_logger).\n\nLaunch Chrome Remote Debugger for a particular Google Cast device as follows:\n\nTo debug Cast apps on an Android TV device, see\n[Android TV: Debugging](/cast/docs/android_tv_receiver/debugging#debugging).\n\nTo debug a Web Receiver app on Google Cast devices, do the following:\n\n1. [Register](/cast/docs/registration) your application and Google Cast device\n on the [Google Cast SDK Developer Console](https://cast.google.com/publish).\n\n | **Note:** The device serial number can be found by navigating to the Google Cast SDK Developer Console and casting the tab to your device.\n\n \u003cbr /\u003e\n\n Both the application and device must be registered to the same developer\n account in order for you to perform debugging.\n2. Start your *sender* app and cast to the Google Cast device\n to load the Web Receiver app for debugging. Make sure your sender and Web\n Receiver devices are connected to the same network.\n\n | **Important:** Debugging will not work if the this step is skipped.\n\n \u003cbr /\u003e\n\n3. There are two ways to connect to your device for remote debugging:\n\n 1. Chrome Inspector\n\n 1. In the Chrome browser, enter the following in the address\n field to go to the Chrome inspector:\n\n chrome://inspect\n\n A list of Cast-enabled devices on that network appears.\n 2. Select the device for the Web Receiver app you want to debug by\n clicking its `Inspect` link.\n\n An inspector window should open, enabling you to remotely debug the\n Web Receiver app.\n 2. Directly to the device's 9222 port\n\n 1. In the Chrome browser, enter the following in the address field to\n go to the device you are debugging directly. This may be faster\n than the Chrome Inspector if you have many devices on your network:\n\n \u003cdevice IP address\u003e:9222\n\n The device IP address can be found by selecting the device in the\n Google Home app, going to settings, and looking under the\n Information section.\n 2. Select the session you would like to debug by clicking its\n `Remote Debugging` link.\n\n 3. If the Chrome Remote Debugger does not populate, select the\n icon to the left of the address bar and select `site settings`.\n Scroll to the bottom of the settings and change the setting for\n `Insecure content` to `Allow`.\n\n4. In the Chrome Remote Debugger console, enable debug logging, by entering the\n following:\n\n ```\n cast.framework.CastReceiverContext.getInstance().setLoggerLevel(cast.framework.LoggerLevel.DEBUG);\n ```\n\n \u003cbr /\u003e\n\n | **Warning:** Always disable debug logging for production, and never log any personally identifiable information.\n\n Full DOM manipulation is supported as well as the full Chrome JavaScript\n REPL ([console](/chrome-developer-tools/docs/console)), which will allow you\n to tinker with the running Web Receiver app.\n\n When your Web Receiver is torn down (lifecycle ended), the debugger will\n become inactive with a warning message along the top. At this point you can\n no longer interact with the debugger. To restart debugging, you must restart\n the Web Receiver app and then reload the inspector.\n\nBreakpoints\n-----------\n\nYou can add manual breakpoints to your code by using `debugger;` within your\nWeb Receiver code.\n\nLocal caching\n-------------\n\nUse `window.location.reload(true);` to perform a forced reload that flushes the\ncache of the Web Receiver application.\n\nPreserving logs between sessions\n--------------------------------\n\nYou can preserve the logs between sessions by clicking the gear icon within the\ndebugger and checking the box next to \"Preserve log upon navigation\".\n| **Note:** If you're having problems playing streams on a Cast device, it may be an issue with CORS. Use a publicly available CORS proxy server to test your streams. (Be aware that third-party software referenced here is not controlled by Google. Google cannot guarantee that third-party software will operate as intended. Proceed with caution.)"]]
