04-07-2010 04:03 PM
I installed eclipse with 1.1 pluging. Looks like it works much stable and faster.
When I selected "Debug As"->"Blackberry Device", IDE builds, signs and uploads bionary to device. Cool!
But due to updating app, device resets and IDE fail to debug.
Why plugin fails to wait for reset? Can it be fixed?
Solved! Go to Solution.
04-26-2010 10:25 AM
Are you using version 1.1.0 or 1.1.2? What BlackBerry Java SDK are you using (4.5.0, 5.0.0, etc..)?
04-26-2010 10:56 AM
BlackBerry Java Plug-in 22.214.171.124003212304-12 net.rim.EclipseJDE.feature.group
BlackBerry Java SDK 126.96.36.199 net.rim.ejde.feature.componentpack5.0.0.feature.g
BlackBerry Java SDK 188.8.131.52 net.rim.ejde.feature.componentpack4.6.1.feature.g
Eclipse IDE for Java Developers 184.108.40.20600216-1730 epp.package.java
I used it with the both 4.6 and 5.0 SDKs. The app installing resets device so as it's big (~512 kb), use record store, etc. So as you understand reset is not issue. The problem that I can't connect to device to debug app.
04-26-2010 11:27 AM
Eclipse could be timing out while waiting for the BlackBerry smartphone simulator to restart. You can increase this timeout value by...
1. Open the Window menu in Eclipse and choose Preferences.
2. Expand Java.
3. Click on Debug.
4. Increase the values in the Communication section (Debug timeout and Launch timeout).
5. Click Apply and then OK.
04-26-2010 11:36 AM
I increased default values by 100 to 24000000 msec
The same result: after selecting Run - > Debug As -> BlackBerry Device in abou 12 sec I got the below alert:
04-26-2010 01:55 PM
What BlackBerry Smartphone model and BlackBerry device software version are you testing on? You can find this under Options, About on the BlackBerry Smartphone.
04-28-2010 01:01 PM - edited 05-13-2010 01:39 PM
I have been able to reproduce this and it will apply to BlackBerry device software lower than 5.0. Here is what is actually happening:
Debug As -> BlackBerry Device deploys the application to your BlackBerry Smartphone and the attaches to the debugger. However, replacing the application can cause the device to reset, which disconnects the debugger.
The workaround to this is to uninstall the existing application (Options, Applications) before performing a "Debug As -> BlackBerry Device", which will prevent the reset.
I have passed this issue to our development team for resolution in a future release of the BlackBerry Java Plug-in for Eclipse. It has been logged in the Issue Tracker here: https://www.blackberry.com/jira/browse/TOOL-161