11-03-2011 03:24 PM
Newbie here. I'm finally able to debug on an actual device, 9330 which shows:
6.0 Bundle 2333 (v220.127.116.114, Platform 18.104.22.1688)
I'm writing apps targeting the 5.0 SDK. I assume from the above that the device itself is release 22.214.171.1244, is that correct? So where do I get the specific simulator for it? None of the Curve 9330 last 4 digit simulators match. (I'm trying to eliminate all the "can't find debug file" nonsense! Are there any detailed white papers on proper on-device debugging? Also, I'm trying to use Eclipse.
Thanks in Advance!
Solved! Go to Solution.
11-04-2011 12:40 PM
All available BlackBerry smartphone simulators are available for download here: http://us.blackberry.com/developers/resources/simu
There may not be a simulator release for every version available for download. But we are continously adding more, so you can keep an eye on that page for updates.
12-28-2011 04:21 PM
I've pulled the closest simulator down and can sort of debug the app. However, I am NOT a fan of developing on simulators. I prefer to develop directly on the device (Curve 9330). My attempts at this quickly ran into the problem of NOT being able to display object property values. (I am using Eclipse). Does the BB JDE support on-device debug inspection of objects/properties? (I am NOT interested in system.out.println!). To rephrase the question:
What development environment will allow for on-device debugging that supports breakpoint step through and will display objects/properties? My preference is Eclipse and I need to support 5.0.0. (Is there a URL or white paper on this for us newbies, I can't be the first guy bumping into this?)
Thanks in advance!
01-03-2012 10:16 AM
Both the BlackBerry Java Plug-in for Eclipse and the BlackBerry JDE support this, but they do need a matching BlackBerry smartphone simulator to be installed (which contains the required .debug files).
01-03-2012 11:40 AM
Need a bit more clarification: My Verizon device shows 6.0 Bundle 2333 (v126.96.36.1994, Platform 188.8.131.528). I show only one simulator for Verizon 184.108.40.2061. Are you saying that the 220.127.116.111 simulator would/should work with the v18.104.22.1684 device? (This goes to my earlier comment above about not finding precise simulator versions). I.E Do all 4 simulator version component values need to match the device's in order for device debugging to display objects/properties? Thanks in advance!!
01-03-2012 12:05 PM
The version numbers must match exactly, however the carrier does not have to be the same.
Often simulators are released as "generic", which apply to any carrier with the same version.
That being said, there may not be a simulator available for every version released. We do continue to make more simulators available on our web site.
01-03-2012 12:29 PM
1. If I want to develop an app that will run on 5.0 as a minimum and I want to debug it using a simulator only then I can install/use any 5.0 simulator, correct?
2. If I want to debug the same app on a specific device then I still need to install a simulator with exactly all 4 segments of the version the same as the device's, correct? (It seems a bit odd to install a simulator when I'm not going to use it).
3. Therefore, until a simulator with all 4 segments the same as the device's is available, I can NOT debug on that device, correct?
Thanks for your patience!
01-03-2012 01:28 PM
Correct on all points.
Note that you can see System.out.println statements without a matching simulator. But most other debugging features do require it.