as

Settings
Sign out
Notifications
Alexa
Amazon Appstore
AWS
Documentation
Support
Contact Us
My Cases
Get Started
Design and Develop
Publish
Reference
Support

Troubleshoot Network Proxy Issues

This page covers common issues and solutions when working with Network Proxy tool. If you don't find a solution to your specific problem here, post an issue in Developer Forum for additional support.

Network traffic stops logging

Cause: Blocked proxy ports, VS Code or Network Proxy requires a restart, port conflicts exist, or there are issues with port forwarding and device network connections.

Solution:

  1. Check if proxy port is open and not blocked by firewalls.
  2. Restart VS Code and Network Proxy.
  3. Open the command palette:

    Mac: shift + command ⌘ + p

    Linux: Ctrl + Shift + P

  4. Enter Reload Window.
  5. Try using a different port number as there could be a port conflict.
  6. Verify port forwarding setup and device network connection.

HTTPS traffic isn't logged

Cause: SSL option is disabled, SSL certificate issues, or an incorrect proxy configuration.

Solution:

  1. Verify SSL option is enabled in Settings > Enable SSL.
  2. Confirm SSL certificate is automatically generated in assets/raw folder.
  3. Check SSL certificate installation status.
  4. Make sure you have a correct proxy configuration in proxy-config.json file.

    Sample configuration:

    Copied to clipboard.

     {
        "enableSSLProxying": true,
        "caBundleFile": "raw/ca.pem",
        "host": "10.0.2.2",
        "port": 5667,
        "enableCallStack": true
     }
    

Debug session conflict

Cause: React Native supports one debugging session at a time. A conflict occurs when an active debugging session exists and the Capture Call Stack option is enabled.

Solution: You have two options to resolve this conflict:

Option 1: Check and stop any active debugging session:

  1. Start Network Proxy.

    a. In Visual Studio (VS) Code, press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Linux) to open the command palette.

    b. Enter "Network Proxy" and select "Vega: Start Network Proxy".

    c. Wait for Network Proxy to initialize.

  2. Check if there's an active debugging session in VS Code.

    a. If there is an active session, you see the debug controls with an active stop button (red square).

    b. If there isn't an active session, proceed to step 4.

  3. If a session is active, click the stop debugging button to end it.

    Image shows the app attached with VS Code debugging controls with debug icon.
    VS Code debugging controls
  4. Build, install, and launch the app.

Option 2: Disable Capture Call Stack in Network Proxy

  1. Go to Setup Network Proxy setting.

    a. In VS Code, press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Linux) to open the command palette.

    b. Enter "Network Proxy" and select "Vega: Setup Network Proxy".

  2. In the Network Proxy settings window, leave the Capture Call Stack option blank. If the option is marked, uncheck the box.

    Image shows the user interface of Network Proxy settings with blank Capture Call Stack option
    Network Proxy settings
  3. Build, install, and launch the app.


Last updated: Sep 30, 2025