I am going to catch tcp packages by using Charles when developing IOS app, but it failed to catch anything when the app running in the simulator.However everything works well when I using safari or other apps both in or out of the simulator.So it seems that only my app in the simulator has this problem.
I have tried this https://www.charlesproxy.com/documentation/faqs/ssl-proxying-with-ios-9/ ,but it didn't work.
Please do me a favor. Thanks
Well...It seems that Charles is unable to capture tcp package, it is designed to capture http/https traffic instead...
Wireshark may be a good choice BTW.
Related
How can i simulate a slow internet connection for React Native app testing on iOs simulator?
I tried with Chrome Developers tools to change throttle in Network tab as said here: https://stackoverflow.com/a/26313279/1206613, but with no luck.
Also tried this solution, but also no go: http://thisbythem.com/blog/simulating-a-slow-internet-connection-on-osx/
Thanks
Give a try with CharlesProxy, it gives you the possibility of setting the bandwidth for connection using it.
I have an app that should connect to the server using CFReadStreamRef and CFWriteStreamRef. All works great on simulator, but not on real device(tested on 4 watches). And I'm not even have any idea of where to look. Internet works on watch, cause map app works good.
If you have any ideas don't hesitate to share them with me, literally ANY ideas. Thank you.
duplicate: Socket connection from WatchOS 2 and CFStream
it won't work according to Apple Developer straight on the watch but you can do that work on iphone and send over data to watch usign WatchConnectivity Framework
https://forums.developer.apple.com/thread/19399
After I have installed Xcode6/iOS Simulator(iOS8), Charles seems can't capture any requests from iOS Simulator.
and Proxy-> Access Control Setting is clean. All Charles settings weren't be modified after upgraded Xcode6
Anybody has the same trouble ?
I get this problem because I use a proxy in my wifi connection to go though the FXK GFW. In this situation, some requests won't go through charles.
You can check this out.
The problem i have is really anoying. Basically if I put "https://a.domainX.com" in Safari on an iPad 3, I get a message that the server did not respond. But if I put the same URL on Opera in the tablet, the page get's displayed correctly.
Also if I put a PROXY between the iPad and the server, the page get's displayed correctly. My current guess is that the Safari browser cannot resolve the domain correctly or there is some problem with the SSL certificate, but only on Safari.
Chrome has the same behavior that Safari, and I presume sinche both browsers are implemented based on WebKIT.
Finally, I did monitor the Safari browser from a Macbook, but there is no information there that could be usefull to debug this problem.
Any tips or suggestions would be appreciated.
PD: English is not my native language, so sorry for any mistakes :)
Finally we where able to debug the problem and we had to use a network sniffer to follow the HTTPS connection flow. The problem was that at some point after the latest iOS upgrade the iPad did not work well with the server side encryption algorithms we had defined, and the HTTPS negotiation didn't go all the way through.
Changing the server side to newer algorithms (and disabling the older ones) did the trick and after that all is working ok.
It was quite difficult to manage this, but we where able to replicate this solution:
http://www.cardinalpeak.com/blog/sniffing-ipad-traffic/
Basically it's about putting a computer between the network and the iPad to sniff the network packets. We didn't use a computer tho, we just connected to the communications switch to see the traffic and redirected the port traffic to the one where we had Wireshark installed (http://www.wireshark.org/), but I guess this is not common solution for everyone.
I hope this helps if anyone has the same or similar problem.
I debug my BlackBerry apps on device emulator, using the MDS simulator for access to the web.
Today I ran a Wireshark trace to catch my app's calls. I saw 2 calls made by the MDS simulator before my traffic started, and hope someone can explain them to me.
http://www.blackberry.net/go/mobile/mds/http/mappings.xml
http://www.blackberry.net/go/mobile/mds/http/mappings2prop.xsl
They seem to return some settings possibly for the simulator.
What are these calls for?
I also wonder if these calls are somehow related to the poor performance of the MDS simulator that I deal with regularly - will the MDS simulator continue to work if this server does not respond?
Hope this makes sense to one of the BB experts here - thx.
Well, I have noticed this before, from my opinion i think it's a kind of request for blackberry server to open a port according to the proxy setting. Or it maybe as a log for connections. That is just my opinion I'm not an expert ...