Android builds with Mac does not install on Android devices.

Solar2D General Questions/Discussion
#101

Have you read this thread?

 

http://forums.coronalabs.com/topic/29712-android-failure-install-parse-failed-certificate-encoding/

It’s got some suggestions to try and determine if is a problem with your Java setup or not.   Also try doing a:

adb uninstall com.lk.shm

before you do your adb install.

Rob

#102

Thanks Rob for the reply.

I actually did read that topic and repeated posts that I’ve made before your reply was an effort to provide answers to questions people asked the OP (original poster) of that topic in order to help the process.

Please do correct me if I’m wrong but I think the OP of that topic did not reach an answer, right?

#103

Did you try the  uninstall call?

#104

Hi,

Sorry for the long delay, again. Can’t work as good as before.

I tried adb uninstall and it just said “Failed” in the Terminal. So I removed them manually via the phone.

I upgraded to Mavericks and when I tried to run my game in Corona Simulator it said that it doesn’t have Java, so I let it to download and checked via Java -version and it said 1.6.0_65.

I tried to build again and install via adb install, replied the same “INSTALL_PARSE_FAILED_CERTIFICATE_ENCODING” error.

What should I do?

#105

In another topic there was a suggestion of signing the apk file manually, I did that and still the same INSTALL_PARSE_FAILED_CERTIFICATE_ENCODING error is what I get.

I’m to the point that would be glad to give you guys my whole project, if you want.

Thanks.

#106

I renamed the apk file to zip and extracted it and there was two interesting things that caught my attention:

  1. There was a file named “icon” that has no extension and it’s size is zero. Is this normal?

  2. I have some files that I have folders with same name. For example. I have sfx.lua and a folder called sfx in the same structure. Can they make problem?

  3. I remember there was a problem with case sensitivity in Android builds, do they still exist to this day and age?

#107

Apparently problem was not related to my folder names as I changed them and problem persists.

Why is this bug this hard to find? It’s so frustrating, everytime I want to work on this game, I get stuck with this bug and can’t get anything done.

#108

Folder names can cause problems, but having an sfx folder and an sfx.lua shouldn’t be an issue.  Folder names with non-ASCII characters can cause issues (and not just within the project).  On iOS, a folder name “resources” causes issues.

Android (and iOS) devices file systems are case sensitive, Windows and the Mac’s filesystems are not.  But this would result in your app getting a black screen (crashing) when you run it and the error would be obvious in your adb logcat.

You are having a signing issue, so sending us your project isn’t going to do much good.  With your upgrade to Mavericks and the changes to java, humor me and try to build and install the Hello World sample app.  Take screen shots if the Corona build screen before you click the build button so I can see what’s set there.

Rob

#109

Hi man,

First of all let me thank you for your constant support.

Following your advice, here is screenshot of my build window:

[media]https://www.dropbox.com/s/1r4t9ho2kvdl1ng/Screenshot%202013-12-01%2023.14.07.png[/media]

And results is that it got installed with “Success” in Terminal.

What now?

#110

Were you able to use _ adb install _ to install the app on your device?

If so, then there is a problem with your  app some where.  If that failed, we have a keystore problem, however, your screen shot shows you are using a debug keystore  and that shouldn’t be generating any errors.

What is the result of the command line command:   java -version

Thanks

Rob

#111

Yes, I installed the HelloWorld app with adb install.

Java -version results this:

java version "1.6.0\_65" Java(TM) SE Runtime Environment (build 1.6.0\_65-b14-462-11M4609) Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-462, mixed mode)
#112

Then there is an issue with your app itself.  If you want to zip it up and get it to me somehow (uploading to dropbox and sending me a link to it would be fine), then I’ll see if I can see what’s causing the problem.

Rob

#113

That would be splendid. How can I give the project to you privately? Can’t seem to find PM feature anywhere.

#114

You can email me at rob at coronalabs.com

#115

Actually it was the “Icon” file.  I removed it from your folder and it installed just fine.  I’m not sure what it’s doing in your folder, but it’s creating issue.  Simply remove it and you should be good to go.

Rob

#116

Thanks man,

I have 11 icon files, which one are you referring to?

My suspicion was for a file named “icon” with no extension in the apk file, if you are referring to the same file, I don’t have it in my project but it is generated in the apk file.

Thanks again,

Cheers.

#117

Yes, the Icon file with no extension.  And yes, it’s in your project.  It was in the zip file and as soon as I removed it, your app installed correctly.

Rob

#118

Thanks but how could you see it, are you using OS X? I can see it with “ls” command in Terminal but can’t see it in Finder.

#119

Finder is probably confusing it with your Icon.png file by hiding the extensions.  I saw it in the file side bar on Sublime Text 3.  But you will probably see it using “ls” from the command line.  Just do a:

rm Icon

from the command line while in the right folder to get rid of it.

Rob

#120

YES, YOU ARE THE BEST, MAN! Love you! Can’t believe it that this nasty bug is finally “killed”, may the force be with you!

I found where that Icon file comes from, I put Icon on folder of my project (Finder “feature”) and it was that very same file … GRRRR!

Thanks again, finally something good happened.

-=-=-=-=-

BTW, how do you navigate files with Sublime Text? I thought it’s only for text editing.