Hey guys, working on my first Corona game here, and loving it so far. One question - I can run the app in the simulator just fine, but when build for Android and run it on a Motorola Xoom tablet, I just see this error:
“This application has encountered a Lua error (see Logs) or has been corrupted”.
Nothing in the Android log shows me anything about the Corona App.
Any ideas?
Thanks,
Michael [import]uid: 121972 topic_id: 33687 reply_id: 333687[/import]
Hi,
I’ve had similare errors and they have been caused by either the phone not being an ARM7 or the graphic filenames not being exactly as used in the code. It is essential that you consider the case - using Windows the filename in the simulator does not get checked.
Robert [import]uid: 116086 topic_id: 33687 reply_id: 133933[/import]
Robert is correct. The first thing you should check is to make sure every filename you reference be it a Lua module file, an image an audio track etc. all match the case the filename really has. The simulator doesn’t check for case when looking for files but the device does. This is the solution to this issue 95% of the time.
[import]uid: 199310 topic_id: 33687 reply_id: 133942[/import]
Thanks guys, that did the trick. I used camel case for a folder and lower case in the code.
Since I’m here, any time saving tips for testing/debugging on the device while making changes?
Best Regards,
Michael [import]uid: 121972 topic_id: 33687 reply_id: 133949[/import]
Hi,
I’ve had similare errors and they have been caused by either the phone not being an ARM7 or the graphic filenames not being exactly as used in the code. It is essential that you consider the case - using Windows the filename in the simulator does not get checked.
Robert [import]uid: 116086 topic_id: 33687 reply_id: 133933[/import]
Robert is correct. The first thing you should check is to make sure every filename you reference be it a Lua module file, an image an audio track etc. all match the case the filename really has. The simulator doesn’t check for case when looking for files but the device does. This is the solution to this issue 95% of the time.
[import]uid: 199310 topic_id: 33687 reply_id: 133942[/import]
Thanks guys, that did the trick. I used camel case for a folder and lower case in the code.
Since I’m here, any time saving tips for testing/debugging on the device while making changes?
Best Regards,
Michael [import]uid: 121972 topic_id: 33687 reply_id: 133949[/import]
Hi
i am getting same problem.How can i see what is actual error ?. [import]uid: 209400 topic_id: 33687 reply_id: 138322[/import]
You need to install the Android Debug Bridge tools (adb). Google how to install it. Once it’s installed you can use the command line command: adb logcat
to see the devices console long if it’s teathered to a USB port.
[import]uid: 199310 topic_id: 33687 reply_id: 138413[/import]
For anyone else having this error maybe my experiance can help. I just spent about 20 hours trying to find what was wrong with my code. To avoid stuff like this I always have my file names in all lowercase so I couldn’t figure out what was wrong. I checked, tripple checked, and check like 5 more times and all of my file names and references matched perfectly.
It was especially hard because you don’t see the debug window when testing on the device. So you have NO idea where the problem might be. I used this Android Log Collector app: http://code.google.com/p/android-log-collector/downloads/list and it helped the process a lot. Still was a nightmare to find the issue.
Turned out in one of my file names (just one) I had a slash before a the reference to a folder. So it was: “/folder/file.png” I took out the first / so it was “folder/file.png” and POOF! everything worked perfectly. Such an annoying problem but I’m glad I could finally find the issue. Hopefully that helps anyone else out there.
One suggestion to Corona Labs. Perhaps you could print an error message in the simulator’s debug window that would cover this error. The simulator could check to see if there might be a problem with mismatching file names and then warn the dev when that’s the case. The fewer surprises when testing on device the better. Thanks! [import]uid: 94309 topic_id: 33687 reply_id: 138628[/import]
Hi
i am getting same problem.How can i see what is actual error ?. [import]uid: 209400 topic_id: 33687 reply_id: 138322[/import]
You need to install the Android Debug Bridge tools (adb). Google how to install it. Once it’s installed you can use the command line command: adb logcat
to see the devices console long if it’s teathered to a USB port.
[import]uid: 199310 topic_id: 33687 reply_id: 138413[/import]
For anyone else having this error maybe my experiance can help. I just spent about 20 hours trying to find what was wrong with my code. To avoid stuff like this I always have my file names in all lowercase so I couldn’t figure out what was wrong. I checked, tripple checked, and check like 5 more times and all of my file names and references matched perfectly.
It was especially hard because you don’t see the debug window when testing on the device. So you have NO idea where the problem might be. I used this Android Log Collector app: http://code.google.com/p/android-log-collector/downloads/list and it helped the process a lot. Still was a nightmare to find the issue.
Turned out in one of my file names (just one) I had a slash before a the reference to a folder. So it was: “/folder/file.png” I took out the first / so it was “folder/file.png” and POOF! everything worked perfectly. Such an annoying problem but I’m glad I could finally find the issue. Hopefully that helps anyone else out there.
One suggestion to Corona Labs. Perhaps you could print an error message in the simulator’s debug window that would cover this error. The simulator could check to see if there might be a problem with mismatching file names and then warn the dev when that’s the case. The fewer surprises when testing on device the better. Thanks! [import]uid: 94309 topic_id: 33687 reply_id: 138628[/import]