How to Inspect & Collect har logs Android Browser Content Using Chrome DevTools<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Inspecting browser activity on your device can sometimes be tricky. Luckily, Chrome DevTools makes it possible to inspect, debug, and troubleshoot: Browser tabs (not just Chrome, but also Edge and other Chromium-based browsers) This article explains how to set up inspection via USB (preferred method) or Wi-Fi (Wireless Debugging with pairing). Prerequisites Before starting, make sure you have: Google Chrome installed on your desktop/laptop.ADB (Android Debug Bridge) installed on your machine. Download here: ADB Platform Tools After installation, open a terminal/command prompt and type: adb If you see adb command not found (macOS/Linux) or The term 'adb' is not recognized (Windows), then you must: Option 1: Run ADB directly from platform-tools (what you already have) On macOS: cd Library/Android/sdk/platform-tools chmod +x adb ./adb On Windows cd C:\Users\<UserName>\Downloads\platform-tools adb.exe Option 2: Add ADB to PATH: This lets you run adb from anywhere in the terminal without navigating to the folder. On macOS: Open the terminal and edit your shell config file: nano $HOME/.zshrc (use .bashrc if you’re on bash) Add the following lines at the end of the file (update the path if your SDK folder is elsewhere): export PATH=$PATH:~/Library/Android/sdk/platform-tools export ANDROID_HOME=~/Library/Android/sdk export PATH="$HOME/.bin:$PATH" export PATH="~/Library/Android/sdk/platform-tools":$PATH Save and exit (Ctrl + X, then Y, then Enter).Run the config: source ~/.zshrc Check adb in the terminal, run adbTry quitting the terminal and restarting the terminal and try typing in adb see if it works or not. On Windows: Open Settings -> Environment Variables.Under User variables, select Path → click Edit.Add a new entry with the path to platform-tools, for example: C:\Users\<UserName>\AppData\Local\Android\Sdk\platform-tools Open a new Command Prompt or PowerShell and run: adb devices Enable Developer Options on Android ⚠️ Note for Work Profile Users: If your device uses a Work Profile (enterprise setup), complete the Work Profile setup first. After that, enable Developer Options. Go to Settings > About phone.Tap Build number 7 times until you see “You are now a developer!”.Go back to Settings > Developer options.Enable: USB debugging (for USB method)Wireless debugging (for Wi-Fi method) Step 1: Connect Your Android Device Option 1: USB (Preferred) Connect your device via USB cable.When prompted on the phone, allow USB debugging access from your computer. On your computer, run: adb devices Open Chrome on your desktop and go to: chrome://inspect/#devices or edge://inspect/#devices You’ll now see: Browser tabs (for Chrome, Edge, or any Chromium-based browser). Once your entry is visible, click Inspect to start debugging. Option 2: Wi-Fi via Wireless Debugging (If USB Is Not Possible) On your Android device, go to Settings > Developer options > Wireless debugging. Tap Pair device with pairing code. This shows an IP address, port, and a pairing code. On your computer terminal, run: adb pair <device_ip_address>:<port> Enter the pairing code when prompted.Open Chrome desktop and visit: chrome://inspect/#devices or edge://inspect/#devices Step 2: Debugging & Capturing Logs Once your device is visible: In chrome://inspect (or edge://inspect), click Inspect under your app’s browser tab.A DevTools window opens where you can: Inspect DOM elements and CSS.Debug JavaScript in real-time.Monitor network requests.View console logs. Step 3: Exporting Logs When debugging, it’s important to make sure logs aren’t lost during page reloads or when the browser closes. In DevTools, go to the Console or Network tab.Enable "Preserve log" (checkbox at the top of the panel). This ensures logs remain available even if the app reloads. To export logs: In the Network tab, click the download icon (⬇️) at the top of the panel to Export HAR (sanitized).This will save the captured network traffic into a .har file. Share these logs with your support/contact team for troubleshooting. Security & Privacy ⚠️ Note: Chrome/Edge DevTools automatically strip sensitive data such as credentials when exporting HAR files, so logs are safer to share. Additional Notes ✅ Works with Release builds of apps — not just debug builds.✅ Works with Chrome (chrome://inspect) and Edge (edge://inspect).✅ Supports both personal apps and Work Profile apps (if Developer Options are enabled after setup). Helpful Links Remote Debugging with Chrome DevToolsRemote Debugging over Wi-FiADB Platform Tools ✅ That’s it! You can now inspect and debug browser content on Android using Chrome or Edge DevTools, and safely capture and export logs for troubleshooting.