• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Apps Uploading to market

D

dimiter

Newbie
I can't upload test HelloWord app: android market don't receive apk-file (load error). It signing problem, i think. My signing:
Export->Export Android Application->Chouse project->Enter keystore password->Chouse key->Enter key password->(Certificate expires on Thu Jul 14 10:54:48 MSD 2061.)->Get apk.
It is right? I can't solute this problem 7 days. Help me.
 
Make sure you are signing the application with your own keystore and not the debug one. Also you cannot upload applications that have the same package name (ex: com.companyname.helloworld)
 
I know about packages. My package: com.hwdimiter93. I think, this is right name.
About degug: i think, if i export in wizard, it's release version. Isn't it?
I create keystore and alias with wizard, i don't undestrsand, how i can export with no my keystore. Sorry for the wrong english, it's don't my language.
 
How select degug or release signing? If i export with Export->Export Android Application, it's release sign or not?
 
You have to follow the instructions and create a signing key -- the market will not let you upload or publish unsigned apps.

Also moving this to 101 section :)
 
I execute Signing your Android Application | Android Development | Android Application Development | Android Game Development | Android Software Development | Google Android Development instruction (in jarsigner i use -keypass and -storepass) instriuction, and have in cmd "jar verified"
But i can't upload application again, my SF-file:

Code: 
Signature-Version: 1.0
SHA-256-Digest-Manifest-Main-Attributes: 3Z5RMcbH4f53yA7saORTXLXKnIN1A
 iXGUSmb/q7kBqs=
SHA-256-Digest-Manifest: p0CmD1xOoOEEAAB50ITNPcTnaSnlWkSoQLzB5VQEoZY=
Created-By: 1.7.0 (Oracle Corporation)

Name: res/layout/main.xml
SHA-256-Digest: vg7FenBpXwT7Pe4M2LdDyaPfF8O85A1vnECPXnncJes=

Name: AndroidManifest.xml
SHA-256-Digest: tpZTi5+8cS7UygjujEIg51WdOYkpQuPD0Mpo+DcOgjw=

Name: res/drawable/icon.png
SHA-256-Digest: YaaOYFPM/mHuYzlVl+4sOl+IWxulTz9UOmX/YpGb4wo=

Name: resources.arsc
SHA-256-Digest: Q8zwaKiUbqHOckzIVi9zk1x//1ye4XKm84CzpXFSxfs=

Name: classes.dex
SHA-256-Digest: 4VcFOh+RuzqRmauqFc4u2LVrDPWw+QnkU8iJGvoGfEQ=
 
You should really just use Eclipse your first time around

Signing Your Applications | Android Developers

Compile and sign with Eclipse ADT

If you are using Eclipse with the ADT plugin, you can use the Export Wizard to export a signed .apk (and even create a new keystore, if necessary). The Export Wizard performs all the interaction with the Keytool and Jarsigner for you, which allows you to sign the package using a GUI instead of performing the manual procedures to compile, sign, and align, as discussed above. Once the wizard has compiled and signed your package, it will also perfom package alignment with zipalign. Because the Export Wizard uses both Keytool and Jarsigner, you should ensure that they are accessible on your computer, as described above in the Basic Setup for Signing.
To create a signed and aligned .apk in Eclipse:

  1. Select the project in the Package Explorer and select File > Export.
  2. Open the Android folder, select Export Android Application, and click Next. The Export Android Application wizard now starts, which will guide you through the process of signing your application, including steps for selecting the private key with which to sign the .apk (or creating a new keystore and private key).
  3. Complete the Export Wizard and your application will be compiled, signed, aligned, and ready for distribution.
Click to expand...
 
I made it week ago, and if file was loaded, i don't post this thread. Align is optionally for applications? It needs?

Maybe, it's not signing problem? I made experiment: try upload other (not myself, i download with market) app, and market don't can receive it.
 
Zipalign is optional yes, but the eclipse tool will do it for you.

You cant download someone else's app and re-sign it, that wont work, and it shouldn't ;)
 
But i don't re-sign, i try upload with originally sign (i dont change those archive). It is normal? It working copy defence system?

How maybe other problems with upload? If i upload apk here, it can help?
 
My alias data fit is?
Orgainization unit: none
Orgainization: none
City: Moscow
First and last name: Dmitrij Lukianov
State or Province: Moscow
Country code: RU
 
dimiter said:
I execute Signing your Android Application | Android Development | Android Application Development | Android Game Development | Android Software Development | Google Android Development instruction (in jarsigner i use -keypass and -storepass) instriuction, and have in cmd "jar verified"
But i can't upload application again, my SF-file:

Code: 
Signature-Version: 1.0
SHA-256-Digest-Manifest-Main-Attributes: 3Z5RMcbH4f53yA7saORTXLXKnIN1A
 iXGUSmb/q7kBqs=
SHA-256-Digest-Manifest: p0CmD1xOoOEEAAB50ITNPcTnaSnlWkSoQLzB5VQEoZY=
Created-By: 1.7.0 (Oracle Corporation)
 
Name: res/layout/main.xml
SHA-256-Digest: vg7FenBpXwT7Pe4M2LdDyaPfF8O85A1vnECPXnncJes=
 
Name: AndroidManifest.xml
SHA-256-Digest: tpZTi5+8cS7UygjujEIg51WdOYkpQuPD0Mpo+DcOgjw=
 
Name: res/drawable/icon.png
SHA-256-Digest: YaaOYFPM/mHuYzlVl+4sOl+IWxulTz9UOmX/YpGb4wo=
 
Name: resources.arsc
SHA-256-Digest: Q8zwaKiUbqHOckzIVi9zk1x//1ye4XKm84CzpXFSxfs=
 
Name: classes.dex
SHA-256-Digest: 4VcFOh+RuzqRmauqFc4u2LVrDPWw+QnkU8iJGvoGfEQ=
Click to expand...

I encountered a similar problem with a failure to install the APK to my phone running Android 2.3.3 due to a reported invalid file digest. I see that you are using Java 7. It turns out that jarsigner from Java 6 uses SHA1 by default for the digest algorithm, while Java 7 uses SHA256. I cannot install an APK with files signed by SHA256, but SHA1 works fine.

To address this problem, add
 
You must log in or register to reply here.
Back
Top Bottom