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.
01-10-2012 09:30 AM
Why do I get this error when I select the bb sdk path in Flash Builder 4.6 Preference?
No permission to execute the blackberry-keytool tool of the BlackBerry Tablet OS SDK 1.1.1 for Adobe AIR
I installed BB SDK inside my Flash Builder 4.6 sdks folder and added it to my sdks. I select it ok. But, I get this error.
More generally speaking. I need to update my existing released playbook app using Flash Builder 4.6. How should it be configured? The release needs to support the current production version on the Blackberry Playbook OS.
01-10-2012 10:52 AM
You should use the 2.0 AIR SDK when using Flash Builder 4.6. Have you tried that?
01-10-2012 11:11 AM
Are you on mac? I don't know why but it may be loosing executable bits on these tools, if you go to sdk/bin
folder and chmod +x * in there it should fix that specific problem