With device manual proxy to my Charles IP address, not seeing any traffic or prompt to allow traffic in Charles Proxy. S10 device appears to load all traffic when navigating to various URLs.
Even charlesproxy.com/ssl loads website but doesn't initiate a certificate to download.
All other android devices tested on same setup works fine. Issue seems specific to Samsung S10
So what seemed to have worked for me just now, with my mac (I assume it would be something similar for Windows) I just opened a regular browser, went to chls.pro/ssl and download the certificate file.
From there I sent it to my S10+ and opened it, which then installed it properly.
If you're trying to hook up to Android devices then beware that Google introduced security measures to not allow proxy monitoring in I believe Android 6 or 7. If the other devices you had worked fine on Android then it's probably because you were using an earlier version of Android, or, you had a debug build that allowed for proxy monitoring. I know there's a SO post somewhere that talks about this "pinning" and I know our company does this as well with debug apk's. If neither of those solutions work then it's probably a matter of getting the Charles certificate installed correctly on that phone but without more information it is hard to diagnose. Hope this helps you
Related
I have installed the root certificates on my Mac and trusted it as well.
Set up the manual proxy on Android and iOS with same IP address as the Mac.
On Charles disabled the allow list.
Enable the SSL proxy using *.
I followed all the possible steps but still on both the devices, internet does not work.
Can anybody help me with this? I am totally stuck at this point.
This morning I was able to capture https traffic on the version of Fiddler I had installed. I was prompted about a Fiddler update available. I clicked the "Next time" option. After closing fiddler and reopening a few minutes later the update was automatically installed (v4.6.20172.31233, 64-bit). Following that update, I am not able to take any traces from my iOS device. I am on a work computer capturing https traffic from my iPhone to monitor a mobile app.
It should also be noted that I'm unable to capture any traffic or visit any web pages on my iPhone when going through the IP and port 8888 setup with Fiddler. Seems like all data is blocked (even when I'm not attempting to capture https with a trusted certificate).
I have attempted a few things:
Went through these steps (which I had done months ago to originally setup fiddler), and it didn't resolve the situation: http://docs.telerik.com/fiddler/Configure-Fiddler/Tasks/ConfigureForiOS
I checked my Tools > Options and everything seems to be configured the same as it was previously.
I double, triple and quadruple confirmed that my iPhone's IP Address and port are correctly matching what fiddler shows when I hover the mouse over the "Online" icon. I confirmed that I'm on the same wifi network on both my laptop and iPhone.
I removed the trusted certificate from my iPhone, but could not download a new one because when I go to ipv4.fiddler:8888 the page does not load. "Safari cannot find the page" and neither can Chrome (from my iPhone). FiddlerMachineIP:8888 loads on my laptop browser, but not my iPhone browser. (I didn't post full http:// links on this post because I have a new stack overflow account and it won't let me yet)
I downloaded the certificate plugin for iOS once more.
I reset my Fiddler Root Certificate by selecting Tools > Options > HTTPS tab > Actions > Reset All Certificates.
I attempted step 4 above again, no success
I closed and reopened fiddler multiple times between each step to restart it, but no success.
Restarted my laptop and iPhone (because why not?)
Do you have any suggestions for what else I can try? Any help is much appreciated. The only thing that was changed was the version of Fiddler. After that, I attempted to run through all the steps above. Currently I'm in a situation where I cannot download the certificate to trust on my iPhone. I don't know what is preventing me from doing that step.
Edit: I reinstalled fiddler and went through all the setup pages. It didn't seem to fix the situation. My phone for some reason will not load the page necessary to download the certificate (ipv4.fiddler:8888)
Try checking the certificate's full trust settings at Settings > General > About > Certificate Trust Settings. Make sure the DO_NOT_TRUST_FiddlerRoot is enabled for full trust.
Disable Windows Firewall and try again. I faced the same problem, and it helped.
I'm trying to run some local testing on iDevices but I must be missing something in the setup. I did that before when it all worked, so maybe someone can helpout:
I'm using Fiddler on a windows machine, have all devices set up via proxies and yes it also captures the traffic of the iphone and ipad.
I've got a few localhost vhosts set up, so running
http://mydomain.local
this works swimmingly on the windows phone via proxy to fiddler. but the iphone and ipad just says the server stopped responding.
The firewall is completely turned off and I can see all other traffic from the iDevices, so what could be the issue? Why does the iphone not read the hosts file but the windows phone does?
Almost a year late, but I had the same problem and can confirm that iOS does reserve ".local" to identify Bonjour-accessible devices
If possible just change your domain extension to something else like ".lan" and your requests will go through the Fiddler proxy as expected.
I wanted to use Instagram on my computer, so I decided to use an Android Virtual Device for that task.
I downloaded the Android SDK and the newest apk for instagram for my computer.
Then I created a new AVD and ran it. After it was booted, I installed the instagram apk using adb install instagram.apk.
It installed smoothly and after clicking the app, it started.
Now here's my problem: From there on nothing works.
When I try to login and I press the login button, nothing happens like there would be no internet connection.
Browsers and other apps using an internet connection work just fine, just instagram doesn't work.
How can I fix this?
I think it has something to do that the android Emulator can't really handle a global proxy.
Therefore hostnames get resolved directly to their IP which violates HTTP 1.1 standarts and the request doesn't get send properly.
To fix this, it is needed to change it so the hostname gets send instead of the IP.
You should try creating an AVD with different settings. More RAM and allowing GPU emulation is a good idea. If you insist on using an AVD and you have an appropriate intel CPU then you can make the emulator run much faster by following these steps. They are a bit complicated, but worth it if you want the emulator to run quicker.
I typically try to avoid using the Android emulator while I am developing apps. It has its uses, but it tends to be slow and doesn't have all of the capabilities of actual devices.
As an alternative to using an AVD, I would recommend downloading and installing BlueStacks. BluesStacks was written from the ground up to allow running Android apps on your Windows PC or Mac. I have used it before and it does a great job. Much better than an AVD.
Try visual studio emulator for android. Instagram works on it with enabled and connected wifi. This emulator works better than BlueStacks.
While working with my app that require network access...
The Android 2.2 emulator's network connection stop working...
The net was working properly but after some time it did not respond on emulator,
while it was working f9 on my system...
I have cross checked the net connections and restarted with the emulator(even created a new avd ). But the problem remains same my net is not working on emulator..
I have also checked the connection with F8 key on emulator...
My app manifest net permission is enabled....
Finally After all I have myself found the solution of to the problem:
It's very common problem that must have been faced by most of android developers....
Recently, while developing an Android Application, I was faced with a situation that wasted 2 hours of my time. The issue was simple, my app was not able to access internet from the Android Emulator.
Initially I thought fixing the issue should have been straight forward, but life is not always that simple.
So what was the real issue because of which my app was not able to access internet? There are multiple reasons because of which this issue could occur. Hence, I decided to document my findings so that other could benefit from it.
There are two main symptoms of no internet connection on android emulator.....
**Only your app is not able to access the internet
**None of the apps are able to access the internet
Lets look at what are the reasons behind each of them.
Only your app is not able to access the internet
If only your app is not able to access the internet on the emulator, check if any other apps are able to access the internet or not. For e.g. you could open up the browser application, visit http://news.google.com/. If the page opens up correctly then problem lies in your app itself and its simple to fix.
Basically, your app needs the Permission to access the internet. This can be done by adding the following line just before the end of tag in AndroidManifest.xml file of your application.
Compile and re-install the app in the emulator and try to access the internet from your app. It should work!
What is the use of uses-permission tag:
Android application can request certain permissions so that they can function properly. Some examples of permissions are, get users location, make a call, access the internet etc. App has to explicitly specify this in the AndroidManifest.xml.
When end users install such an app on their device, the android OS will notify the user that, app is requesting certain permissions. If users are fine with that, then only the app will be installed. Else users can deny the permission and the app will not be installed.
This mechanism is Androids way of implementing security and users privacy!
This is the more tricky situation:
None of the apps are able to access the internet
Now this situation is tricky. There are two reasons because of which this could happen
Proxy server is not configured on the emulator
Incorrect DNS used by the emulator
Setting Up the DNS Server:
emulator.exe -avd 'android1.6' -dns-server 8.8.8.8
The android1.6 is your avd name I created an avd with name android1.6
So just replace android1.6 with your avd name.
Run this code in command prompt after setting the path to tools & platform tools of your android sdk