05-17-2013 07:14 PM
I'm sorry, but I'm getting pretty fed up with the way BB is NOT handling their community support. I'm still awaiting reply from 2 or more threads. If you don't support us, then you'll just keep getting **bleep**, half-working, half-untested apps in your ecosystem. But then again, you're probably already used to that so I see why you wouldn't care.
Having said that, the most basic tool to convert my Android app from Eclipse (apk2bar) is failing on my Mac.
No matter what I try, new eclipse, new android sdk, standalone sdk, standalone tools, new BB10 plugin, setting environment variables on /etc/launchd.conf, .bashrc, .bash_profile, $PATH, $ANDROID_HOME, $ANDROID_SDK, move sdk to new folder, re-set folder paths, and any other tips others have provided do *NOT* work on my Mac Air.
I have even edited apk2bar file (inside the .../eclipse/plugins/net.rim.ajde_18.104.22.168302260701/b
[ERROR] Invalid %ANDROID_HOME% path: /Users/dritan/android-sdk-macosx/
Obviously the SDK path is set under Eclipse but it makes *absolutely no difference* to the bb plugin whether you put a real SDK path there or oranges. The only way to get apk2bar to recognize Android SDK is to export the environment variable under "...eclipse/plugins/net.rim.ajde_22.214.171.124302260701/bl
I'd like to have a word with the makers of these tools and API engineers. Why does BB carry the word "incompetent" when talking across other developers about this new-gen platform? I'd like to see this platform thrive and succeed (because the devices aren't half-bad) however we are being hindered by the development process.
The way I see it, there are 2 options:
1. Remove APK to BAR functionality entirely and be done with the BS that all Android devs are facing
2. Support the conversion full on.
Right now I'm stuck on a plethora of APK to BAR problems, from API calls returning different values between Z10 and Q10 to the tools of development.
A disgruntled fed up developer wishing he didn't have to deal with this **bleep** the WHOLE EFFIN DAY
Solved! Go to Solution.
05-21-2013 12:08 PM
Agree that lack of support on this site is an issue. I think Blackberry should really be getting more involved with devs as BB10 is so critical for success of the company and Apps are a huge part of that. I will say though that if you can connect with some Blackberry devs or dev relations folks (twitter, email, messages through forums) that they can be really helpful. They helped me out with a few things over the past couple of months. But it takes a while to build those connections.
Anyway on my Mac if I'm using command line tools for testing/debuging I use:
and then I use that same terminal window for apk2bar and such. Seems to work (for me anyway).
For releases I just build using Eclipse (although still use command line to install on device).
Also for apk2bar I specify a debug token (which I generated some how):
./apk2bar ~/Desktop/MyApp_bb.apk -d z10_debug_token.bar
Hope that helps.
05-22-2013 04:46 AM
I *believe* the problem is with apk2bar not understanding the Android SDK v17 file layout. I could apk2bar yesterday with v16 just fine, but upgraded today to v17, and presto... no workie.
v17 changed the file locations, and apk2bar seems confused. See http://supportforums.blackberry.com/t5/Android-Run
05-22-2013 10:56 AM
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 12:12 PM
Thank you for your reply fix! I'm sorry I was pretty agravated that day and was searching everywhere but found no answers. I've re-constructed my thought process to be less agitated about posts and do nothing but wait.
06-03-2013 05:14 PM
Yes, we're all in the same boat trying to keep up with ever-changing APIs and SDKs.
I would recommend doing the following:
This will cleanly reference the SDK without having to remember to copy those files over if something changes in the future.
06-13-2013 10:07 AM
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/
Or for Eclipse, you should be able to see the update now.