Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
04-30-2013 06:52 PM
Hi, I just received word that my first submitted App did not work on any device - but gave the following error message:
"An error occurred while starting (AppName). The application has been terminated.'
I had thoroughly tested my App and it worked flawlessly for me on multiple simulators. I have read some similar posts on this forum, and I'm wondering if the problem is with code signing. So my question is this: Do I need to sign my App again before every release, or do I only need to sign it only once when at the start? Or might the problem be something else altogether?
Solved! Go to Solution.
04-30-2013 08:58 PM
Agree with RexDoug.
Your messge however suggests to me that you are doing some long processingon the Event thread, for example, connecting to a Server as part of the start up procesing and blocking the UI until you get a response. This sort of thing does not fail in the SImulator, possibly because it runs at LAN connection speeds, so the blockages are always small.
05-01-2013 06:37 PM
Thanks for the feedback.
Actually, my App is very simple - I chose a simple one for the first, so I didn't complicate matters. I''ll try simply re-signing my App and then re-submitting it.