I was very happy when I found ability to create release signed and proguarded apk
in my IntelliJ IDEA 11.
But created apk is very small ( 6 MB) against 33 MB of
all files in "production\out\mygame"
I guess images from /assets were not included to this final apk.
Or should I upload somehow classes.dex, mygame.apk.res to GooglePlay?
Thanks.
I was able to export the signed apk from the provided project and run it on my device. Try to disable Proguard option, it didn't work for me, probably because your project needs different configuration for obfuscation.
The signed APK contains all the images from /assets.
Finally I am not right. IntelliJ works okay. It is just impossible to install unsigned apk on device (what I tryed to do). Thanks
Related
My application's debug apk(one in bin folder) size is 25.8 MB, I'm not using proGaurd as of now, I have multiple libraries such as Facebook, Twitter, Google play services, Vuforia, and few other graphics related jars. So my problem is when I'm generating release version apk using export wizard I'm not getting correct apk file size. Everytime I generate apk for release version the size is different( like 19MB, 21MB, 23MB ,22MB,25MB). When I install this apk on device it is crashing. I have 8GB of RAM, I cleaned project before starting process, closed all running applications except eclipse , I also run CC cleaner and started eclipse from cmd prompt with 'eclipse-clean' command but still I wasn't successful to generate correct apk.
Any suggestions to solve my problems will be appreciated.
Using eclipse to generate Android app.
All of a sudden when I export a project - I get an apk file that's not valid.
e.g. missing AndroidManifest.xml and res folder.
It was working a few days ago and I didn't make any config changes.
When I test it in an emulator - the correct apk file is generated in the bin folder -
albeit without certificate signing etc.
A really hackish workaround is to go to Eclipse->Preferences->Android->Build and change the debug key to the cert you want to sign with. The downside is it's still built in debug mode. Eclipse can easily drive a good man insane trying to troubleshoot it. You might consider upgrading/reinstalling your version of Eclipse and/or reinstalling/upgrading to the latest ADT plugin.
If you don't have time to battle Eclipse, use the command line:
http://developer.android.com/tools/building/building-cmdline.html
How to compile APK from command line?
What is the difference between the different .apk outputs when building a signed apk from IntelliJ IDEA?
When I do a signed apk build from IntelliJ Idea (13.1.2) I get three different apk files.
../myApp.apk (921 KB)
../out/production/myApp/myApp.apk (914 KB)
../out/production/myApp/myApp.unaligned.apk (1412 KB)
My guess is unaligned is non compressed and shouldn't be used in the play store. Which one should be used in the playstore?
Note: I am using proguard but not using Ant or Maven.
Use the one you find at .../out/production/Your App name/yourapp.apk
Yet again, in properties of the project you can set the custom location for your APK. But I suggest you get used to the default ones since it will be a pain to set up your path each time.
I am working on an android application in Titanium. When i do a direct build by clicking Run>Android Emulator, the size of app.apk file generated under "approot/build/android/build" is 8 MB and i could able to copy this file in my device and install.
But when i package and distribute for Android store by choosing Keystore and password, the resultant .apk file size is only 5MB and when i copy this directly to device and try to install. Its actually not getting installed.
Will the app built using distribution process will be this size? please suggest.
Output from adb when installing the app :
Click on this link to see the output bigger : http://i.stack.imgur.com/Dtzb7.png
Googling, I found this for error code 103:
https://groups.google.com/forum/?fromgroups=#!topic/rhomobile/WJJvB8NVcuU
Could it be that you are using sdk 1.7? try to switch to the java sdk 1.6.
I found the solution, below are the answer to my question
1) Yes, when app is executed for production the file size will be reduced.
2) After publishing the app to a specific folder, we should be signing the application using below
command
jarsigner -verbose -keystore /home/balan/tmp/KeyStore360/android.keystore myproject.apk androidalias
Thanks for Steelight letting me know about the adb logcat, this helped me to sort out that my apk file missing certificate.
I have a webkit plugin apk (just like the sample BrowserPlugin under development/samples). I want to integrate it into the system.img. I build it as the preload apk in /system/app/, but when the phone boot up, the apk is not installed properly.
If I install the apk in /data/app/ manually, it works well.
when the apk in /system/app/, the .so inside the apk can not be extracted to /data/data//lib/
Anyone know how to integrate the webkit plugin as a preload apk on Gingerbread, please kindly help me.
Thanks
.so file should be merged to the system.img separately. If it's a browser plug-in, it should be copied to /system/lib/plugins/<package_name>
It looks like there's no mechanism in android to extract .so file from an apk file that contains .so files if it's integrated with the system.