Did you find any errors in the console log from building your app with the older keystore?
nope, everything works fine. i got this:
18:12:50.395 Using custom build id from app bundle: 00000 (AppSettings.lua)
18:12:50.395
18:12:50.395 Using custom Build Id 00000
18:12:50.405 Excluding specified files from build:
18:12:50.405 excluding: Icon.png
18:12:50.405 excluding: Icon-Small-*.png
18:12:50.405 excluding: Icon*@2x.png
18:13:37.793 BuildID: 5995c08396016
18:13:58.696 Android build succeeded in 68 seconds
and again, the app updates successfully on the device if i overwrite the old one. the only problem is the play store not accepting it (or any of my older apps signed with this key)
Are you on a Mac or Windows?
Windows
Can you run regedit.exe (as an Admin) and find this key:
HKEY_CURRENT_USER\Software\Ansca Corona\Corona Simulator\Preferences
Add a string value “debugBuildProcess” and give it a string of “1”
This should increase the logging. You will probably want to exit the simulator first, then re-run it and try and build your project.
19:07:22.873 Using custom build id from app bundle: 00000 (AppSettings.lua)
19:07:22.873
19:07:22.873 Using custom Build Id 00000
19:07:22.873 Excluding specified files from build:
19:07:22.873 excluding: Icon.png
19:07:22.873 excluding: Icon-Small-*.png
19:07:22.873 excluding: Icon*@2x.png
19:07:22.873 AntCall: buildFilePath: C:\Program Files (x86)\Corona Labs\Corona SDK\Resources\build.xml; target: build-input-zip; logLevel 1
19:07:22.934 DeviceBuildData: {“isLaunchPadActive”:false,“targetCertType”:“distribution”,“targetPlatformVersion”:140300,“debugBuildProcess”:1,“targetDevice”:0,“dailyBuildRevision”:3120,“buildBucket”:“ansca-templates”,“clientPlatform”:“Win”,“targetAppStore”:“google”,“targetPlatform”:1,“clientDeviceId”:“9a7e226ba3dbe33e4958b48d25511de5”,“plugins”:{“plugin.applovin”:{“supportedPlatforms”:{“android”:true,“iphone”:true,“appletvos”:true},“publisherId”:“com.coronalabs”},“plugin.google.play.services”:{“supportedPlatforms”:{“android”:true},“publisherId”:“com.coronalabs”}},“dailyBuildYear”:2017,“clientProductId”:“basic”,“appName”:“Test”}
19:08:09.904 BuildID: 5995cd4c08456
19:08:26.674 AntCall: buildFilePath: C:\Program Files (x86)\Corona Labs\Corona SDK\Resources\build.xml; target: build; logLevel 1
19:08:30.375 Android build succeeded in 68 seconds
Well that really didn’t provide any thing useful… *sigh*. Maybe try upping the value from 1 to 2 or 3. I get a lot more information on my Mac. There is another key, but it’s more for diagnosing issues with the build servers. You can try and add it too.
debugWebServices
Both take values of 1 - 3 (or delete the key to turn off extra logging)
Rob
loglevel 3 logs the same stuff as 1 on windows, just tried.
while debugwebservices dumps a some sensitive data, not sure i should post it here
I’m looking for messages about failing to sign the app. Have you updated your Java?
Yes, latest 32bit jdk and both latest versions of jre.
But again, I don’t think it’s a problem on my part, o yours. The signed update is accepted on the device, it’s only the play store that’s not accepting it.
And again, all of my old builds, signed successfully with corona and uploaded to play store, give me the same error.
Uploading stuff signed with another key is working fine.
Did you find a solution to this? I get the same error. I tried building using Windows and Mac.
This is my log
2:39:38.953 Testing credentials for ‘C:\Users\xxxxx.keystore’:
22:39:40.298 jar signed.
22:39:40.298 Picked up JAVA_TOOL_OPTIONS: -Duser.language=en
22:39:41.600 Excluding specified files from build:
22:39:41.600 excluding: Icon.png
22:39:41.600 excluding: Icon-6*.png
22:39:41.600 excluding: Icon-7*.png
22:39:41.600 excluding: Icon-Small*.png
22:39:41.600 excluding: Icon@2x.png
22:39:41.600 excluding: Default-568h@2x.png
22:39:41.600 excluding: audio/*.m4a
22:40:43.037 BuildID: 59bae90ebb96d
22:40:43.378 WebServices: downloading build
22:41:00.521 Android build succeeded in 79 seconds
There isn’t anything in the log that looks suspicious. Is that the complete build log?
What version of Corona are you using?
Rob
nope, i had to create a new keystore
I used 3 different versions of Corona all with the same result
I havent released my game yet so its not critical, but for others I can only imagine the pain this must cause 