Adobe AIR SDK for BlackBerry PlayBook updated to v1.0.2 bringing minor fixes and additions

It's been a couple of months since we saw the last update to the Adobe AIR SDK for the BlackBerry PlayBook, but it seems that RIM slipped out an update (bringing us to v1.0.2) at the end of May without us noticing. It doesn't appear that there are any dramatic changes or additions, which is likely why RIM didn't send this one out with a bunch of fanfare, but an update is an update nonetheless, and at least we get a change log with it. Read on after the break for a list of additions and fixes, and to download the update, hit the link below. 

For more information/download the Adobe AIR SDK for the BlackBerry PlayBook

Command line tool improvements

• The blackberry-airpackager command line tool now has a -debugToken option to populate the author and author id fields of the .bar file manifest for debugging.

Installer improvements

Various improvements have been made to the installer. The installer now:

• Supports console install mode
• Supports Adobe® Flash Builder® 4.5.1.
• Only asks for the AIR SDK when integrating with Flash Builder 4.0.1.
• Does not copy the Adobe® Flex® SDK when integrating with Flash Builder 4.5.0 or 4.5.1.
• Supports integration with Eclipse when integrating with Flash Builder 4.5.0 or 4.5.1.

Fixed Issues

• The BlackBerry Tablet OS SDK did not integrate with Flash Builder 4.0.1
• The default option in the installer for "Integration with Eclipse" shouldn't have been "Yes".
• The installer asked for integration with Eclipse when you have not integrated with Flash Builder
• When the project had underscores (_) in its name, an invaild ID was generated for the package.
• It was possible to use invalid characters in the device name, causing debug token creation to fail.
• The device list did not refresh after new test devices were added.
• The blackberry-airpackager command line tool did not update the debug host on target.
• Debug Token Request deleted the contents of a folder, when the folder name was specified instead of a .bar file name.
• Changes made to the default debug host IP were not recognized by the targets after you restarted Flash Builder.
• The link to developer documentation in the installer was not clickable.
• The packaging process used an icon in the app.xml file instead of the icon in the blackberry-tablet.xml file.
• Test tablets were not saved until the Preferences dialog box is closed.
• The BlackBerry Tablet OS SDK for AIR installer on Linux® asked for Flash Builder integration even though Flash Builder isn't available on Linux.
• The blackberry-deploy command-lne tool did not print the correct error message after five failed authentication attempts.

Thanks to everyone that sent this in!