I created google play certification which expires date 24/10/2033 and IDE created .apk file but i tried to upload this file google said "You uploaded an APK that is not zip aligned. You will need to run a zip align tool on your APK and upload it again."
How can i fix this situation?
Kind Regards.
18 Answers, 1 is accepted

Make sure you install the Android SDK. With this SDK the 'zipalign' tool is installed.
Then follow these steps:
- Generate your apk file from Icenium
- Open a command prompt and go to the folder with the apk
- Type: zipalign 4 <input>.apk <output>.apk (where input is your apk file and output is the zipaligned apk)
Upload the output.apk to Google Play
Make sure that the installation folder of the Android SDK is in your path. Zipalign can be found in the tools folder.
No need to download and install whole SDK for this, we have attached zipalign in as answer to this post.
Jordan
the Telerik team
Share feedback and vote for features on our Feedback Portal.
Want some Kendo UI online training - head over to Pluralsight.

Thanks for your reply about situation Jan-Dirk and Jordan. I handled zip-align process correctly and my app published on Google Play now. On the other hand i realized another issue. My app is not showing for android tablets for example Samsung GT-P5110. When i search on google play in tablet app not shows and if i try to install with link on tablet Google Play says this app is not compatible with your tablet.
Do you have any ideas why i have face to face with this issue?
Kind Regards.
I believe this is the issue we are facing : http://stackoverflow.com/questions/8420228/android-market-filters-app-telephony/8494994#8494994
There is no easy way to add this to AndroidManifest.xml.
You can use http://code.google.com/p/android-apktool/ to decode your app, change the android manifest by adding
<uses-feature android:name="android.hardware.telephony" android:required="false"/>
You will need to manually sign it after that though. There is more information here how to sign it manually: http://developer.android.com/tools/publishing/app-signing.html#releasemode
We will probably add this by default or at least to optionally add it to the manifest in the future.
Evgeni "Zammy" Petrov
the Telerik team
Share feedback and vote for features on our Feedback Portal.
Want some Kendo UI online training - head over to Pluralsight.

Evgeni i decoded my apk file and added xml tag to AndroidManifest.xml file. After that i created my release key but i can't create .apk file again because i don't have a eclipse project or ant buil.xml file for building the project. How can i compile and create againg .apk file?
Kind Regards.
Apktool can also encode. Instead of using the "d" option you can use "e" that will package the app back into apk. After that you can sign it with your release key and you should be good to go :)
Hope this helps,
Evgeni "Zammy" Petrov
the Telerik team
Share feedback and vote for features on our Feedback Portal.
Want some Kendo UI online training - head over to Pluralsight.

It's my fault, i miss that on manual sorry!!!. I created apk file with using "b" not "e" actually i don't know what is the difference between two parameters but with "b" parameter i created .apk. Now i'm trying to get icenium release key file because if i create new release key i cannot upload my file on play store for update my application. Google said to me "Your existing APKs are signed with the certificate(s) with fingerprint(s): sha1: XXXXX and the certificate(s) used to sign the APK you uploaded have fingerprint(s): sha1. XXXXXXX."
Any ideas for the icenium release key?
Edit: I fixed sha/certificate problem with converting p12 to .jks file and i can upload now google play but now i have another problem google play says android.hardware.telephony still in feature so apktool seems not worked for me? I think apktool cannot detect the changes on AndroidManifest.xml file and built without changes. I'm still trying to figure it out.
Edit 2: AndroidManifest behaves case sensitive. I fixed it and my app on Google Play now.
Kind Regards.

"You uploaded an APK that is not zip aligned. You will need to run a zip align tool on your APK and upload it again."

See my reply to the first post here: http://www.icenium.com/community/forums/icenium-graphite-/google-play-deployment#vfiVF3_xRmKLJP8AAPRZbQ
In addition see Jordan's reply in which he says that you can download ZipAlign here: http://www.icenium.com/clientsfiles/6450a864-da6a-41d9-b417-4132962abfe5_zipalign.zip?sfvrsn=0
So, in short:
- Download ZipAlign from my Jordan's link
- type: zipalign 4 <input>.apk <output>.apk (where input is your apk file and output is the zipaligned apk)



We have a story for that in our backlog and we will try to push it up in priority, but as we are close to "feature freeze" for upcoming release it may not be possible to re-schedule it.
I'm sorry for the inconvenience you may have to bear with for a while.
P.S. And Jan-Dirk big thank you for your helping hand with the forums.
Greetings,
the Telerik team
Share feedback and vote for features on our Feedback Portal.
Want some Kendo UI online training - head over to Pluralsight.




You no longer need to disassemble and re-assign manually your apps in order to make a configuration change. In Icenium 1.6 we've added the ability to make configuration changes to your app by modifying the respective Info.plist
and config.xml
for iOS and AndroidManifest.xml
and config.xml
for Android directly in the Icenium code editor. For more information, see Edit Configuration Files.
Steve
the Telerik team
Share feedback and vote for features on our Feedback Portal.
Want some Kendo UI online training - head over to Pluralsight.