Nook build rejected - "Parse Failed: No Certificated"

Solar2D Android
#1

Hey There,

Does anybody know what could possibly be causing this issue?

We have multiple apps live with Nook and have had one reviewed and approved since this situation started. Not sure what it is about this specific app that is causing the problem.

Our app was rejected by Nook as follows:

Result: The app fails to install onto the NOOK Color. An error message displays:
“Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]”.

At first I thought maybe when I created the build I accidentally selected “Kindle” or “Google” instead of “Nook” or had the wrong keystore selected, or some error in the build dialogue. I created a new APK being careful to double check that all the settings were correct, and that APK was rejected with the same error.

Thinking that the issue was a mistake I made while creating the .keystore file itself, I deleted the .keystore and created a new one, used it to build a new APK, and still was rejected with the same error.

We read online that this could be a Java issue, that Corona might not always be friendly with 7. Considering there is a different app that we built and submitted and was approved AFTER this app was first rejected, it doesn’t seem that Java is the problem. And all our other apps have been approved with the same exact version installed. Still, we tried a switch here too and got our 4th rejection with the same [INSTALL_PARSAE_FAILED_NO_CERTIFICATES] result.

Anybody? Any ideas? What could be different in the way this app is built that is causing the rejection?

Everything works correctly on the Nook device in our testing, and the app has been approved for Kindle and Google Play.

Thanks SO much in advance!

#2

What build of Corona SDK are you using?

#3

I should have included that!

I believe we were using Corona build 971 which was a stable public release when we first submitted this app, but we’re current with build 1076 now while still getting this rejection error.

#4

The “INSTALL_PARSE_FAILED_NO_CERTIFICATES” error typically indicates that the APK was not signed or was signed wrong.  Does your APK install correctly on your Nook device?  Or can you install a Google Play APK on a normal Android device without this error?

#5

Yes, the APK installs correctly on our test Nook device with both the debug signing and also the release keystore signing.

Two other versions of this app (signed with a Kindle keystore /and/ signed with a Google Play keystore) have also been submitted and approved for the Amazon Appstore and Google Play Store, respectively.

We just noticed that daily build 1103 includes this release note:

“Windows: Fixed bug where Corona fails to read the Android keystore after doing a Java update from version 6 to 7.”

Could this be a fix, or a related note, to our issue?

We submitted several apps using Java 7 that went on to be approved in the Nook Store, then had this rejection happen, and then changed Java back to version 6 in case that’s what caused the error and tried submitting again (with Corona build 1076) but that got rejected as well.

#6

If you are able to install your APK onto your Nook device, then that means it was signed correctly and there isn’t any problems with your built APK.  The most likely problem is that your APK got corrupted when uploading to their website or when they downloaded it for testing.

So, I would say, don’t worry about it.  Just re-upload your APK and inform them that you verified that the APK is signed correctly and you were able to install/run it on your Nook just fine.  Plenty of other Corona developers have had no problems submitting their apps to the Nook store, so this may just be a fluke.

#7

Thanks - I know that many other Corona developers have had no problems with Nook, we haven’t had any problems either - we have 25 apps live on Nook but this one just won’t get approved after FIVE submissions.

It is a larger size APK than our others, so it makes sense that the issue is happening somewhere in the uploading/downloading process, but it is under their limit of 100MB and we’ve now re-uploaded it five times.  Will try again now…

#8

Have you tried contacting their tech-support group directly?

This is in case it is a known issue with their upload web page that they might have a work-around for.

#9

What build of Corona SDK are you using?

#10

I should have included that!

I believe we were using Corona build 971 which was a stable public release when we first submitted this app, but we’re current with build 1076 now while still getting this rejection error.

#11

The “INSTALL_PARSE_FAILED_NO_CERTIFICATES” error typically indicates that the APK was not signed or was signed wrong.  Does your APK install correctly on your Nook device?  Or can you install a Google Play APK on a normal Android device without this error?

#12

Yes, the APK installs correctly on our test Nook device with both the debug signing and also the release keystore signing.

Two other versions of this app (signed with a Kindle keystore /and/ signed with a Google Play keystore) have also been submitted and approved for the Amazon Appstore and Google Play Store, respectively.

We just noticed that daily build 1103 includes this release note:

“Windows: Fixed bug where Corona fails to read the Android keystore after doing a Java update from version 6 to 7.”

Could this be a fix, or a related note, to our issue?

We submitted several apps using Java 7 that went on to be approved in the Nook Store, then had this rejection happen, and then changed Java back to version 6 in case that’s what caused the error and tried submitting again (with Corona build 1076) but that got rejected as well.

#13

If you are able to install your APK onto your Nook device, then that means it was signed correctly and there isn’t any problems with your built APK.  The most likely problem is that your APK got corrupted when uploading to their website or when they downloaded it for testing.

So, I would say, don’t worry about it.  Just re-upload your APK and inform them that you verified that the APK is signed correctly and you were able to install/run it on your Nook just fine.  Plenty of other Corona developers have had no problems submitting their apps to the Nook store, so this may just be a fluke.

#14

Thanks - I know that many other Corona developers have had no problems with Nook, we haven’t had any problems either - we have 25 apps live on Nook but this one just won’t get approved after FIVE submissions.

It is a larger size APK than our others, so it makes sense that the issue is happening somewhere in the uploading/downloading process, but it is under their limit of 100MB and we’ve now re-uploaded it five times.  Will try again now…

#15

Have you tried contacting their tech-support group directly?

This is in case it is a known issue with their upload web page that they might have a work-around for.