This Application Has Been Corrupted - Bug - What is the problem?

Solar2D Daily Builds and Public Releases
#1

When I built my application for the first time on Android and Nook, I got this error when I installed it on my device. I’ve built many applications previously which makes me wonder what is the problem with this build. I have checked, and their are no errors in the Console, and all the build.settings are correct. Also, I have required all of the necessary libraries.

If someone could please help me troubleshoot this problem I would greatly appreciate it. Has anyone else had this error before?

Build 704 and Others I’ve Tried.

Regards,
Jordan Schuetz
Ninja Pig Studios [import]uid: 29181 topic_id: 19221 reply_id: 319221[/import]

#2

Hey Jordan,

How certain are you that everything is capitalized correctly? That seems to be the number one reason for this error.

Peach :slight_smile: [import]uid: 52491 topic_id: 19221 reply_id: 74121[/import]

#3

@Peach,

I submitted 3 apps for Nook and one passed, the other two got the “This application has been corrupted” rejection.

When you say “that everything is capitalized correctly” are you talking about individual resource files in the app, or something else?

Thanks,

Ken [import]uid: 16734 topic_id: 19221 reply_id: 107181[/import]

#4

Hey Ken,

Yes, am talking about individual resource files - a single missing/unnecessary capital letter can throw everything out.

I know it’s a PitA :frowning: [import]uid: 52491 topic_id: 19221 reply_id: 107188[/import]

#5

Peach,

Yes, I was aware of that and tested my app before submitting. Because of the Corona BUG with the Nook Color, I had to just select the Noon Tablet for submission. Hopefully that bug will be fixed in the next stable release so I can resubmit my apps for both Nook Color and Nook Tablet.

My best guess is that the issue is because I have my images in sub folders. That works for debug builds on the device, but I’m guessing it doesn’t work for release builds. Sadly there is no real way to know unless I can test a signed build on the device with adb. [import]uid: 16734 topic_id: 19221 reply_id: 107197[/import]

#6

Ken, have you tried running adb logcat?

Recently on one of my own apps, i decided to handle scaling manually and found the reason why it no longer loaded on my android device was because I was loading a texture too big for the device. [import]uid: 84637 topic_id: 19221 reply_id: 107340[/import]

#7

Developing with Corona under Windows Vista

Just my experience with the application has been corrupted error on installation. I had it a number of different ways. One was long resource filenames, another was similar with mixed case names – remember windows does not care about case.

Also, check your java version, there is something about how the security of java 1.7+ works that does not allow an installation based on that code to work. I reverted to 1.6 and it worked fine.

Lastly, depending on how you deploy your .APK I had put my file on a web server and found that depending on how it was downloaded, it may be missing a few bytes which would throw of the archive’s CRC – again causing an error.

So my rules of thumb.
> Use short lower case file names
> Keep the java version low as you can go 1.6 for me.
> Have log cat running :slight_smile: [import]uid: 108994 topic_id: 19221 reply_id: 107343[/import]

#8

It may be the Java version as I’ve built this on multiple machines and it is possible I submitted the one that passed on a machine with Java 1.6 and the ones that failed were Java 1.7. I’ll make sure to have all my machines use Java 1.6 [import]uid: 16734 topic_id: 19221 reply_id: 107362[/import]