Network Payload Capture

Purpose

To let you capture the network transaction sent in and out of the devices in test sessions.

 

To setup Network Payload capture on your local devices

For iOS devices: https://support.kobiton.com/hc/en-us/articles/4950363673357-Network-Payload-Capture-Setup-for-iOS-device (for iOS devices operating on Latest Kobiton platform, you only need to follow step 3, 4, 5 and 6 of the article, on Legacy Kobiton platform, you need to follow all steps).

Important: You need to perform additional setup steps on the Mac mini host as instructed here for iOS devices operating on Kobiton 4.0+ platform (Latest Kobiton).

For Android devices: https://support.kobiton.com/hc/en-us/articles/4874959556749-Network-Payload-Capture-Setup-for-Android-device (for Android devices operating on Latest Kobiton platform, you only need to follow step 3, 4 and 5 in this article, on Legacy Kobiton platform, you need to follow all steps).

 

Show the overview of network requests

In session details, it will show all network requests as (1) that follows the setting To expand/ collapse the overview, click on the icon (2) Expand/ Collapse
network_overview.png


Show the network payload

In Session Details, observe the payloads in the tab Observe Request / Response Payloads
network_payload.png

Setup for this feature

Network Payload Capture requires both physical setup to add a certificate on the device as well as defining settings within the Portal. Please see the following articles for more information on setup:

The following outlines the steps for defining settings within the Portal:

  1. Go into Settings/ Network Capture to pull up the settings form
    setting_network_capture.png 
  2. Input the base-domain that you want to capture the network transactions (i.e all transactions from sub-domains will be captured also)
    setting_domain.png
  3. Click on Advanced to change the data type you want to capture. By default, Application/ json will be captured
    setting_data_type.png 

Supported MIME types

Data/File Types
Application/json MIME type support 'Application/json'
Audio MIME type support 'audio/aac' , 'audio/mpeg', 'audio/webm', 'audio/wav'
Font MIME type support 'font/otf', 'font/ttf', 'font/woff', 'font/woff2'
Image MIME type support 'image/bmp', 'image/gif', 'image/jpeg', 'image/png', 'image/svg+xml', 'image/webp', 'image/tiff'
Text MIME type support 'text/plain', 'text/xml', 'text/css', 'text/csv', 'text/html', 'text/javascript'
Video MIME type support 'video/mpeg', 'video/webm'
Model MIME type support 'model'

 

Known limitations

  • Android support includes versions 9 - 13

  • iOS devices will experience a 30-second to one minute delay as the proxy is being configured.
  • Manual and Appium sessions will be able to capture the network transaction. Espresso and XCUITest sessions are not able to do it for now.

  • If this feature is not enabled on your system, please contact us for more information.  

  • Since we do not support certificate pinning yet, it should be more stable on web and hybrid application. If you want to capture payload for native application, make sure to disable certificate pinning in your app.

Was this article helpful?
0 out of 0 found this helpful