Debugging app errors

  • App

Console Logs

There might be cases when the app crashed, or exhibited unexpected behavior. If you want to file an issue at https://github.com/postmanlabs/postman-app-support/issues, or email us at help@getpostman.com (if you wish to include confidential data), it might help expedite things if you include the app’s console logs in your report. To access the console logs, follow these steps:

For the Chrome app

  1. Type chrome://flags/#debug-packed-apps in the URL bar in your Chrome browser window
  2. Search for “packed” or try to find the “Enable debugging for packed apps” setting
  3. Enable the setting
  4. Restart Chrome One this is done, you can access the Developer Tools window by right clicking anywhere inside Postman and selecting “inspect element”. You can also go to chrome://inspect/#apps and then click “inspect” just below requester.html, under the Postman heading.

For the Mac / Windows / Linux app

  1. Head to `View` in the application menu, and click on ‘Toggle Dev Tools’.

In the DevTools window, clicking on the top level Console tab should show the app’s debug logs:

Network Calls

For the Chrome app

You can also use the DevTools window to inspect the request and response payloads. If the Interceptor is disabled, switch to the Network tab, and you should see each call as it’s made. Clicking on this will let you view the headers and payloads for the requests and responses:

For the Native app

Head to `View` in the application menu, and click on Show Postman Console or use the keyboard shortcut cmd + alt + c (ctrl + alt + c). Similar to Devtools, every call along with its headers and payloads will be logged to the Postman Console.