08-23-2012 02:44 PM
Hi! I'm new to BB development and the whole RIM's deploy system. I have already uploaded a free demo of mine and now I'm trying to have a game accepted.
I recieved an email that my game doesn't even start. When I run the game from inside the eclipse IDE I don't have that problem, but when I export it I have the same problem on my PlayBook on the other hand if I just install the bar file created by the eclipse IDE during running the game and not the one exported there is no problem.
Do I understand correctly that the one exported is signed with a certificate and the other one isn't? If so do I have to get a different certificate for each application and for each version I want to upload on the market?
08-24-2012 12:58 AM
you do not need a kex for every application.
i think the problem is the release build configuration. have you checked if everything is included (right mouse click on your project -> C/C++ Build -> Settings -> you can change the current config with the drop down menu configuration).
if everything is fine with the configuration build the project and check your sigining settings:
Preferences -> Blackberry -> Signing
check the value under: RIM Signing Authority ... should be yes -> else signing is not enabled
check the value under: Developer Certificate ... should be your name and a path
you can find more information here:
08-24-2012 12:58 PM
I went over the signing steps again and have checked that under RIM Signing Authority there is a yes and also for the developer certificate has my name but still cannot run my game after installing it on the PlayBook.
I don't even see the splash screen.
08-24-2012 01:14 PM
If you are able to install your signed app on your PlayBook and it just does not start I don't think this is 'signing' issue.
Does Export->Release run fine for this app?
09-05-2012 10:24 AM - edited 09-05-2012 10:29 AM
were you able to figure out what was the problem?
As it was mentioned by BGmot, since you were able to deploy your app to the device, it seems to me that this is iikely not an signing issue.
If you still have issues of lanuching this app from your device, can u try to find the log for your app from the device?
we can see if it will give us more clues.
09-05-2012 10:51 AM
09-05-2012 03:12 PM
according to this KB
The resource files installed together with the app shall be read-only. The application code shall not modify them.
You might want to change your design to modify the copy in the working directory?