# Decrypting traffic using Charles Proxy

**URL:** <https://community.amazondeveloper.com/t/decrypting-traffic-using-charles-proxy/6149>\
**Category:** Q&A\
**Tags:** appstore-fire-device\
**Created:** [August 20, 2024, 1:58pm UTC](https://community.amazondeveloper.com/t/decrypting-traffic-using-charles-proxy/6149 "2024-08-20T13:58:23Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![qiyin](https://avatars.discourse-cdn.com/v4/letter/q/edb3f5/32.png) [@qiyin](https://community.amazondeveloper.com/u/qiyin)\
**Post date:** [August 20, 2024, 1:58pm UTC](https://community.amazondeveloper.com/t/decrypting-traffic-using-charles-proxy/6149/1 "2024-08-20T13:58:23Z")

</div>

Hi I’m working as FAST channel integration developer,

Currently I’m trying to Decrypting traffic using Charles Proxy for fireTVstick 4k,

OS version 6.7

in Dev mode, I did the following article([Network Proxy (Developer Tools on Fire TV](https://developer.amazon.com/docs/fire-tv/network-proxy.html)) step by step.

I could run the commands without any problem, but after running the command:

```auto
 adb shell am start -a "android.intent.action.VIEW" -d "file:///storage/emulated/0/Download/charles-ssl-proxying-certificate.pem" -t "application/x-x509-ca-cert"

```

The **step 4** is correctly done ( Provide a friendly name and ensure that **VPN and apps** is selected under **Credential use**.)

But at the **step 5** ( 1. Press **OK** to install the certificate. You will be asked to authenticate with your Amazon credentials and an onscreen notification will confirm success.) this is where the issue is happening. At this Step, there is a modal for verifying the credentials, but after accepting the modal, there is another message showing below saying **“the certificate is not installed”** , I’ve already done it many times and even reset the device from factory. I do not understand what is happening.

This issue is a big roadblock on developing quality FAST channels for the Firetv fire stick, if somebody could provide a little clarity on this I’d be very thankful.

Thank you whoever read this 🙂

---

<div class="post-metadata">

**Author:** ![Levon](https://dhm3gbtzu79o6.cloudfront.net/user_avatar/community.amazondeveloper.com/levon/32/74_2.png) [@Levon](https://community.amazondeveloper.com/u/Levon)\
**Post date:** [August 23, 2024, 5:04pm UTC](https://community.amazondeveloper.com/t/decrypting-traffic-using-charles-proxy/6149/4 "2024-08-23T17:04:45Z")

</div>

Hi qiyin,

Thanks for posting! I asked the relevant team to investigate.

---

<div class="post-metadata">

**Author:** ![qiyin](https://avatars.discourse-cdn.com/v4/letter/q/edb3f5/32.png) [@qiyin](https://community.amazondeveloper.com/u/qiyin)\
**Post date:** [August 23, 2024, 5:18pm UTC](https://community.amazondeveloper.com/t/decrypting-traffic-using-charles-proxy/6149/5 "2024-08-23T17:18:02Z")

</div>

Thank you a lot Levon!

If you need me to provide any files, screenshot or record I can do it for sure,

We are developing channels but first we will need to troubleshooting them with Charles proxy.

Have a good weekend!

Best,

Qiyin.

---

<div class="post-metadata">

**Author:** ![Levon](https://dhm3gbtzu79o6.cloudfront.net/user_avatar/community.amazondeveloper.com/levon/32/74_2.png) [@Levon](https://community.amazondeveloper.com/u/Levon)\
**Post date:** [August 28, 2024, 8:31pm UTC](https://community.amazondeveloper.com/t/decrypting-traffic-using-charles-proxy/6149/6 "2024-08-28T20:31:21Z")

</div>

Thanks Qiyin,

Yes, a screenshot and if possible log files would be super helpful. Thanks!

---

<div class="post-metadata">

**Author:** ![qiyin](https://avatars.discourse-cdn.com/v4/letter/q/edb3f5/32.png) [@qiyin](https://community.amazondeveloper.com/u/qiyin)\
**Post date:** [August 29, 2024, 8:25pm UTC](https://community.amazondeveloper.com/t/decrypting-traffic-using-charles-proxy/6149/7 "2024-08-29T20:25:59Z")

</div>

Hi Levon,

I will leave this here,

repeated the steps I hope this help,

Just a cue trying to build the App maybe the error show at the terminal is a cue:

ERROR: /Users/awg/AndroidStudioProjects/firestick2/app/src/main/res/xml/network\_security\_config.xml:19: AAPT: error: resource raw/charles\_ssl\_proxying\_certificate (aka com.example.firestick2:raw/charles\_ssl\_proxying\_certificate) not found.

[Drive with the videos and captures](https://drive.google.com/drive/folders/1S1OLwBjWd05-NmBLW_6G1qM-OZcMdf6X?usp=sharing)

One more thing to Add, I’m able to see the adb logcat at it’s terminal, but I cannot check the ‘Network tab’ for FireStick.

Thank you a lot!

---

<div class="post-metadata">

**Author:** ![Moses](https://dhm3gbtzu79o6.cloudfront.net/user_avatar/community.amazondeveloper.com/moses/32/524_2.png) [@Moses](https://community.amazondeveloper.com/u/Moses)\
**Post date:** [October 12, 2025, 9:07am UTC](https://community.amazondeveloper.com/t/decrypting-traffic-using-charles-proxy/6149/8 "2025-10-12T09:07:22Z")

</div>

Hi @qiyin ,

Sorry for the late reply here, is this still an issue you’re facing?

Thanks,

Moses

---

<div class="post-metadata">

**Author:** ![qiyin](https://avatars.discourse-cdn.com/v4/letter/q/edb3f5/32.png) [@qiyin](https://community.amazondeveloper.com/u/qiyin)\
**Post date:** [October 13, 2025, 2:46pm UTC](https://community.amazondeveloper.com/t/decrypting-traffic-using-charles-proxy/6149/9 "2025-10-13T14:46:25Z")

</div>

Hi Moses,

Thank you for the response,

Actually no, we gave up on Charles, but we created a middleware for troubleshooting. We are good.

Quick question, do you have (for Amazon Fire TV) any plans on releasing an SDK for Flutter?

Thank you and have a nice day!

---

<div class="post-metadata">

**Author:** ![system](https://dhm3gbtzu79o6.cloudfront.net/user_avatar/community.amazondeveloper.com/system/32/5065_2.png) [@system](https://community.amazondeveloper.com/u/system)\
**Post date:** [October 27, 2025, 2:47pm UTC](https://community.amazondeveloper.com/t/decrypting-traffic-using-charles-proxy/6149/10 "2025-10-27T14:47:16Z")

</div>

Closed on October 27, 2025, 2:47pm UTC

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
