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 ...
Related
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.
Actually i am developing stuff for the iPad, but fiddling with Firebug lite is no fun and is limited.
I would like to remotely control an iPad from my pc or mac - if possible without jail break.
Something like "windows desktop remote connection" to remotly control another OS - but for the iPad.
How can i achieve that?
Update: Why do i get downvotes here? Please clarify!
As far as I know I don't think there is anything available yet. But I just saw a forum with some info about this topic:
http://forums.whirlpool.net.au/archive/1488754
UPDATE
I think you need this
Chrome Extension is Also available
I'm developing a mobile app using Flash Builder 4.6/AIR. I've been able to debug on the device (an iPhone 4s) just fine until now. I connect my iPhone to my mac with the USB corad, and debug.
All of a sudden I'm getting a black screen for close to a minute. Then I see the "Enter ip address or hostname" dialog. If I enter the ip address of my machine it doesn't matter. The window goes away for about 15 seconds, then comes back. Meanwhile, Flash Builder on my mac times out. The only way I can actually see the program running is if I hit 'Cancel' on that dialog. The app then launches, but I cannot set any breakpoints, cannot debug.
Everything I've found on the internet around this issue mentions it in reference to AIR for android -- not iOs. But I'm seeing it with iOs.
Anyone know what's going on here?
Thanks.
To make it easier for future readers, the official answer to this issue;
With the current (official) version of the AIR SKD (3.2) USB debugging is not supported on iOS devices. This is going to change with the future 3.3 release which (amongst others) adds USB debugging support:
"USB debugging for AIR iOS
This new feature allows the iOS developer to connect to the desktop via USB while debugging their mobile applications instead of relying on network connectivity."
With version 3.2, iOS debugging works over the local network, so both devices (the machine the debugger runs on and the iOS device) have to be in the same network so that they can communicate with each other.
See also the reply to What is the address of my Flash debugger?, it really helped me to resolve similar issue. Using 'ios-debug' mode was the way to go.
If you still have this problem using Android with the device connected to same wifi, try checking firewall rules. In my case FlashDevelop was blocked and I didn't suspected because of updates worked perfectly.
Bit of a hardware question here. I am developing iPad applications for a client and am finding that when I send over beta versions for the client to test, he is finding many more crashes on his devices than I am seeing. A lot of these crashes are 'low memory crashes' which I simply am not seeing/able to reproduce.
Am wondering what differences between the 2 devices there may be so that we can work out if it is a hardware issue. Any ideas?
Make sure of the client's configuration/environment matches your environment. Eg: Outlook Exchange Sync, MobileMe sync. In my Contacts application these caused a lot of crashes because of these.
If possible add more logs and get the logs from console of the client device and verify.
Possibly your client has more stuff running at the same time. Or your own app is background-enabled and is getting killed from time to time...
Always test your own code with the Simulator - it has a feature that allows you to simulate low memory warnings.
Has anybody got the BB simulator and MDS simulator to work?
I have the MDS installed and 4 BB phone sim's. For some reason, when I first install the BB sim it might work and then it will stop working.
Has anybody had this issue and know how to fix it?
The first time I used both, BlackBerry JDE 6.0.0 and its version of MDS-CS, it worked very well. After a couple of simulator reloads to test a Browser-Push application, the 9800 simulator stopped connecting with the Mobile Device Service Simulator. All rules are important, but in my case, rule #3 allowed me to connect the simulator's internet browser after deactivating the WiFi connection
MDS should be running before you start the simulator; and it listens on port 8080, so make sure nothing else is listening on that port before you start it.
The simulator seems to pick up the MDS location from the rimpublic.property file (under MDS/config), which is part of the MDS install, and rimpublic.property needs to have the machine's fully qualified host name in it, not localhost.
If you've started your simulator without the MDS running, you will need to remove the .dmp files in [installroot]/[phonemodel]. This problem often happens with BlackBerry JDE version 6.0.0.
These rules seem to have work for me so far.
Well, there are several common mistakes when using MDS simulator with BlackBerry Simulator.
If you're opening network http connections you need to add "deviceside=false" parameter to your urls
In case you're behind proxy, you have to add several configuration parameters to enable MDS Simulator check them out here
I just spent 2 days trying various of the tips online about MDS (and there are many) but none helped me.
For me, the solution was to turn off network registration upon simulator launch in eclipse.
Edit: this has helped in some situations, but MDS still not always stable.
(posted in case someone with my problem googles to this page)