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-20-2011 12:55 PM
Guys this is not the solution! The problem is your Flash Builder still refers to old plugins, and because of that it cannot be configured to use new 1.0.1 sdk. I suggest to delete old sdk, and re-install as admin making sure the correct link is created for Flash Buidler to pick up new plugins!
04-20-2011 01:28 PM
elena, you are right !
i tested the solution and there wasn't an error any more. but after some tests, i realized, that the new sdk is not fully integrated in FB -> therefor reinstall everything was the only working solution :-(
04-20-2011 01:41 PM
elena - The right solution is a problem when you cant get flash builder to recognize the 1.0.1 sdk plugin. After uninstalling and reinstalling everything, the 1.0.1 sdk never shows up as a target platform. Only way I can get it to come back is by installing the 0.9.4 sdk and using the solution proposed here to compile with 1.0.1 sdk.
04-20-2011 05:21 PM
Yes, late last night I realised that the Debug Token section on the signing page was not available, so I uninstalled Burrito completely (which took out all the old SDK's), reinstalled burrito, installed SDK 1.0.1 again, then ran Burrito as Administrator to integrate the SDK.