Package file was not signed correctly google search

I am seeing this too with Xamarin Android 4. Is there any update or confirmation on this. I see the bug is opened but no acknowledgement by Xamarin. I have the same error reported on Galaxy 3's. I have this same problem after creating an Android package on Xamarin Studio 5. Others users have no problem installing. I have tried manually signing with jarsigner but I still get the same error.

Frankbuckley, how did you get the workaround to actually work? What I don't understand is that it has "Normal" priority, as it basically breaks any Release for any app with a minimum target at or below 4.

I had this exact issue, publishes just fine on the play store and installed fine on some devices but failed on a galaxy tab 2 and Samsung S2. In case you're wondering if it is worth trying, I can confirm that re-creating the key using JDK6 fixed the problem for me, the devices that were failing are fine now. Bit of a pain since you have no choice but to create a brand new app. I noticed since then that the Xamarin setup docs do indeed say to use JDK6.

The content you requested has been removed. Ask a question. Data charges may apply. J how hard it is to produce an Android phone that can run Vanilla Android It's not possible at all. Every device including Nexus devices needs Android to be ported to that device. This means setting it up, from the source code, with the correct drivers, configured correctly for that device. Even if there are no other manufacturer customizations such as HTC Sense , it needs to be done to make Android work at all.

Even if the device is similar to or shares some components with an existing device, it still won't be compatible with that device's ROMs. This work needs to be repeated by the manufacturer for each new Android version. This costs money, and for unbranded devices where repeat custom and reputation aren't important, there's really no advantage for the manufacturer, or way for them to recoup their costs.

C I had been getting error for days. I finally managed to solve the problem using the following steps: I "ejected" the SD card via settings, device, storage. Android 6. Blackberry Priv. Cracking your screen most likely isn't covered through a warranty. This is a good reason why you should purchase a screen protector. Community Bot 1 1 1 silver badge. William Jockusch William Jockusch Which IDE do you use? How do you build the project? Are you sure you've used the same keystore and alias?

Xamarin Studio on my mac. But I'd really like to be able to test a signed apk to see if it is good or not.

Google wants Android Developers use Mac? Or maybe java 7 jarsigner for Mac is old same-no-warning functionality as java 6 for Win? Add a comment. Active Oldest Votes. Actually this is a common problem and i guess you must be using Java 7 or later.

Improve this answer. ProllyGeek ProllyGeek OK, based on the output, how do I know if the problem will occur or not? Actually this is a common problem - common how? I've built and released hundreds of apk versions to the playstore and never had this sort of issue TacB0sS this is common for people who use java 7.

We've been using Eclipse until today. We've now moved to Android Studio that forces you to use Java This doesn't make much sense Improve this answer. I managed to do that from titanium backup by converting google plus from system app into user app and uninstall it normally, Thank you for your advice The Overflow Blog.

Stack Gives Back Safety in numbers: crowdsourcing data on nefarious IP addresses. Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually.

Should the frequency of Community bot bumping unanswered questions be reduced?