Forked from nstarke/release-android-debuggable.md
Last active
December 16, 2024 03:10
-
-
Save michaelchiew08/c3da612f96202eb48a363d318357b132 to your computer and use it in GitHub Desktop.
Revisions
-
michaelchiew08 revised this gist
Dec 16, 2024 . 1 changed file with 8 additions and 1 deletion.There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode charactersOriginal file line number Diff line number Diff line change @@ -40,16 +40,23 @@ In the `application` xml node, add the following xml attribute: android:debuggable="true" ``` And also change the following xml attribute `android:extractNativeLibs` to `true`: ``` android:extractNativeLibs="true" ``` Now we need to reassemble the application. We do this by running: ``` $ apktool b -o com.mypackge.apk output-dir ``` Finally, we need to resign the APK so that the device will accept it: ``` $ keytool -genkey -v -keystore resign.keystore -alias alias_name -keyalg RSA -keysize 2048 -validity 10000 $ apksigner sign --ks resign.keystore --ks-pass pass:<your_key_password> com.mypackage.apk ``` That's it! You should now be able to transfer the new com.mypackage.apk back to the device and run it. -
nstarke revised this gist
Apr 19, 2016 . 1 changed file with 10 additions and 4 deletions.There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode charactersOriginal file line number Diff line number Diff line change @@ -17,20 +17,20 @@ For this task, we'll need `apktool` ( http://ibotpeaches.github.io/Apktool/ ). you'll need to find the path to the APK to pull it off the device. Run: ``` $ adb shell pm list packages -f -3 ``` Find the package in the list (it should look something like `/data/app/com.mypackage.apk=com.mypackage`), and pull it off the device: ``` $ adb pull /data/app/com.mypackage.apk ``` Next, we need to disassemble the apk using `apktool`: ``` $ apktool d -o output-dir com.mypackage.apk ``` In `output-dir`, find `AndroidManifest.xml` and open it up in the text editor of your choice. @@ -43,7 +43,13 @@ android:debuggable="true" Now we need to reassemble the application. We do this by running: ``` $ apktool b -o com.mypackge.apk output-dir ``` Finally, we need to resign the APK so that the device will accept it: ``` $ keytool -genkey -v -keystore resign.keystore -alias alias_name -keyalg RSA -keysize 2048 -validity 10000 $ jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore resign.keystore com.mypackage.apk alias_name ``` That's it! You should now be able to transfer the new com.mypackage.apk back to the device and run it. -
Apr 19, 2016 .There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode charactersOriginal file line number Diff line number Diff line change @@ -0,0 +1,50 @@ # How to make a Release Android App debuggable Let's say you want to access the application shared preferences in /data/data/com.mypackage. You could try to run `adb shell` and then `run-as com.mypackage` ( or `adb shell run-as com.mypackge ls /data/data/com.mypackage/shared_prefs`), but on a production release app downloaded from an app store you're most likely to see: ``` run-as: Package 'com.mypackage' is not debuggable ``` While ADB's `adb backup` command will pull many of the files from the application's data directory, the files can be inconsistent with what is actually on the device. If you want to see what is actually on the device, you need to make the application debuggable. For this task, we'll need `apktool` ( http://ibotpeaches.github.io/Apktool/ ). Once you have it setup, you'll need to find the path to the APK to pull it off the device. Run: ``` adb shell pm list packages -f -3 ``` Find the package in the list (it should look something like `/data/app/com.mypackage.apk=com.mypackage`), and pull it off the device: ``` adb pull /data/app/com.mypackage.apk ``` Next, we need to disassemble the apk using `apktool`: ``` apktool d -o output-dir com.mypackage.apk ``` In `output-dir`, find `AndroidManifest.xml` and open it up in the text editor of your choice. In the `application` xml node, add the following xml attribute: ``` android:debuggable="true" ``` Now we need to reassemble the application. We do this by running: ``` apktool b -o com.mypackge.apk output-dir ``` That's it! You should now be able to transfer the new com.mypackage.apk back to the device and run it. Now you should be able to run `adb shell run-as ls /data/data/com.mypackage/` without getting the debuggable error.