Debugging on a Chrome OS device

While developing an application for Chrome OS, you may find issues that you need to debug on a Chrome OS device. You can use the Unity ProfilerA window that helps you to optimize your game. It shows how much time is spent in the various areas of your game. For example, it can report the percentage of time spent rendering, animating, or in your game logic. More info
See in Glossary and Managed Debuggers to profile and debug applications respectively on Chrome OS devices.

Chrome OS has networkingThe Unity system that enables multiplayer gaming across a computer network. More info
See in Glossary restrictions which mean the Unity Profiler and Managed Debuggers can’t automatically connect to Chrome OS devices wireless or through USB connections. Instead, manually connect to the device wirelessly using its IP address. To do this:

• For the Profiler, see Profiling your application.
• For Managed Debuggers, see Android Debug Bridge for Chrome OS devices.

Android Debug Bridge for Chrome OS devices

To wirelessly connect ADBAn Android Debug Bridge (ADB). You can use an ADB to deploy an Android package (APK) manually after building. More info
See in Glossary to a Chrome OS device, you first need the device’s IP address and port. To find this:

1. Open the Settings app and select Network in the sidebar.
2. Select the active network interface.
3. If the device uses a wired connection, the IP address and port is visible in the window. If the device uses a wireless connection, select the SSID the device is connected to. In the details, you can see the IP address.

The steps to connect ADB to a Chrome OS device using an IP address are the same as for Android. To do this, see Connect to a device over Wi-Fi (Android 11+) and use the IP address you acquired above.

Note: If your device or host machine goes to sleep or loses network connectivity you may need to reconnect.