I’m using Win7, 32bit. Latest build 2017.3179. Also used 3178 first.
When I build for live build, build works fine. When I build for submission, the build appears to complete.
14:09:27.481 BuildID: 5a22b3c417b66
14:09:28.102 WebServices: downloading build
14:10:02.542 Android build succeeded in 130 seconds
However the apk is only 21kb. Tried a different older project and got the same result.
Problem started yesterday (Dec 1) late afternoon UTC.
Update: Tried android build from a Mac. Same result.
Then I built an IOS version of the same app. It seems fine, but I’m not submitting yet as I need to make changes, so unsure if the build is OK.
The minimum app size for an Android build should be around 8mb, so 24kb doesn’t sound right. A .apk file is just a .zip file, so you can rename it to .zip and extract the files and see what’s there. Maybe post a list of the files that it unpacked.
You can also follow the instructions in this thread:
https://forums.coronalabs.com/topic/71032-build-fail-with-no-clear-reason/
to increase the amount of build logging we do and see if there is any more useful information.
There is also a second debug key that you can increase too: debugBuildProcess
Rob
Rob,
So the downloaded apk just had a Manifest.mf file. That had 2000+ lines mostly of references to icons and graphics.
This is the last 2 lines.
Name: lib/armeabi-v7a/libjnlua5.1.so
SHA1-Digest: DnKk946u7mvdRMBeMwdbT0A1itU=
Setting the debug to 1 and 2 resulted in just one extra line - build failed at xxx seconds.
Other info:
Using appodeal for the first time - but I checked with an older app without appodeal and that failed also.
The build server communication takes a lot longer than I’m used to, but the app previously was just 13mb before I added appodeal. The live build (which works) is only 20mb with appodeal.
Thank you for responding on the weekend.
That’s really bizarre. We may need you to zip up your project and email it to support so we can try and build it and see what happens.
Rob
Even more bizarre. Used a Win10 laptop running Corona 2017.3026.
Appeared to be a successful build, 22mb file. However, rejected by Android Publish with a very long list of errors, suggesting a problem in the package.
Here’s an example
You uploaded an APK with an invalid signature (learn more about signing). Error from apksigner: ERROR (Jar signer APPTOONZ.DSA): No digest for res/drawable-xxhdpi-v4/ic_maps_indicator_current_position_anim1.png in META-INF/APPTOONZ.SF ERROR (Jar signer APPTOONZ.DSA): No digest for assets/images/graph_pay.png in META-INF/APPTOONZ.SF ERROR (Jar signer APPTOONZ.DSA): No digest for res/drawable-hdpi-v4/abc_list_longpressed_holo.9.png in META-INF/APPTOONZ.SF ERROR (Jar signer APPTOONZ.DSA): No digest for res/drawable-xxhdpi-v4/abc_ic_star_half_black_16dp.png in META-INF/APPTOONZ.SF ERROR (Jar signer APPTOONZ.DSA): No digest for res/drawable-mdpi-v4/common_google_signin_btn_icon_dark_normal.9.png in META-INF/APPTOONZ.SF
The list was over 600 items long.
THEN, I upgraded my Corona on the laptop to 2017.3178. Got the result of 21kb file, no error reported, just like from my desktop and the mac.
Can you post a screenshot of your build dialog just before you hit “build”? Please don’t blur out any fields. If you feel the information needs protected, reply to the email where you submitted the issue to support and attach it there.
Thanks
Rob
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.