05-18-2013 10:10 AM - edited 06-13-2013 10:02 AM
The BlackBerry Plug-in for the Android SDK Tools version 1.5.2 does not support version 22.0 of the Android SDK Tools. We are working on an update that will be available in early June that will support the latest ADT version.
The BlackBerry Plug-in for the Android SDK Tools version 1.6 are now posted and support version 22.0 of the Android SDK Tools!
You can download the CMD tools here: https://developer.blackberry.com/android/tools/
For Eclipse users, you should be able to see the update within Eclipse.
Solved! Go to Solution.
05-21-2013 12:22 PM
According to the Eclipse doc's you can roll back to a previous version:
- Start Eclipse
- Select Help -> About SDK -> Installation Details
- Under the Installation History tab you'll see a list of previously installed versions.
- Select the one you want and pick Revert.
I tried it on my system and it didn't work. It said some of the required files were not found.
At the moment I'm stuck and will have to wait until BlackBerry issue the update.
Hopefully you have better luck than I did.
05-22-2013 02:47 PM
I posted this solution elsewhere and will work as a temporarily fix until we can get a new tools version out:
As a developer myself, I can completely understand your frustration. When you need to get something done and there's no immediate resolution to your problem(s), it can be aggravating. Hopefully this helps.
I'm going to make some assumptions here:
1. You're running OSX 10.8.x
2. You're running the most recent (permitted) version of Java (I believe that's 1.6.0_45, not Java 7)
3. You've updated to ADT v22 (most recent)
The reason why I emphasized the third point, is because Google has modified the locations of a few files/folders that happen to be dependencies of our tools. Because of this, our tooling will be unable to find these dependencies and will emit a message saying the ANDROID_HOME variable is not set (even though this is not the case).
Referencing the release notes of ADT v22, it appears that Google has moved some Android tools from <ANDROID_SDK>/platform-tools, to <ANDROID_SDK>/build-tools/17.0.0. We are currently working to update our references to reflect this change.
As a temporary solution, you can copy all of the files from <ANDROID_SDK>/build-tools/17.0.0 back to <ANDROID_SDK>/platform-tools. This will allow our tools (apk2barVerfifier, apk2bar, etc.) to function as expected. You may need to provide the SDK location directly to the tool, depending how you've got things setup.
apk2bar Sample.apk /Applications/android-sdk-macosx
Let me know if this helps!
05-22-2013 03:36 PM
It should, yep
We're looking for the dependencies (aapt, aidl, etc.) in the <ANDROID_SDK>/platform-tools directory, so as long as you get them back into there then you should be fine.
05-30-2013 04:17 AM
I can confirm that restoring the previous platform-tools directory is a good workaround to solve the issue.
This Android SDK Tools update also broke some other tools, so maybe it is a good idea not to upgrade from version 21 unless all third parties can also prepare an update. However the presented workaround seems to solve everything for now.