Network Traffic Monitor
With Appetize, you can capture, inspect, validate and troubleshoot all network traffic (including any API calls) occurring during your app session for real-time or later analysis.
Note by default, a user needs to be authenticated to view network traffic using the built-in intercept proxy. See App Permissions for more information.
Capture Network Traffic
To allow Appetize to capture all network events, you need to set the proxy of the device to intercept
.
With Query Parameter
Add the proxy
query parameter to your app or embed URL with intercept
as value.
See Query Params Reference for more information.
With JavaScript SDK
Set proxy
to intercept
in the configuration e.g.
See Configuration for more information.
Inspecting Network Traffic
With App Page
The app page provides a simple network log of all the events that took place. You can access this via your app's app link
or by going to your Apps page, selecting the app you want to inspect, and then clicking debug
on the latest build or choosing a specific build you would like to debug.
You can also open the network logs in Chrome DevTools if you are running the app in a Chrome Browser by selecting the Chrome DevTools
button.
Alternatively you can download the HAR file and open it in your favorite Network Monitoring tool.
With JavaScript SDK
You can listen for all network events via our JavaScript SDK. To easily view them in the browser you can print them to the console or you can store it to file for later analysis
See our JavaScript API Reference for more information.
getNetworkInspectorUrl provides a direct URL for opening network logs in Chrome DevTools
Troubleshooting
Certificate Issues
When using Appetize’s Network Intercept Proxy to monitor HTTPS traffic, your app might encounter certificate errors if it uses certificate pinning. To resolve this, you can either:
Remove the certificate pinning from the app uploaded to Appetize, or
Add Appetize's proxy's SHA-256 hash to the list of trusted certificates in the app:
By doing so, the app will trust the proxy’s certificate and allow secure HTTPS traffic monitoring.
If your app uses third-party libraries that also make HTTPS requests, those libraries might not be aware of the SHA-256 hash you add. In such cases, you may need to update the library’s certificate pinning or trust settings as well.
Note:
Last updated