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.
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 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 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 have recently developed an Android app that i publish ad i do not see any current installs on my Developer console list.
I already installed on 2 devices. The application is free and i have also a paid version.I already have 3 reviews but no installs are showing...?!
play.google.com/store/apps/details?id=iappz.universalconverterfree
What settings do i still need to do? Is it mandatory to add/set up Google Analytics to track this?
I was under the impression that this is already build-in and a basic install statistics will be already available...
Thank you
How long ago did you release the app? Most of the statistics are usually a few days behind (latest stats I see on my apps are for the 23rd) so you may just need to wait a few days.
The statistics related to the number of installs on the Google Play Console take some time to update. It not like that you install an application and suddenly it will update the console. It will take some time.
My app uses AdMob. My app doesn't contain any inapp purchases. No device is excluded in developer console and devices tested had higher sdk version than minimum required. My app is optimized with proguard and then zipaligned. Users can install other apps without problems. Why are they getting this error? How can I solve it?
Also when trying to install it via browser on a PC? In this case, where does the error occur, on the pc or the mobile device?
Which app is it?
I think Google Play takes random amount of time even after app being published, before it becomes available for download. Same thing happened to other person I know. After few hours of app being published (not app being uploaded) his app could be downloaded. His app could be downloaded before mine even though mine app was uploaded before his.