Issue with Vega builds always proxying after setting up with CharlesProxy, whether we want to use with or without the proxy

Vega Open Beta Bug Reports
1

:warning: Before you continue

Before submitting a bug report, please review our troubleshooting documentation at Troubleshoot Issues | Vega Troubleshooting

If you still want to file a bug report, please make sure to fill in all the details below and provide the necessary information.

NOTE: PLEASE ONLY REPORT A SINGLE BUG USING THIS TEMPLATE.
If you’re experiencing multiple issues, please file a separate report for each.

After Vega App is installed running with Proxy, manual steps taken to not run the app without proxy

1. Summary

We have our app running inside a webView, and the first thing the ReactNative wrapper would do is to load the hosted URL.

We also have our proxy setup running with Charles proxy following these steps

The issue for us is, once we install our app running with Charles proxy, with proxyConfig.json. If on a subsequent launches, we wanted to run our app without making use of proxy, we will have to manually delete entire assets/raw folder, rebuild and reinstall the app.

Ask: is there a build flag or programmatic reactNative API, that can be used to turn off connecting to a proxy server. This way devs can decide whether to use proxy or not regardless of whether the app is built with assets/raw proxyConfig.

App Name:
App Link on Amazon Appstore (found through Developer Console → Actions column in App List → View on Amazon.com):

Bug Severity
Select one that applies

  • Impacts operation of app
  • Blocks current development
  • Improvement suggestion
  • Issue with documentation (If selected, please share the doc link and describe the issue)
  • Other

2. Steps to Reproduce

  1. Build and install an app with assets/raw populated with proxyConfig and resources for connecting to Charles proxy
  2. if we do not want to use proxy, we are deleting the assets/raw folder. We then rebuild and reinstall, so the app does not auto connect to the proxy server

3. Observed Behavior

Explain what actually happened, noting any discrepancies or malfunctions.

Once you have assets/raw with proxyConfig. App always tries routing network calls through Charles proxy, whether you want to use the app with proxy or not.

4. Expected Behavior

Describe what you expected the SDK to do under normal operation.

Programmatic APIs or build flags to turn off proxying

4.a Possible Root Cause & Temporary Workaround

Fill out anything you have tried. If you don’t know, N/A is acceptable

We could save the proxyConfig and resources in a separate folder outside of assets/raw. We can then based on build flag, running with proxy would copy over the proxy configs into assets/raw. And if we wanted to run without proxy, we would delete the assets/raw.

6. Environment

Please fill out the fields related to your bug below:

  • SDK Version: Output of kepler --version

  • App State: [Foreground/Background]

  • OS Information
    Please ssh into the device via kepler exec vda shelland copy the output from cat /etc/os-releaseinto the answer section below. Note, if you don’t have a simulator running or device attached kepler exec vda shell will respond with vda: no devices/emulators found

    SDK Version: 0.21.4726**
    App State:** Foreground

3

Hi @dipu,

Welcome to Amazon Developer Community!

Thank you for the detailed bug report on the CharlesProxy configuration issue.

Our team is investigating this issue and will provide an update as soon as we have more information.

Thanks for helping us improve the Vega platform, and for sharing your temporary workaround approach.

Warm regards,
Aishwarya

4

Hi @dipu,

Thank you for reaching out regarding proxy configuration settings.

I’ve investigated your request to disable proxyConfig and proxying network traffic dynamically. After reviewing our current implementation, I can confirm that we currently do not have a feature to modify proxy settings without rebuilding the application.

I understand this limitation creates inconvenience for development workflows. I’ll discuss this request with our team for consideration as a potential feature enhancement.

Best regards,

Takeshi