Android app signature?

Chip Thomas livecode.list at gmail.com
Mon Jan 27 17:53:19 EST 2014


This seems to mostly address being in the emulator.

Is there another way to verify/compare the key between the two apks?


On Mon, Jan 27, 2014 at 2:20 PM, Neil Roger <neil at runrev.com> wrote:

> Hi Chipp,
>
> This stackoverflow post might give you some leads-
>
> http://stackoverflow.com/questions/19959890/android-
> app-not-install-an-existing-package-by-the-same-name-with-a-conflicting
>
> Kind Regards,
>
> Neil Roger
> --
> RunRev Support Team ~ http://www.runrev.com
>>
>
> On 27/01/2014 22:12, Chip Thomas wrote:
>
>> I built the standalone for my app update using the same keystore I used
>> with the original release.
>>
>> But when I try to run the APK on my device (emailed to myself), I get this
>> error:
>>
>> "Application not installed. Package with that name and different signature
>> already installed."
>>
>> After some research, I used keytool to compare the certificate
>> fingerprints
>> of the META-INF/*APP*.RSA files of both the original apk and the new one,
>>
>> and they match.  Would that be a good indicator that these should be the
>> same signature?
>>
>> I definitely don't want users to have to uninstall and reinstall the app
>> in
>> order to get this update.
>>
>> Any help or insight is greatly appreciated!
>> _______________________________________________
>> 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
>>
>
>
> _______________________________________________
> 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
>



More information about the use-livecode mailing list