I'm trying to test my application on my phone. I have successfully done it before but for some reason it seems to not be updating with the latest version. I uninstall my app from my phone, I build my application in Titanium for Android. I go to install now and it appears to install it on the device. I open the application and it is in the same state I left it in and has not appeared to have been updated. Driving me nuts!!!!!!
It sounds like your app's identity has changed, so when adb goes to install the app, the phone rejects your new version. This could happen if you installed a signed version of the app, and then went back in to development of it.
Try uninstalling the app from your phone, and then deploying it again. With a fresh slate, you should be able to get it working again!
Hope this helps; let me know if it doesn't and we can explore some other solutions! -Dawson
Related
I looked at other solutions for the above problem, but none of them seem to resolve my issue.
I am running AS 3.5.2, under Help/About/Check for new versions everything is showing as fully updated.
I am using Windows. When I plug my phone into my computer, it runs the latest updated version.
When I Build APK(s) under Build menu, and then install that version onto my phone, it is an old version.
Up until about 2 weeks ago it was building APKs fine, and today after making a few code changes (been 2 weeks about since I last made changes), it now has this issue.
What I've tried:
1. build.grade (app) - changed the version code and name to 2 from 1
2. Build menu - clean & rebuild project
3. Checked for updates and updated as needed
4. Run/Debug configurations - confirmed Gradle-aware Make is present (even removed then re-added)
So to add some more information. It turns out the Android Studio IS making the correct version. However, my phone just isn't loading it from the APK. This is what I have done:
I created a new version, 1.07, and with my phone plugged into my computer, it correctly runs this version on my phone, even when I unplug the phone and restart the newly installed app on the phone. I then navigated to the APK stored on our intranet (previously saved there as described earlier in this post), downloaded it and installed it on my phone. It has now reverted to v1.06 strangely. So on a different phone that had an older v1.04, I also downloaded the app from the intranet and installed it, and it showed v1.07. This shows that the APK WAS indeed correctly created. Then on a 3rd phone where the app was never previously installed, I installed it from the app, and it was v1.07. Again, correct version.
I then went to my 1st phone again, went into settings, went to the apps, and deleted the cache and data, then uninstalled it from my phone. I then went to downloads and APK's and deleted all previously downloads. So theoretically no trace should be left on my phone.
I then again downloaded the APK, and it is again v1.06!!!
I plug my phone into the PC (to use as the emulator) and it then correctly installs the correct v1.07 onto my phone.
What is happening...!!!? It is almost like it reverts to the previous v1.06 when I do a manually download and install of a v1.07 APK, but where is the v1.06 even coming from? Does the phone keep a history of the app versions?
Please help me make sense, and how to get it working. This app is for about 300 people in our company, hence me distributing the app over the intranet as a link.
Although this method is a bit vague and old fashioned, but it still works.
Step One: Run your android device as a virtual emulator.
Step Two: Run main.dart in your android device. This will install the app in your device.
Step Three: Go to Play Store and install this app called APK Extractor.
Step Four: Extract your APK from the app.
The APKs created through this are smaller and more efficient as compared to the ones created using Android Studio and work pretty well.
Last week I created a new Ionic4 project and wound up having to rip out everything but Android Studio to exorcise version incompatibilities in the build tools. That seemed to fix everything. However, after sending a client a third or fourth debug-signed APK, he reported he couldn't install it. ADB installed it on my tablet just fine, but it couldn't be installed from a webpage or the file system. Since then, some releases have installed, some not.
Investigating with an APK extractor turned up nothing unexpected.
Then I generated a new Ionic project from the sidemenu template, changed the widget ID to a unique name, and changed the homepage a bit. Nothing that should cause an install fail. And it failed!
LogCat showed an install error -22, but nothing more helpful. Turning off the Security Scan option within Play Protect does allow the app to install. If you turn the scan option back on and force a scan, it oddly doesn't complain about the "unsafe" app. Searching Google hasn't turned up any explanation.
Anyone else run into this? Telling clients to turn off security doesn't look great.
I am developing an app from so many days and i use my phone to test the app. So android studio always installs my app in my phone directly through ADB.
Today i made a signed apk from android studio and when i tried to install it. It gave me an error "App not installed - an existing package by the same name with a conflicting signature is already installed"
Check This Image :- http://i.stack.imgur.com/qumOm.png
So i uninstalled the old app and when i tried to install the signed apk it gave me error again"App not installed"
I Think my old app still left some Data in my phone.
So i used Titanium BackUp Manager and in first removed the app data and then uninstalled the old app.
This solved the problem and i was able to install my new app now.
Any,Other suggestions are welcome ??
You can get rid of the signature by removing /system/app/ folder from the device.
I also had issues installing gcam ports on my android device.
The above solution worked for me and I was able to install the app after removing
/system/app/GoogleCameraLegacy folder through TWRP recovery.
when i compile my android app to test on android device the first time, it installs the app on the device, but after changing some code when i recompile the code from eclipse ,the device runs the first installed version of the app.
please help me out.
some times such problem occur, try uninstalling then reinstall it.
Here are a few things you should be checking for:
Make sure you install the update, and not just compile it
Make sure the update is signed with the same certificate. Otherwise it will not install
Make sure your device is connected and USB debugging is enabled.
Try uninstalling the app from the device before pushing the update.
You can check to see if the install succeeded or failed in the console.
Through Eclipse I can easily re-install (without having to uninstall the app first), a small app I am currently developing, any change any number of times.
When I export that app ("release mode") and place it on a website, it downloads and installs without any problem. (I have to check "Unknown sources" for allowing installation of non-Market apps first, of course).
If I uninstall this app, then download it again and install it again, it installs without any problem.
However, if I try to re-install this app without uninstalling it first, then Android notifies that the installation failed.
My question is why? What makes an Android app re-installable? (i.e. without having to uninstall it first, thus losing its existing settings)
You cannot replace a signed application with an unsigned one.
You fail to install it because it has the same app version. If you recompile it and then download it, it will update, because the version will have changed.