Application not getting deployed on Blackberry simulator

15,039

Solution 1

Copying the .cod files into the simulator's directory (where all the other .cod files are) and restarting the simulator will work.

Probably though you want to automatically deploy from Eclipse. If this isn't working for you, there are a couple of things to check:

Check that the project has been activated for BlackBerry - from the right-click menu for the project, make sure that Activate For BlackBerry is checked.

If that's already checked (as it is by default when you create a new BB project), then sometimes explicitly building the project will do the trick: From the Project menu, choose Build Active BlackBerry Simulation

EDIT: In response to some comments below I thought of something else. The configuration you choose may have something to do with your problems (BlackBerry -> Build Configurations). The configuration in the JDE Plug-in doesn't affect the code generated, but it does affect which projects are activated for BlackBerry. If you switch configurations, your project may become un-activated.
Since it doesn't affect the code, I usually just pick one configuration and stick with it throughout debugging and release.

Solution 2

You might be missing 'jar' in your PATH. If so, the eclipse BB plugin silently fails and your application won't be pushed to your simulator plugin directory. To see this failure within eclipse, choose 'Project > Build Active BlackBerry Simulation'.

If you don't have jar in your path, then you will see:

I/O Error: Cannot run program "jar": CreateProcess error=2, The system cannot find the file specified rapc executed for the project

So, if your JDK is here:

C:\Sun\SDK\jdk\bin

Then append it to your system environment's PATH variable, then re-run 'Build Active BlackBerry Simulation' and you should see:

rapc executed for the project [YOUR PROJECT]

Solution 3

Here are a couple of ideas:

1) If you have any build errors then the application won't deploy to the Simulator. The Eclipse compiler (that underlines compile errors in red) is different to the "rapc" one that creates the binary for the Simulator. I have heard of situations where the Eclipse build seems to work, but the rapc compile fails - check the Console for the detailed rapc output (this might not look like a normal Eclipse build error).

2) In the Eclipse menu, open BlackBerry -> Configure BlackBerry Workspace.

Under BlackBerry JDE choose Code Signing and make sure the three RIM checkboxes are selected. I had compile errors when these weren't selected.

Under BlackBerry JDE choose Installed Components. Choose to use the Component Package 4.7.0 as I have heard of problems with the 4.5.0 Simulator.

You should delete all these extra answers you posted, or you might get downvotes - they should be comments instead of answers.

Solution 4

Check if your simulator is set up to clean the file system / configuration before launching the simulator. Simulators can be set up like this. If you deactivate it, the application should not disappear.

Solution 5

For future readers, there is another possibility for this issue. Check your workbench project directory (folder) for a ProjectName.err file. This may provide a clue as to why your build is silently failing and thus not deploying. In my case, it was an "Error!907", a new icon I added to my project was too big. There was absolutely no other indications in Eclipse 3.4.1 that there was a problem in my build.

Share:
15,039
iOSDev
Author by

iOSDev

Mobile Application Developer by profession

Updated on June 05, 2022

Comments

  • iOSDev
    iOSDev about 2 years

    I am tried deploying .cod,.alx.jar files on blackberry simulator 8100;the application is not getting deployed on phone.I am using Blackberry plugin for Eclipse. How can I solve this issue?

    Please help


    Update

    Hi, Thanks for your reply. I am trying to run the application the way you suggested.

    Do I need to setup new run configuration every time I run any project?

    What should be default value for build configuration ? [Debug,Private,or Release]