[Android Software/Hacking General [Developers Only]] s0niqu3:
IMPORTANT!

5-11-2012 - v3.0 BETA notes

Some notes about the new v3.0 beta released today.

First, please backup your entire old apk_manager directory before you install/clone the 3.0 git repo. My OCD got the better of me when it came to releasing 3.0, and I ended up trashing my entire git repo/history (from v1.0-2.2.5) and starting a new history when I was ~90% through the 3.0 dev process. Because of that, your old directory will cause problems, DO NOT CLONE/INSTALL 3.0b into your old 1.X/2.X directory.

Second, for those comfortable with the command line that really want to help test APK Manager, there are four 'hidden' menu options in most menus (main menu, debug/settings menu, auto-updates menu, signing menu, clean menu) that turn on a variety of debugging options.

96) turns on 'trace mode' (set -x) for the entire script, once the main loop starts. This will make the script basically unusable for people, please only use this if you can reproduce a bug, and are saving the entire terminal output to submit an issue/error log.

97) turns on 'verbose mode' (set -v) for the entire script, once the main loop starts. This will cause some display issues, but the script will remain mostly usable.

98) turns on 'error mode' (set -e) for the entire script, once the main loop starts. This basically causes the script to exit if any condition/test/command fails. Not really useful on its own, but very useful in combination with option 96 or 97.

99) turns on a very (and I do mean VERY) simple debug information display between main apk manager header and most menus. This shows the current PID, the last exit/return code (Currently non-functional) and the last directory change.

So, if you can reproduce any bugs, please close apk manager, and delete your log.txt. Then open APK Manager again, and on the main menu, choose option 98, then next choose option 96. Then reproduce the bug, and copy/paste the entire terminal output into a log on pastebin.com, gist, etc., and send it to me. And of course, if you feel confident debugging and fixing it yourself, then fork the apkmanager repo, and send me a pull request with your changes.

4-14-2012 IMPORTANT!

An update to the issue below. This has been resolved in version 2.1 of APK Manager, and should not present any issues moving forward. However, because the old user settings and private keys were stored locally, inside the apk_manager directory, in order to save these before upgrading, I've created a migration utility/script, that needs to be run before you upgrade.

The link to this migration utility is in the original post in this thread, and the tool is also included in the APK Manager disk image starting with versions 2.1.1.

To run this tool:

mount the "Migration Utility.dmg"

Copy Migrate.app to your old root apk_manager directory.

Copy Migrate.sh to your old apk_manager/other directory.

From your old root apk_manager directory, run Migrate.app

Verify that the script completed without any errors

OPTIONAL - for those paranoid, you can double check that it worked manually. Execute the following commands in a terminal:

cd $HOME
ls -la | grep .apkmanager
cd .apkmanager
ls -la

4-13-2012 IMPORTANT!

AFFECTS all versions of apk manager prior to v2.1 (forthcoming release as of 4/13/2012.)

If you use any advanced signing functionality, you must backup your existing private key(s) and keystore(s) before upgrading to a new version of APK Manager.

Forthcoming version 2.1 will have a separate, automated, one-time backup & upgrade script to run, and all future versions will have automatic backup of key(s) and keystore(s) built in.

By default they get created and saved in the apk_manager/other/.keystores directory. This is a hidden directory by default. You can do one of several different things to unhide/view this directory, and backup your keystore(s).

I'm outlining one simple method here.

Enable 'show hidden files' in Finder. From a terminal copy and paste the following two lines:

defaults write com.apple.finder AppleShowAllFiles TRUE
killall Finder

Finder will restart after those two lines, browse to your apk_manager/other directory and make sure you see the .keystores folder (it should be dimmed compared to regular folders.)

Copy this folder and all contents somewhere safe (desktop, user home directory, user backup folder, dropbox, etc.)

Proceed with your upgrade (usually just delete the old apk_manager folder and copy over the new one, you might need to manually move project folders, etc. too)

Copy/Paste your saved .keystores directory into your new apk_manager/other folder

Test advanced signing functionality to ensure everything still works.

Once you've verified everything is working, run the following code to turn off viewing all files/folders in finder:

defaults write com.apple.finder AppleShowAllFiles FALSE
killall Finder