Package file was not signed correctly - Help me

[galiksoft]

Hi everybody.
I made a game for android. I searched for the signing process and everything is ok.
(
http://www.glbasic.com/forum/index.php?topic=6169.0
http://www.glbasic.com/forum/index.php?topic=7150.15
http://www.glbasic.com/forum/index.php?topic=6560.0
)

I send it to google market and the package was accepted.
But, when people buy the game and install it in his phone, they get this message: "Package file was not signed correctly"

I had the java sdk 1.7, I have read that that version has signing problems, and I must use java sdk 1.6.
I did that. I desintalled everything. Later, I installed java 1.6 and android sdk. I Recompilled the game for android and signed the package. I submitted to google. Everything right. But when someone try to install from android market, the same message occurs.

Help me please

[Wampus]

That's strange.

So, you're starting with the file glbasic-release-unsigned.apk and then signing it with your private key. Do you test the signed packages with jarsigner -verify your_app.apk ?

[galiksoft]

yes.
It says ok...

What could be the cause?

[Wampus]

I'm not sure what the cause could be right now. Try jarsigner -verify -verbose - certs your_app.apk to see what it says. The CN= element should contain your company name.

Are you doing the zipalign after the signing and not before?

[MrTAToad]

What is the name of your application ?

Did you remove the three dummy files from the META-INF directory ?

It is could also be a problem with the person's device - ie the package software is too old, which, in turn may mean he's trying to install the program onto an older version of Android.  See http://code.google.com/p/android/issues/detail?id=22435

Basically, they may need to run a super user fixer...

[galiksoft]

"Are you doing the zipalign after the signing and not before?"
Yes

My app is "bang! bang!"

https://play.google.com/store/apps/details?id=com.galiksoft.bangbangdroid&feature=search_result#?t=W251bGwsMSwxLDEsImNvbS5nYWxpa3NvZnQuYmFuZ2Jhbmdkcm9pZCJd

It was not a single user with that problem, but a lot of users...

[Wampus]

I just found a thread on StackOverflow that I think you should look at. It describes your problem and several solutions: http://stackoverflow.com/questions/2519374/published-android-apk-gives-error-package-file-was-not-signed-correctly

Left over stuff from JDK1.7 or old installations of the badly signed app might be the cause.

[MrTAToad]

Its possible that the company name isn't the same as in the keystore setup...

[Wampus]

Did the problem get resolved? If so, it might he helpful to know which step worked.

[galiksoft]

I don't know!

i haven't an Android device.

May someone test it and give feedback?

[MrTAToad]

I'll certainly see if you can send me the signed package...