Ok, I've now figured out why the app won't install...it;s because Android requires that the SIGNING KEYS match the previously installed app's key.
But, it's not like I changed the key. The previous instance from a year or so ago did NOT have a key and now it MUST have a key. So, there's NO POSSIBLE WAY to make no-key match a new-key. (Sigh.) I figured this out, because my wife just got a new Android-based phone, and the app installed just fine there, since the earlier instance of the app was never installed on it previously. Once that indicated what the problem was, I did a factory-reset on my Nexus-7(2012), and then the new app installed just fine. On Sunday, August 23, 2015 at 8:38:36 AM UTC-4, cookdav wrote: > > Ok, I got past the problem of "Parse Error..", by SIGNING the app. > (That wasn't necessary a year ago.) > > So, now the installer runs, but at the end, the installer says: > > > X App not installed. > > [ Sigh. No reason given. What...we're supposed to be mind-readers??? ] > > > > > > On Sunday, August 23, 2015 at 2:47:42 AM UTC-4, gjs wrote: >> >> Hi, >> >> Maybe try again but without installing via ES File Explorer ? >> >> I just tried the a similar test - downloading & installing by >> 'sideloading' a (properly signed) apk via a gmail attachment to Nexus 7 >> (2012) with Android v5.1.1 & it installed (using the default Android >> installer - NOT ES File Explorer) without error & worked OK. >> >> (My apk was created in Eclipse however, no AS...) >> >> Also if you are attempting to download & install from a Web page you also >> need to set the correct content type in your web server, eg - >> >> <mime-mapping> >> >> <extension>apk</extension> >> >> <mime-type>application/vnd.android.package-archive</ >> mime-type> >> >> </mime-mapping> >> >> Regards >> >> On Sunday, August 23, 2015 at 2:04:31 AM UTC+10, cookdav wrote: >>> >>> After doing a successful assembleRelease in AndroidStudio (version >>> 1.3.1), I can use the >>> debugger to download and install my app, via a USB-cable, and it >>> installs (and runs) fine. >>> >>> But, if I put the APK file onto my webpage, and download it (using >>> Chrome) onto the tablet, >>> when I try to install it (using ES File Explorer), I immediately get >>> "Parse error ...there was a problem parsing the package". >>> >>> The target tablet(s) are Nexus 7(2012) and Nexus 10, running Android >>> v5.1.1. >>> >>> This all worked fine, back a year ago, when I was running beta copy of >>> AndroidStudio. >>> (I have imported this year-old app's project tree, into AndroidStudio >>> 1.3.1) >>> >>> So, I repeated this experiment, after creating a NEW boiler-plate app in >>> AndroidStudio >>> and I get the same behavior...i.e. it installs this generic TestProject >>> via USB-cable via >>> the Androidstudio's debugger just fine, but I get the "Parse error" if >>> I try to install >>> a downloaded copy (either via Chrome or via the USB-cable) residing in >>> the Download folder. >>> >>> Is there some 'debugging' method of installing Android APKs that will >>> give a more specific >>> error-code, to provide specifics of what the problem is??? >>> [ When I google this 'Parse error' symptom, there are at least a DOZEN >>> different reasons >>> mentioned that can cause this error, but none of them apply. ] >>> >>> Yes, I have developer options enabled on the tablets including >>> allow-from-unknown-sources, >>> and yes, I've verified the exact file-sizes using ES FIle Explorer, etc, >>> etc. >>> >>> Ideas? Or should I just give up trying to develop native Android apps >>> using AndroidStudio? >>> >>> >>> -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
