… Also I just tried building a sample app with the adk, and was able to do that successfully. I did have to generate a new debug.keystore to build with eclipse, and I know you said that that shouldn’t be the problem, but tried using that key anyway, and it didn’t work. Any ideas?
I’m really sorry for necroposting but, was there any solution to this? I was using this normally till a few days ago then I can’t install the apk anymore, it gives me Failure [INSTALL_PARSE_FAILED_CERTIFICATE_ENCODING]
Suddenly I’m encountering this error as well…
It really helps when you have a problem like this to let us know what version of Corona you are running and what Operating system you’re running it on.
Also have you checked to make sure your JDK is correct?
Are you signing with the debug key or a release keystore?
Sure. I’m signing with my release keystore which has worked until just now. I’m on Build: 2013.1137 and Mac OSX 10.8.4. My java version is 1.6.0_51. Trying to install to my Samsung Galaxy SII
thanks,
Jen
I’m sorry I forgot about the build and OS. I’m using build 2013.1137 and Mac OSX 10.8.4. My java version is 1.6.0_51. I checked for any sign of jdk7 but there wasn’t. I tried the debug.keystore from my windows version of Corona (same build) but it said it was expired in the Corona Terminal which is weird.
Stephen, looks like we have identical setups
Hi Jen, yes it seems we have the exact setup and problem. Everything was working fine last week. When I verify the apk file using jarsigner -verify it gives me this:
Warning:
This jar contains unsigned entries which have not been integrity-checked.
This jar contains entries whose signer certificate has expired.
I’ll update here if ever I find a solution to this. For now i’ll be using windows.
hi, a little more info here. I am working on two projects (actually more than that) at the same time. One of them that has a simpler setup I am able to build w/o issue using my regular dist keystore. The other one is the one I’m having trouble with. That one has more add-ons including GCM integration. I wonder, can you compile a simple project from sample code? If so, maybe it’s the particular project that is posing problems.
Jen do you have any folders names res, resource or anything that sounds like it could be a keyword?
Are you building your app back into your project folder?
Are you using anything that does symlinks or copying in/out used/unused assets?
Are you using something like Glider for an IDE that may be leaving it’s debugging code in (seriouslly doubt that would cause this error though)
Since you can build one and not the other, can you temporarily swap out build.settings on the one that won’t build?
Do you have any weirdness in your path names?
Hi Jen,
Like you suggested, I tried building a sample project and install it using adb and it worked. I’m going to try and see what’s wrong my code or build settings then, but definitely it’s not the keystore.
I’m really sorry for necroposting but, was there any solution to this? I was using this normally till a few days ago then I can’t install the apk anymore, it gives me Failure [INSTALL_PARSE_FAILED_CERTIFICATE_ENCODING]
Suddenly I’m encountering this error as well…
It really helps when you have a problem like this to let us know what version of Corona you are running and what Operating system you’re running it on.
Also have you checked to make sure your JDK is correct?
Are you signing with the debug key or a release keystore?
Sure. I’m signing with my release keystore which has worked until just now. I’m on Build: 2013.1137 and Mac OSX 10.8.4. My java version is 1.6.0_51. Trying to install to my Samsung Galaxy SII
thanks,
Jen
I’m sorry I forgot about the build and OS. I’m using build 2013.1137 and Mac OSX 10.8.4. My java version is 1.6.0_51. I checked for any sign of jdk7 but there wasn’t. I tried the debug.keystore from my windows version of Corona (same build) but it said it was expired in the Corona Terminal which is weird.
Stephen, looks like we have identical setups
Hi Jen, yes it seems we have the exact setup and problem. Everything was working fine last week. When I verify the apk file using jarsigner -verify it gives me this:
Warning:
This jar contains unsigned entries which have not been integrity-checked.
This jar contains entries whose signer certificate has expired.
I’ll update here if ever I find a solution to this. For now i’ll be using windows.
hi, a little more info here. I am working on two projects (actually more than that) at the same time. One of them that has a simpler setup I am able to build w/o issue using my regular dist keystore. The other one is the one I’m having trouble with. That one has more add-ons including GCM integration. I wonder, can you compile a simple project from sample code? If so, maybe it’s the particular project that is posing problems.
Jen do you have any folders names res, resource or anything that sounds like it could be a keyword?
Are you building your app back into your project folder?
Are you using anything that does symlinks or copying in/out used/unused assets?
Are you using something like Glider for an IDE that may be leaving it’s debugging code in (seriouslly doubt that would cause this error though)
Since you can build one and not the other, can you temporarily swap out build.settings on the one that won’t build?
Do you have any weirdness in your path names?