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.
05-09-2012 03:19 AM
05-09-2012 12:59 PM
@twindsor Hi Tim,
I have tested the two simple WebDB versions, both yours and mine, repeatedly. The initial results this morning have been somewhat consistent. Your version does not seem to freeze up, whereas my version freezes every 2nd or 3rd time.
However, once I removed the onFirstLaunch from the config file from MY test version (posted earlier in this thread), it will NOT crash. I have tested it again, and again, and again, and it seems to work.
So, it appears as though you are a genius. Your "long shot" solution looks like it works.
However, we are left with the question, why does it work? I have included that onFirstLaunch in my previous apps without issue until now. What does it do? I thought it simply had to do with the loading screen. Why must it now be left out?
Rest assured that I will pester you again in this thread if this happiness turns out to be short-lived. But in the interim, thank you again for your help.
05-09-2012 01:15 PM
Have you removed the whole loading screen tag, or just the first time attribute?
My hunch was that since there's no actual settings included in the loading screen tag that it's either doing a transparent loading screen or otherwise messing up somehow which looks like a freeze. I think there needs to be some element, ie: background or image to be displayed, even though all the properties are optional.
Just a theory though, I could be completely out to lunch.
05-09-2012 01:19 PM
05-11-2012 11:22 AM
That's really weird. I'll have to look into it further to figure out what is happening. At least you are up and running though and can submit your app.
07-22-2012 10:45 AM
Ouch. My Webworks app has been freezing randomly when displaying select lists. Not finding any solution, I had reached the point where I started to re-implement the lists myself, just to get the app shipped...
Then I stumbled on this thread. Turns out it fixes the problem, for whatever reason.
Since the solution is spread out over multiple pages, to help anyone searching: in Playbook OS 2.0, if your Webworks application freezes (hard lock, requires app quit), take a look for a loadingScreen element in your config.xml. If you have onFirstLaunch="true", try removing it.