apkmanager bugs

Sigh, some days looking at that makes me want to cry, why have I really bothered?

Well, I’m still not sure I should bother with APK Manager anymore, but at this point I’ve wasted so much time on it, I just don’t feel like abandoning it.

Anyway, I’ve pushed some new fixes to github over the past week to try and fix problems that result from having any ‘spaces’ in the path to apkmanager. And just now I pushed still additional changes to patch dex2jar when installing for these same ‘spaces in path’ problems. If you’ve already downloaded and installed dex2jar from inside apkmanager, please delete the apkmanager/other/dex2jar folder, and install it again.

Cheers 🙂

20 thoughts on “apkmanager bugs

  1. Mike Kelly 16 July, 2014 / 12:20

    hi Jocelyn,
    when I double click its icon, I get: “APKManager” is damaged and can’t be opened. You should move it to the Trash.
    running Maverick on a macbook pro. I really need to decompile the manifest.xml document from my APK file built with Corona SDK to let it know its tablet compatible as well. THANKS for this app!

    • jocelynmallon 16 July, 2014 / 12:34

      Hi and thanks for the message. I’m out of the house for a few hours, but I’ll look into this when I get home.

    • jocelynmallon 17 July, 2014 / 20:54

      Hi again,

      Sorry for taking so long to get back to you, but I can’t replicate the problem on my end. Maybe try trashing the APKManager folder/repo and cloning the repo again from github.

      • Mike Kelly 18 July, 2014 / 08:17

        no worries, Joyce…

        so I installed the 3.0 Beta version today. after which, I get from your terminal:

        Last login: Fri Jul 18 09:29:18 on ttys004
        Michael-Kellys-MacBook-Pro-3:~ mikelly321$ git clone git://github.com/jocelynmallon/apkmanager.git
        2014-07-18 11:09:59.812 xcodebuild[2145:d07] [MT] PluginLoading: Required plug-in compatibility UUID 37B30044-3B14-46BA-ABAA-F01000C27B63 for plug-in at path ‘~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/Unity4XC.xcplugin’ not present in DVTPlugInCompatibilityUUIDs
        2014-07-18 11:09:59.813 xcodebuild[2145:d07] Failed to load plugin at: /Users/mikelly321/Library/Application Support/Developer/Shared/Xcode/Plug-ins/Unity4XC.xcplugin, skipping. Reason for failure: *** -[__NSPlaceholderDictionary initWithObjects:forKeys:count:]: attempt to insert nil object from objects[0]
        Cloning into ‘apkmanager’…
        remote: Reusing existing pack: 551, done.
        remote: Total 551 (delta 0), reused 0 (delta 0)
        Receiving objects: 100% (551/551), 17.21 MiB | 3.95 MiB/s, done.
        Resolving deltas: 100% (308/308), done.
        Checking connectivity… done
        Michael-Kellys-MacBook-Pro-3:~ mikelly321$

        but when I double click the app icon, I still get:

        “APKManager” is damaged and can’t be opened. You should move it to the Trash.
        Safari downloaded this file today at 11:05 AM from github.com

        yikes. thanks!

      • jocelynmallon 18 July, 2014 / 08:26

        Hi again,

        All of the Xcode errors seem to be unrelated to APK Manager, but the result of missing Xcode plugins. I don’t really know why or how to fix those, maybe try reinstalling xcode from the app store?

        It does seem like the apkmanager repo cloned successfully though regardless of those Xcode errors.

        The only other thing I see is that there shouldn’t be any kind of Safari message attached to the APKManager.app after cloning the repo, the system shouldn’t even see the file as having been ‘downloaded’ from anywhere.

        Honestly I’m not really sure what’s going on, and I haven’t really been doing any android hacking lately, so it could be a bug somewhere, but again, I can’t replicate these errors on my end 😦

      • Mike Kelly 18 July, 2014 / 08:42

        I went through the github app. looked good until I got:
        ERROR: Corrupt download/file, md5 hash fail:
        download: cfa995a8dafe31f2696b839e411af42e
        expected: 9780aeca7928aaba3e18cd89d29fbe31

  2. Mike Kelly 18 July, 2014 / 08:48

    I didn’t realize where the clone was, and so the Safari error was because I was trying to open the original download. so the a-op opens now but I do get the error above. will installing Homebrew help?

    • jocelynmallon 18 July, 2014 / 08:49

      Hey again,

      Yeah, sorry, with 3.0+ homebrew is pretty much required. If I continue any kind of work on APK Manager I’ll likely make it the only option, since trying to compile my own binaries and stay up to date is a huge time sync.

      • Mike Kelly 18 July, 2014 / 09:02

        Homebrew seems to be doing the trick, but I’m not sure how much of the Android Tools I need to install. for example, do you know if I need Android L or Android 4.4W (API20)?

      • jocelynmallon 18 July, 2014 / 09:05

        Hey again,

        I wouldn’t bother with any of the Android L, Android Wear or glass stuff. Just install the basic 4.4.X platform tools, build tools, etc. (I think 4.4.4 is the latest?)

  3. Mike Kelly 18 July, 2014 / 11:47

    progress update. works like a freaking charm!!! decompiled my AndroidManifest.xml file like John Ramensky (aka Gentle Johnny) could crack a safe. my Corona SDK compiles the Manifest file using build settings, but Google Play wasn’t recognizing that I included scree support for large and large screens and so it was classifying the app for phones. your decompiler verified that: was in place so now I just have to figure out why it’s not being recognized, but at least I know it’s there now and how I could have added it if it weren’t. thanks for this brilliant Mac update of the APK Manager, Jocelyn!

    btw, a slow (all typewritten) but sure video tutorial (PC) on how to use the original APK Manager resides at: https://www.youtube.com/watch?v=NuavNsIaErE in case any of your other fans come across this exchange.

    it was easy to adapt to yours from it!

    p.s., I hope you were finally able to purchase your dream Mac Machine…

    • jocelynmallon 18 July, 2014 / 16:29

      > p.s., I hope you were finally able to purchase your dream Mac Machine…

      Almost there. I just need a GPU now, and sadly the AMD 290/290X aren’t readily supported by OSX yet (coming with Yosemite supposedly) so it’s really between a GTX 780 and 780 Ti, and I can’t afford either 😦

  4. Mike Kelly 18 July, 2014 / 11:48

    looks like it eliminated the supports-screen code I had pasted in, but you get the point I’m sure.

    • jocelynmallon 18 July, 2014 / 16:28

      Hey again,

      I’m glad you finally got it working. I suppose I should really just learn Objective-C and turn this into a real application.

      Maybe someday. 🙂

      • Mike Kelly 19 July, 2014 / 09:35

        hi Jocelyn,
        I guess I spoke too soon. I was able to decompile yesterday, no worries, but today I tried to actually change the AndroidManifest with xCode, save it and compile it again, using steps 11 initially and 14 finally. the resulting APK file is less than half the size of the original, and when I copy it to my tablet’s APK folder using Android File Transfer, it won’t install.
        am I missing a step?
        oh by the way, my app includes an obb file… I don’t know if there’s a reattachment issue there or not.
        sorry. thanks again!
        Mike

      • jocelynmallon 19 July, 2014 / 09:40

        Hey,

        At this point you’re probably beyond my scope of knowledge when it comes to android programming (ironically I don’t know anything about it) so it’s possible there’s some kind of bug. It’s also possible that it’s an error in the version of apktool.jar used by APKManager. I haven’t really kept up to date on that, so I don’t know if it has problems with tablet apps.

        The size issue isn’t always a problem, usually it just means that a higher compression level was used by APKManager than the original compiler. Just open the APK file with a zip tool (e.g. betterzip) and see if all the files are there, if so, it should work. If it doesn’t, you can try setting the compression level to 0 (uncompressed) and try again.

        I’ll try and look into any newer versions of apktool sometime this weekend.

  5. Mike Kelly 19 July, 2014 / 10:05

    I set the compression to 0; it still comes out to 3.9MB instead of 8.2MB. I downloaded the betterzip app you suggested (pretty cool app!!), and the two APK’s were pretty much identical except there’s a folder in the original called META-INF which includes three files: MANIFEST.MF, MYKEY.DSA, and MYKEY.SF altogether weighing in at 37KB, that isn’t in the other.

    • jocelynmallon 19 July, 2014 / 10:06

      Hi again,

      The META-INF folder is the signature, so without that your APK shouldn’t install. You either need to copy that over manually (APK Manager should ask you to do it, but maybe that’s broken) or re-sign the APK.

      • Mike Kelly 19 July, 2014 / 10:13

        I used betterzip to copy the folder, and then re-zipped (uncompressed) and renamed. still a no go.

  6. Mike Kelly 19 July, 2014 / 10:06

    trust me; Android programming is not my thing either. at this point, I’m mostly truing to change to this: android:launchMode=”standard” because I’m having issues with the app opening up automatically after download.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s