created Android app cannot be installed on real device, Testing on that device works

[Matthias Rebbe]

Thanks Mark and Colin.

@Mark: Yes it is enabled.

@Colin: I googled a little bit, but  was not so successful with that. 
But your posting made me remember  your book. I remembered reading in there something about the Keytool-Application for Android some weeks ago. I was not interested in that stuff at that time, because
i did not plan to release an Android app. But now it was the right information at the right time. 

I created a keystore according to your explanations in your book and  "et Voilà" i was able to install the apk w/o problems.

Your book is worth every penny ! ! ! Thanks a lot.

Regards,

Matthias


--
Matthias Rebbe
matthias (at) rebbe.tk
Tel +49.5741.310000
Tel +49.160.5504462
--
"Life is too short for boring code"







Am 02.11.2012 um 01:16 schrieb Colin Holgate <coiin at verizon.net>:

> You will get exactly the symptoms you describe if you install an app with the same ID but that has had its certificate changed. It could be that the certificate persists, and the system knows that the ID is already associated with a certificate that it has. But also, if you're not using a certificate, I wonder what happens if there is already an app installed that also doesn't have a certificate?
> 
> If you do a Google search of 'android deleting old certificates' you'll see lots of questions about removing old trusted certificates. Might be worth checking out.
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode