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-12-2011 10:33 PM
I get the same issue. All my libraries are built from 4.5 up and I am getting that error.
The exception is one library that I am currently working on. Guess I can be happy about that since, as stated, it's the one I'm currently working on.
01-12-2011 10:53 PM
They also appear to have removed the creative hack that actually let us close the the BlackBerry Simulator when using 64-bit Windows. This could get *extremely* annoying.
(The simulator itself deadlocks on shutdown, its a well known bug that RIM's simulator team apparently has absolutely no intention of ever fixing. The Eclipse plug-in team apparently got as annoyed as we are, and implemented a creative hack inside their plug-in so we can kill the similator normally when running through Eclipse.)
Oh, and that welcome web page that the plugin is supposed to display? Its completely broken and throws up an MSIE debugging dialog.
01-12-2011 11:08 PM
The web page issue might just be on their side (though I close it anyway since I don't need it).
As for the "closing the sim on x64". I don't have that issue. They did resolve that issue in the last plugin, if you read the release notes they tell you if you encounter the "can't close sim, running x64" issue. what to do.
01-12-2011 11:12 PM
Okay, I see the note in there about FledgeHook.exe. I guess they were just launching it automatically in the v1.1.x plugin.
But the packaging error mentioned above is a serious showstopper for me.
01-12-2011 11:56 PM
Definitly. My sims went into a compile loop (tries to compile, can't so sim never starts. I try to start sim, it tries to compile, can't so sim never starts. I ...)
I'll look into it to see if I can come up with a temporary workaround.
01-13-2011 06:40 AM - edited 01-13-2011 06:41 AM
I found the following issues:
1) The update site does not include the OS X version
2) The OSX version is intel-only, yet the installer requires Rosetta (PPC emulator) because it uses an ancient version of Install Anywhere. The IA installer doesn't seem to do anything except extracting a ZIP file. So I need to install Rosetta and run a messy installer just to unpack a ZIP.
3) The Eclipse version seems to be customized, e.g. it's called 'Blackberry Eclipse plug-in" instead of Eclipse. It also uses a non-default theme (squared tabs instead of the default rounded ones)
4) It throws StackOverflowError's and crashes.
Please provide an update site that installs the OSX plugin and only that.
01-13-2011 08:26 AM
@mbasheerk: The "Full installer" comes with Eclipse, the plugin, and 6.0. The other component packs need to be installed from the update site.
01-13-2011 10:31 AM - edited 01-13-2011 10:38 AM
jprofitt: "Does anyone know what the requirements are for the "Version" attribute in the Application Descriptor now? I used to be able to append info to designate beta builds (b1, b2, etc) but it complains about that now."
I am having the same error with the Version attribute, mine is set to:
01-13-2011 11:14 AM