I encounter this problem on Android 2.3.2 device when trying to play my build
i builded apk with latest corona and then uploaded it on web server and dl’ed it on device and installed
what i did wrong? maybe i needed to make config lua file for resolution settings? i used just main.lua and couple of images [import]uid: 16142 topic_id: 11416 reply_id: 311416[/import]
Check filenames… lowercase names for example [import]uid: 9577 topic_id: 11416 reply_id: 41346[/import]
Did you ever find the answer to this? This has just started happening to me, I did quite a number of changes before building for my device so i’m not sure what could have caused the problem.
Runs fine in the simulator just fails when trying to run on device with the corrupt message. [import]uid: 72726 topic_id: 11416 reply_id: 58139[/import]
Same Problem here. No idea why the “is corrupted” message is shown. [import]uid: 64174 topic_id: 11416 reply_id: 58651[/import]
I think the problem is from corona build 619+, i just installed 618 and it go working again…
They should be fixing now i hope… I want to use the newest fixes for androd since 619+ [import]uid: 75034 topic_id: 11416 reply_id: 58734[/import]
Daily builds are not guaranteed to work perfectly, or even at all - please use the latest stable build (at this time .591) to build with if you encounter issues with daily builds.
Also avoiding subfolders can help and ensure that you have got your capitalization correct. (eg, “Picture.png” is not the same as “picture.png” on device even if the simulator shows it fine.)
Peach [import]uid: 52491 topic_id: 11416 reply_id: 58835[/import]
I have the same problem using build 591. I made a build a week ago and it worked fine, but my latest build just fails to run with the “Corrupt” error on the Android phone.
Is there some way we can get more info about the failure? A log file on the device with something useful? Or a feature in the simulator to write out a file manifest? At least then I could compare the manifest against my files on disc.
Looking through each lua file and comparing hundreds of filenames is a lot more tedious than it would be if there was a manifest feature.
Also, what is wrong with using a sub folder for images? I know the Android wants all of the sound files in the root, but the build that worked had images in a subfolder and there were no problems.
Any guidance is greatly appreciated. [import]uid: 16734 topic_id: 11416 reply_id: 60918[/import]
Everyone,
You would typically get an application corrupted error message if there is a syntax error in your Lua script or if it uses an API that does not exist. If it’s working in the simulator, then it’s in a code path that only gets executed on the Android device such as the accelerometer, gyroscope, gameNetwork, etc. Lua listeners.
The best way to track these down is to use the Android SDK’s “adb” utility. If you connect your Android device to your PC via USB, you can run the following command line to see a real-time log of everything that is happening on the Android device…
“adb logcat”
The log should then give you better detail of what has went wrong within the app. [import]uid: 32256 topic_id: 11416 reply_id: 60966[/import]
Thanks Joshua. Your message was a great help for me. [import]uid: 84304 topic_id: 11416 reply_id: 64261[/import]
“adb logcat” did it for me, thanks Joshua. Although I had to use Snagit to grab the screen as the app launched because I couldn’t find any way to stop it (except pulling the USB lead out).
Turned out it was capitalisation. I was referring to “utilities.lua” as “Utilities” in one of my “classes”.
[import]uid: 95579 topic_id: 11416 reply_id: 66994[/import]
Kevin,
Glad you got it working. Yeah, the Android file system is case sensitive, so that would definitely cause a problem. To make things more confusing, Windows and OS X file systems are not case sensitive, so the Corona Simulator wouldn’t catch these casing issues and would allow it. Someday we’ll have to add some warnings to the simulator about file casing differences, but that’s not an easy thing to pull off.
Oh, and you can stop “adb logcat” by pressing CTRL+C.
[import]uid: 32256 topic_id: 11416 reply_id: 67024[/import]