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.
03-05-2012 06:40 PM
Anyone know what might be causing this?
03-06-2012 03:24 PM
03-06-2012 04:56 PM
That's definitely not good. Can we reproduce this consistently? If so, would you please log this issue here and we can get our dev team to investigate:
03-07-2012 03:30 PM
We are currently in the process of trying to identify the exact cause of the problem.
So far, all my test cases have not been able to reproduce the problem we are experiencing in the actual application.
We are using RequireJS, jQuery, jQTouch, Google Maps, PhoneGap (not loaded for Playbook), lawnchair and touchSwipe.
I beleived jQTouch to be the most likely cause, but the problem was still occuring after removing it.
I will create an issue in github when we have more information on the problem.
03-08-2012 01:19 PM
After more unsuccessful tests today, I decided to security wipe the playbook and reinstalled the app. After the security wipe was completed and the playbook set up again, I installed the app the usual way. It was working fine. Then I connected to the web inspector using chrome on my computer and tried again. The problem happened. I closed the web inspector and started the app again.. the problem happened... I deleted the app from the playbook... cleared out all my browsing history/content on my computer... installed the app and ran it and it worked fine... I reopened the app and connected using the web inspector and it works fine...
Our app is currently working correctly now... It seems the Web Inspector was causing the issue???
Is there anyway for the Web Inspector to affect the app? even if it is not currently connected to the app?
10-30-2012 07:36 AM
I'm experiencing the same problem with simple HTML SELECT components.
I've never used webinspector to test my app, so I can exclude that it was the cause.
Problems happen randomly:
I click the SELECT A (it contains 3 elements) -> the webworks app stop to run.
I restart the app, I click on the same previous SELECT A and now it works.
Sometimes the problem happens also with empty SELECT.
I've tryed to manage it with try/catch on click event but this doesn't catch anything because formally there's no exception.
When will be fixed?
10-31-2012 08:25 PM
Removing 'on FirstLaunch=true' fixes the problem of popup behind screen which also mimicks the app 'freezing'
takem from thread: