Here we go
Can you move your app to a local drive and try to build from there? Also, I was trying it with a debug keystore. It might be worth trying that as well. (test them separately please.)
Thanks
Rob
Works fine for debug keystore, making live build successfully today.
From local drive (no dropbox) result is the same. File is 21kb.
Any possibility you can trace by the buildid (5a257fbfa0477) your end. The dialog box says all the right things, including downloading. And the download time looks right for 20mB+
Here is the console output.
Testing credentials for ‘C:\Dropbox\apptoonzshared\apptoonz.keystore’:
17:02:45.837 jar signed.
17:02:45.837 Picked up JAVA_TOOL_OPTIONS: -Duser.language=en
17:02:48.023 Using custom build id from app bundle: 00000 (AppSettings.lua)
17:02:48.023
17:02:48.023 Using custom Build Id 00000
17:02:48.023 Excluding specified files from build:
17:02:48.023 excluding: sources/
17:02:48.023 excluding: appstore/
17:04:25.142 BuildID: 5a257fbfa0477
17:04:25.695 WebServices: downloading build
17:04:57.060 Android build succeeded in 129 seconds
Sending my keystore file via email
what if you don’t do a live build?
Rob
Interesting, the build works. Of course can’t submit that to app store.
So I rebuilt my keystore, in case it had become corrupt. It worked, but the app was rejected by google because I was updating an existing app, not creating a new app.
Are the symptoms characteristic of a corrupted Key?
Google determines updates from new based on the Package name. However, you cannot update an app if you use a different keystore.
Rob
Rob,
Did you build my app using the keystore I sent you? This would determine if the issue is on my side (setting or similar) or perhaps a corrupted keystore.
Unfortunately I’m in the position where I’ll have to abandon apps and create new ones instead of updating existing.
Conor
I’m away from my office and I don’t have a way to build and run Android apps, so no I have not had a chance to do so. It will at least be the weekend before I can look at this.
Rob
Hey, I just realized that 21kb build as due to packaging bug we had for only like 2 versions. Try 3184 please
3184 (without any changes to keystore OR with the new keystore you supplied) still results in 21kb build
Hello!
In support ticket you opened, I re-exported your key with
keytool -importkeystore -srckeystore apptoonz.keystore -destkeystore new.apptoonz.keystore
When building with new new.apptoonz.keystore, does google still thinks it is a new app?
I’ll respond by email, very confusing for readers.
Oh. OK. I found the error in build log on my mac, new keystore doesn’t work either…
[antcall] Exiting /Applications/Corona/Corona Simulator.app/Contents/Resources/build.xml.
[exec] Current OS is Mac OS X
[exec] Executing ‘jarsigner’ with arguments:
[exec] ‘-signedjar’
[exec] ‘MyCoronaActivity-signed.apk’
[exec] ‘-keystore’
[exec] ‘/Users/vlad/new.apptoonz.keystore’
[exec] ‘-storepass’
[exec] ‘mbwali’
[exec] ‘-sigalg’
[exec] ‘MD5withRSA’
[exec] ‘-digestalg’
[exec] ‘SHA1’
[exec] ‘MyCoronaActivity-unsigned.apk’
[exec] ‘apptoonz’
[exec]
[exec] The ’ characters around the executable and arguments are
[exec] not part of the command.
Dec 18 08:01:27.612 [exec] jarsigner error: java.security.SignatureException: private key algorithm is not compatible with signature algorithm
Dec 18 08:01:27.976 Override ignored for property “sign.apk.via.command.line.result”
Dec 18 08:01:27.977 [exec] Result: 1
This what I get on submission to play store
You uploaded an APK that is signed with a different certificate to your previous APKs. You must use the same certificate. Your existing APKs are signed with the certificate(s) with fingerprint(s):[SHA1: 64:F6:F6:90:DE:14:9C:2F:E4:BA:88:D4:A1:99:24:CD:35:02:8F:96]and the certificate(s) used to sign the APK you uploaded have fingerprint(s):[SHA1: C2:73:78:81:75:2E:69:9E:B6:4B:9F:BC:38:0C:A8:B7:8D:E9:62:F9]
Hey!
So, I was looking into what is going on, your key has “signature algorithm name: SHA1withDSA”, while all keys I have are “SHA256withDSA”. It seems that Java stopped supporting first one some time ago. I would suggest installing some old Java and JDK (6 or 7), make sure to uninstall current.
No good. Downgraded to jdk-6u45 and still same result
Are you sure all other versions of Java were removed?
Rob
Please, make sure you have only java 6 installed. If that doesn’t work, may I ask you to try following:
replace c:\Program Files (x86)\Corona Labs\Corona\Resources\build.xml with this build.xml file. I was able to build with your original key using it.
Well, success. I had made sure that only Java 6 was installed.
The new build.xml did the trick.
Thanks to Rob and Vlad for their patience on this.