I want to know how uninstalls on my app are recorded on the Google Play console exactly. I do not want my own personal uninstalls on my test devices to show, so I want to find out how the uninstalls work, in order to block them.
When testing an app on Android Studio over and over are those updates/uninstalls recorded on the Google Play console? If I install the app using an external APK and not through the store, do uninstalls of those get recorded?
Thanks.
P.S. I have tried googling this question but the problem is I could not find any relevant answers. Three hours after searching and still cannot find an answer.
You cannot detect the uninstall event of your own app. When an app is uninstalled the event ACTION_PACKAGE_REMOVED is sent as a broadcast to all apps except the app which is being uninstalled.
So to answer your question, Google console calculates the number of uninstalls via Google Play Store app, not via your own app.
Also, Google Play store only tracks the install and uninstall events for the apps which are installed from the Play store. So, if you want to block the uninstalls from your test devices from being counted, install the APK directly and not from the play store.
Maybe I have not been able to find exact documentation of your problem but you don't need to worry as it is sure that Google will not count installs or uninstall of your debug/signed apk if you install it manually or from Android studio.
It counts the number of installs or uninstalls of your application only if you download the app from Google Play Store.
Recently google changed the way of calculations, so you can find here how it's performing.
Related
I have an app that is released only as an "internal test" on the Google Play store
When I go to the Google Play store on my phone, the app does not show up at all, under "installed" or "updates" or any other tab
When I click the 'internal testing' link (the one that Google Play Console says to give to internal testers), it opens Google Play and shows my app's store page. The store page shows the correct latest version, but I'm unable to install it. My only options are "uninstall" and "open" (which opens the currently installed old version of the app)
I have "enable auto-update" enabled from the Google Play store page
I've waited two days
I've made sure the app is closed completely on the phone
As far as I can tell, there's no way to update the app without uninstalling it, which deletes all the app data. How can my testers update the app?
Updating seems to be broken for apps that Google has not reviewed yet, which they don't do for internal apps.
I released the app to closed beta, causing Google to review it, and stopped using "internal releases" altogether. I'm not sure which of the two was the fix, but now auto updates work.
I think I've found a workaround. It's now worked 3 times out of 3, so fingers crossed.
First, uninstall whatever version you have on your device.
Then visit the link provided from Google Play Console on a PC instead, and from there you click the 'If you don’t have the app installed, download it on Google Play.'-link.
Once there, press install, and choose your device.
This way, the latest version of the app is installed on your device, and not some random version; like seems to be the case, using the Play Store on the device.
Not ideal, but it works :)
Requirements for getting the Internal Update on Play store
Add your same email Account in internal testing which you used as in play store.
Join Beta Testing program which will be visible when you search the same app on play store.
Turn on internal-app-sharing on playstore - > PlayStore->Setting->About ->PlayStore-version(press 7 times), Turn On Internal App Sharing in General Settings of play store.
Wait for some days & Get the app link from play store console to get the update version
i made app and build it as an apk file in flutter and i tried to install it in my android phone but while installing it, play store said: the app is unkhown do you wanna install,
and then i installed the app and app was working well, the question is how i can solve it, Do i have to buy a play store account? or there is another way to solve it.
If you intend to make the app available to play store users then you need to create a play store account. Normally the warning that you received if from Android OS telling the user that the app can't not be trusted, since it does not come from the play store but yourself built it. You can ignore this "warning" for now.
The warning will not be shown to the users when the app is built, signed and uploaded to play store.
You should refer to the official documentation to know how to sign and publish your binary file to the Play Store.
You'll need 25$ to create the Play Store developer account (available for your entire lifetime) and a bit of reading from the official documentation
I want to know how uninstalls on my app are recorded on the Google Play console exactly. I do not want my own personal uninstalls on my test devices to show, so I want to find out how the uninstalls work, in order to block them.
When testing an app on Android Studio over and over are those updates/uninstalls recorded on the Google Play console? If I install the app using an external APK and not through the store, do uninstalls of those get recorded?
Thanks.
P.S. I have tried googling this question but the problem is I could not find any relevant answers. Three hours after searching and still cannot find an answer.
You cannot detect the uninstall event of your own app. When an app is uninstalled the event ACTION_PACKAGE_REMOVED is sent as a broadcast to all apps except the app which is being uninstalled.
So to answer your question, Google console calculates the number of uninstalls via Google Play Store app, not via your own app.
Also, Google Play store only tracks the install and uninstall events for the apps which are installed from the Play store. So, if you want to block the uninstalls from your test devices from being counted, install the APK directly and not from the play store.
Maybe I have not been able to find exact documentation of your problem but you don't need to worry as it is sure that Google will not count installs or uninstall of your debug/signed apk if you install it manually or from Android studio.
It counts the number of installs or uninstalls of your application only if you download the app from Google Play Store.
Recently google changed the way of calculations, so you can find here how it's performing.
I'm developing an application on Android Studios that is already linked to the Google Play Console. During development, I am constantly uninstalling and reinstalling my application and writing experimental code that at times crashes my app. These crash statistics seem to show up on the google play console statistics. Could someone verify if that is indeed correct? Also does the uninstall count get ticked up every time I uninstall the application from my phone during development?
I hope my question is clear, haven't been able to find anything that speaks specifically to whether or not statistics are affected when developing an Application on android studios that is already linked to the play store.
I'd be happy to clarify anything that is unclear.
Thanks!
Installs and uninstalls from Google Play will still count. Installs and Uninstalls from Android Studio don't.
Crash statistics from Android Studio installs do show up right now, but should stop soon - this is an error in the Play console.
My company would like to give an Android device to a group of our selected customers.
Doing that, we would like to provide users with our mobile app. The app is already on Google Play, but we would like to avoid users downloading and installing by themselves. We prefer to give the device ready, with the app already installed.
We found several ways to manually install an APK on the phone without having to login to the market. But it seems that doing that, the user will not be able to update the app via Google Play, as the app would not be recognized as installed.
Any idea?
As per January 2015, this appears to be impossible. Here is the response I got from Google Play Developer support:
Side-loaded apps do not update via the Play Store. If you would like the app to update, you will need to uninstall the app on your phone and reinstall the app via the Play Store.
I wonder if anyone found a way around this?
To summarize the answer from #Android-Developer and OP's comment discussion:
Google Play recognizes the app signature of APKs regardless of the installation source. As long as you use the same package name and keystore when generating your APK, Google Play will be able to detect newer versions and trigger an update.
To install the app without logging in to a Google account, enable the "Install from unknown sources" option in Settings. You can disable it once the installation is complete.
You may install Titanium Backup if your phone is rooted, then long press on your side loaded app package and select "Attach to market" option. Now you may receive updates via Google Play.
I don't recommend this, I mean never install cracked or patched apps because of copyright or security risks, but installing a Modded version of Google Play can make patched side loaded apps to be upgraded after attaching them to market via Titanium Backup. This is not needed for purchased apps because they are registered in your Google account, so attaching to market will be enough.
To get a MANUALLY INSTALLED APK to show up in the Google Play Store in the UPDATES or INSTALLED section, do either of the following:
1.) Manually install the APK with the SAME APK filename that Google knows the app as (i.e. from the APK download site like APKMirror.com).
2.) If you CHANGED the APK name when you saved it, it will NOT show up in Google Play Store as an installed app.
However, IF there is an update to the app, you will have to do a ONE-TIME search for that app in the store and update it. It will give you the UPDATE option on the app's store page. Once updated via the store, it will show up in the store's Installed / Updates section from now on.
Why does this work? Because the UPDATE will be done thru the store and the APK name it's using during the update process is what Google knows the app as.
If there is NO update, do option #1.
I always add the App name and version info to the front of the filename so I know what it is for later use (because if I'm manually installing, I'll probably be saving it for multiple / future devices).
I also keep the original name at the end, so I can rename it back to the original name if needed. Android is the only O/S I've seen where the filename matters during the install process.