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.
07-06-2012 03:57 AM
If you couldn't reproduce it and it happens only sporadically, I suspect it is most likely a memory problem; the PB might have been low on (graphics) memory.
07-06-2012 04:39 AM
It happens everytime it starts on user's device.
However I think the problem has to do with the user not giving file permissions for the app.
I'm now tryng to find how to detect the app permissions at runtime and display a warning instead of crashing.
Anybody know of the recommended way to do this?
Shouldn't RIM fail the app if it crashes when not given the required permissions?
07-06-2012 04:44 AM
If file permission is he problem, it should be something that you can reproduce.
I don't know to to detect if file permission is turned off. But if a file open fails, you could pop up an alert dialog instead of having the app continue with a null file handle.
07-06-2012 04:51 AM
In that case, you could advise the user to turn on file access permission until you upload a fix that handles the problem gracefully.