In Android 8 there is a new section called "App details in store" (Settings -> Apps -> select an app). The apps installed from Google Play has setted this field to: App downloaded from Google Play Store.
Apps installed from Amazon: App downloaded from Amazon Appstore.
But when I install an app from my own app, this is the message: App downloaded from Package installer
Some screenshots:
I've setted Intent.EXTRA_INSTALLER_PACKAGE_NAME but the result is:
I would like to set my app name in this field: App downloaded from "MyAppName"
Any ideas?
Thanks!
It is a name of the application installer application.
Like which app has installed this app into the phone:
In case of Google Play - google play app has installed this app on your phone.
In case of Amazon - Amazon app installed this app to your phone.
In case of installation from APK - Package Manager app has installed it in your phone.
So if you want your app to be listed there - you will have to create an application, which is able to install other applications. It has to be a system app, because only system apps can install other apps.
Solved! Its possible set the name of my app as installer using the installation method implemented in
Split APKs Installer
Related
I have an app that was installed by 800 user by package installer (not google play) but now I will publish this app in Google play with new version code an I want that users update to new version in Google play. How I do it? I made a test with another app and did not occur update.
Google Play will not update apps installed via package installer. You will have to ask your users to re-install from Play by communicating with them.
I have an app installed in multiple devices running 6.0.1 and 5.1. The package name used is com.mycompany.cricket. This application is not available in Play store.
Now today I published the same app with a different package name - com.mycompany.friskies. If I try to install this app from Play Store then, I get "Error Code: -505" and app doesn't get installed.
If I uninstall the app com.mycompany.cricket from my device, then I can install com.mycompany.friskies from Play Store but lof of our clients are already using com.mycompany.cricket, so we can't tell them to uninstall that and install the new app from Play Store. This app (com.mycompany.cricket) is available from the Beta testing platform TestFairy.
Both of these apps are signed using the same release key.
Please help what could be the reason.
I have a application preloaded on ROM, and put it on system app. Current version code is 3. This apk also published on Google Play.
Note : All cases below I use same key store, same package with the apk preloaded on ROM.
* From Android Studio, I build a new version and upgrade version code to 4.
Case 1:
I copy this apk to phone and install manually. Phone display "Can not install". I check the log and it show :
"W/PackageManager: Package xxx signatures do not match the previously installed version; ignoring!"
Case 2:
I uploaded the new apk to Google Play. Google Play accept it normally. After Google approved and published the app, I open Google Play app , find my app and check the status. It displayed "UnInstalled" and "Open".( It should display "Update" but it did not).
Right now I can not update my application. Can anybody tell me what is the reason for this case?
Below is the checklist to update app-
Update will come only if you already have that app installed in
phone as PackageManager checks for that package if it is not same it
will install as new app(not update).
It has to be signed with same key which was used to sign system
app when it was preloaded in ROM.
Version Code has to be increased.
So, I have an app which I am running on real device. When running the app the following dialog is shown.
Clicking Yes is followed by error in Console
- google-play-services_lib] Installation error! The package already exists.
- Launch failed on device:
I have tried uninstalling app from my phone but didn't work.
Any idea how to fix it?
You dont need to reinstall google-play-services. It's updating automatically by Play Market.
I had problems like yours and let me guess:
when you debuging app from eclipse - google play services doesnt sign in, but when u release it and download from play market - it works fine.
If its true, so mark your google-services as a library and delete from "java build path" in your app.
right click on project-> Properties -> Java Build Path -> Projects
Delete google-play-services from there
Now, you have to obtain debug certificate SHA1
in Eclipse go to Window->Preferences
Andoid->Build
(there you can find debug certificate SHA1 for debuging)
Go to Android Developper Console https://play.google.com/apps/publish
Select your game in Play service
Go to "linked applications"
Create a NEW linked application android and put it your debug certificate SHA1
Wait a few to changes be deployed
You will get two similar links, but with different SHA1 ( one for debugging, second for releasing)
Now, you need to clear the Android Application cache before trying to connect
Clear cache of your application
Launch your app
I solved my problem like this
That's caused by attempting to install an apk maybe from the ide with debug keystore on a device that has the production apk with the production keystore. Just go into the phones app settings and uninstall the app. I get a few of these after I test the upgrade path from the beta store and then go back to developing with the ide.
try doing it through command prompt use:
adb uninstall PACKAGE_NAME
and see if it works
also try renaming the package name just to be sure.
I feel you are trying to install google-play-services.You don't need to update google play services.From the docs:
The Google Play services APK
The Google Play services APK contains the individual Google services
and runs as a background service in the Android OS. You interact with
the background service through the client library and the service
carries out the actions on your behalf. An easy-to-use authorization
flow is also provided to gain access to the each Google service, which
provides consistency for both you and your users.
The Google Play services APK is delivered through the Google Play
Store, so updates to the services are not dependent on carrier or OEM
system image updates. In general, devices running Android 2.3
(Gingerbread) or later and have the Google Play Store app installed
receive updates within a few days. This allows you to use the newest
APIs in Google Play services and reach most of the devices in the
Android ecosystem (devices older than Android 2.3 or devices without
the Google Play Store app are not supporte
I have my application in Google Play, I've downloaded and installed it on my phone.
I'm also currently working on update of this application, and whenever I want to install my .apk file on my phone it shows me, that I can't do it, because the app is already here.
Where in Eclipse can I set some settings, which will allow me to install my updated app without installing original one?
EDIT
I want to have two versions on my device at the same time.
One simple solution is to change the package name, since that's how the OS identifies the .apk. Indeed, the package is unique to the Market: how does an android phone(or market) recognize an app
You can not install and run the app from eclipse because the app installed on the device (the one from play store) is signed with a different key.
When you export your app you sign the apk with a specific key and when u run it from eclipse you sign it with a different key - the debugkey.
If you HAVE to install another version on the device without uninstalling the old one from the device (the one you got from the play store) you should:
1.export your app and sign it with the same key you signed the app you uploaded to the play store.
2.upload the exported apk to the device.
3.install it.
EDIT:
If you want to versions on the same device you should change the app package name.