Android app signature?
livecode.list at gmail.com
Mon Jan 27 19:34:33 EST 2014
Hmm, the stack has definitely been worked on across different computers.
But the apk has been built on the same computer.
So you encounter this issue with all your updates?
Has anyone else experienced this?
On Mon, Jan 27, 2014 at 3:56 PM, Roger Eller <roger.e.eller at sealedair.com>wrote:
> I get the same error as you, even if I sign for development only, but have
> worked on the stack on different computers. Unless I always build the apk
> on the same machine, the user has to uninstall the app just to install an
> update. I don't like it, but I don't know how to correct the problem.
> On Mon, Jan 27, 2014 at 5:12 PM, Chip Thomas <livecode.list at gmail.com
> > 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
> > error:
> > "Application not installed. Package with that name and different
> > already installed."
> > After some research, I used keytool to compare the certificate
> > 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
> > 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:
More information about the Use-livecode