I'm trying to install a generated APK on my phone, but it's giving me 'App not installed' error. The app is not unsigned and everything regarding the keystore seems fine.
I also tried generating APK for a different app and then installing it on my phone and had no problems doing so, it worked immediately and gave me no errors. I also checked the permissions in Manifest file and the dependencies in gradle file, couldn't see anything wrong with that also.
The app does compile and runs when I do it via USB & Android Studio.
Does anyone know what to do? I'm probably just doing some stupid rookie mistake or something.
You can view the project on Github here.
EDIT: So I tried sending the apk file to a friend to see whether it's just me having this problem and that turned out to be the case. Still not quite sure why won't install on my phone, but at least others can get their hands on it :)
Related
I have an app that I developed wow like 8 to 10 years ago, but I have been updating it constantly at least once a year or so.
I'm actually in the process of completely redoing the app from scratch, and it's working great when I run it on my Android from my computer, but when I build it with a signing key on PhoneGap Build, I get the error message "App Not Installed." when I try to install the apk.
I've read through several other posts on the topic and I can attest:
I have plenty of storage space on the phone.
The new version number is larger than the old version number.
The signing key is the same as the original version.
I do not have any version of the app currently installed on my phone.
Any other ideas on what may be causing this?
I've removed all my plugins to take that out of the equation, but I still get the same error.
The original app was build with OnsenUI and Cordova.
The new app is build in Ionic 5.4.16, Cordova 9.0.0, and Android 8.1.0.
Something else I have noticed is that if I change the app id (com.company.appname) to anything else (i.e. com.company.appnamedev), it installs. I feel like this is very indicative of the issue, but I don't know what to do with it.
Very much appreciate any guidance to finding the problem.
Unfortunately this isn't going to be the answer many of you solution seekers are hoping for, but I got it to work. Based on Mike N.'s suggestion, I attempted to sign it locally and push it to my device with adb. In doing that, I was having trouble with remnants of two older plugins (onesignal and admob) that I had already removed from my config.xml file.
I'm really not sure why, but after I got rid of those old pieces in my package.json, I attempt to push it to phonegap build again and it was able to install. So, I guess the solution would be to make sure you have fully removed any plugins that may be causing problems.
Now the big trick - adding these pieces of functionality back in. But, the app compiles on PhoneGap Build and the signed file installs on my device now.
UPDATE: So, it turns out this is directly related to the one signal plugin I'm using. Still figuring out why, but when I added it back in, it works great locally, but when I attempt to build with PhoneGap Build and load it to my phone, I get the error "App Not Installed." At least I know what's causing it now.
I finally figured out the root of all my issues. As it turns out, I had another half baked app I started and had on my phone under a different name and app identifier, but I had temporarily dropped the same google-services.json and GoogleService-Info.plist files into that other app that I use for the one in question here.
After employing Mike N's suggestion, I got the error:
adb: failed to install mynewapp.apk: Failure [INSTALL_FAILED_DUPLICATE_PERMISSION: Package com.company.new attempting to redeclare permission com.company.new.permission.RECEIVE_ADM_MESSAGE already owned by com.company.old]
I uninstalled the old app that should not have had those files to begin with and everything installs and works great now. Hopefully this helps someone else out who encounters the same bizarre situation.
You can use My APK application and installing an apk using My APK Installer (MAI).
If there is an error, it will show the detail (like duplicate permission, provider, mismatch signature,...)
I built an android application and signed the apk following all the steps on this tutorial. Even though the APK builds successfully after installing it on a mobile device it fails to load. I only get a white blank screen. I've searched for solutions and tried most of the suggestions but with no luck.
I then decided to start the project from scratch and guess what? the problem still persists. What could I have possible done wrong? I don't really know where to look because I don't even get an error message.
Please help???
I would try debugging that with a tool like GapDebug (https://www.genuitec.com/products/gapdebug/). I would:
Download and install GapDebug.
Attach your device to your PC/Mac via a USB cable.
Deploy your APK to the device and run it.
In GapDebug, choose your app as the app you want to debug.
At this point you may already see one or more errors showing up in the GapDebug console. If not,
On the device, restart the app.
Check the GapDebug console for errors.
I'm able to serve and run my app on Android (emulators, real device over ADB), but when I try to package the APk and install it on a device, I get an error. It seems like the package works just fine (an APK comes out with no error), but when I try to install my device says:
An existing package by the same name with a conflicting signature is already installed.
My sample app name is "boop" and I just made the keys/alias from scratch, so I'm not sure I really believe there is a conflict.
Anyone seen this before? Any ideas?
Doh! Figured it out.
I'd tested the application over ADB on this device. Seems like that actually installs the APK (which might be common knowledge, but I pictured some kinda temporary thing).
To get my actual signed APK to install, I just needed to uninstall the current version of "boop" on my device.
I could really use some help here.. I was using Phonegap build to build my (android) app with pretty much some JS, HTML5 and CSS.. I finished the project and was testing it by scanning the QR code and getting it on my android. Anyways all was fine and I was ready to upload to the android marketplace. After trying to upload the apk I got an error message saying the app was declared in debug mode (even though i never had debugging enabled in phonegap) after a little more research I then found out that I need to be running this in Eclipse and it needs to be signed. So I read the android documentation on signing and what not but I have no idea how to get over this hump.
I am like a lost puppy because I dont know eclipse and the app is finished. So I try to import my already done files into eclipse how I think I should be importing it and I get the error message that AndroidManifest.xml cant be found.. I have no idea the steps I need to take next, I am guessing I just need to import this puppy into eclipse so I can sign it and then I am assuming I will be able to upload to the marketplace?
Any advice for me knowing where I am in my project and what I need to do to get this off the ground? I am a complete noob and feel so lost.
[edit] it may be worth noting that I built this with Phonegap build and altough I do not have AndroidManifest.xml, I do have config.xml and all I really need to know is how to apply my signing key and I guess keep google marketplace from seeing it as being in "debug" mode.
Thanks for reading
I have compiled my application using nbandroid with netbeans 7.0 on a mac. Then keysigned it with jarsigner and aligned it using zipalign. It uploaded to the market with no issue but it will not install on any device giving the error "invalid package file". I have searched many times, but I have only found solutions on how to fix the problem on the device itself. Does anybody know what might be going on here?
Many Thanks,
Daniel
My app had a similar problem. See this Android Signed APK showing incomplete
In the end, I created an alternative eclipse project, copied all the files from original project and signed it using the original key. Seems like this is some eclipse-android plugin issue.