This is possibly not a duplication. I have tried to find the solution. However I could not find any. My aim was to publish a private app in Google Play. What I have done is,
register an enterprise user https://enterprise.google.com/android/experience
Add user.
Get the Organization ID
Publish the app from Google Play using the Organization ID from "Pricing and Distribution" (since it was the same user (developer and enterprise), I just had to select that company).
The app was published and it was being shown in the app list in enterprise account
But the problem is, when I go to the work profile from the device. That app is not in the list of apps in the work profile.
** the app was published one day ago.
** the app has been enabled in enterprise account 4 hours ago.
** the app is just a sample app with blank activity.
You get Google Play store app in work profile apps list. So you need to open it and search there you will get your published app for installation.
And also your app is not visible directly in the work profile app list because, I guess you set the Auto install option false while setting up apps for organisations.
See the attached image, you need to enable the Auto-Install option enable to get it.
Related
Google Play has something called Private Apps: https://support.google.com/googleplay/work/answer/6145139?hl=en
However, to my understanding this means that only members of my organization can install the app. It doesn't say what "organization" mean but I assume it's members of a Google Workspace or a specific email domain.
I want to achieve something similar to Apples "Unlisted apps": https://developer.apple.com/support/unlisted-app-distribution
This means the app is present on the Appstore, but it's not listed or searchable. Only if you have the link to the app you can download it, and the user will receive automatic updates.
Is there something similar on Google Play? I want to distribute and update the app via Google Play, but only to users that I share the url with.
You can publish the app on the Google Play store via the Play Console and while selecting where to launch (publish) the app, add the app/app bundle only to the closed testing option. There you can add specific email ids and only those will be able to see the app, get updates, etc. no one else.
we use internal testing on playstore to test the app internally before we move to closed and open beta. More details can be access in the below link
https://support.google.com/googleplay/android-developer/answer/9845334?hl=en
I have an app on Google Play Console. Atm the testing method is set to Closed Beta Testing and we have a list of users to test it. Looks like this:
I have my mail in the list of testers and shared myself a link. When I follow it, this page is presented:
When I follow the link, I can see the app on Google Play. The page contains also 2 messages:
Your administrator has not given you access to this item
You're a beta tester for this app. Future updates will include beta versions
There is no install button. As I understand, the issue is with the first message about access. How can I fix it?
This error message is displayed if you're using Managed Google Play to distribute your app privately, targeting it to organisations - this can be verified by navigating to Store Presence > Pricing & distribution > User programs. When distributing a private app using a closed track you also have to add the organisations under the "Manage testers" section - these aren't automatically added when you create a track.
We recently released an app on google play and after a couple of beta versions I moved it from beta to production. However, some people cannot download the app. Here is an example from Vietnam:
I don't know Vietnamese, but I asked a colleague to translate it and it says:
"Another account, {{email}}, has joined the beta program of this app. The updates for this app could include many beta versions."
Does anybody know how to solve this?
Google Play Store seems to store the application and user account association information in the device's local storage. Clearing the data of the Google Play Store from its app info page should do the trick. Now simply switch the the account that you have joined the beta program with and you should be able to install / update the restricted app version.
If it still doesn't work, repeat the process but this time reboot the device.
Another option is to install the app remotely through google play's website. First remove the app from the device, visit the site with the required google account and install the app in the device of your choice remotely.
This should not block updates, it should only be a warning. The English version of the message is "Another account on this device, XXXX, joined this app’s beta program. Updates to this app might include beta versions."
(Good translation by your colleague).
This is a device with more than one gmail account associated with Google Play. It is probably either shared by multiple people or the user has multiple gmail addresses.
An android device can only ever have one version of an APK (with the same package name) on it installed at once, even with multiple users.
The warning is saying that the current account looking for an update is not enrolled in the beta program for the app. However, another account on the device is enrolled in the beta program. This means if this user does an update, they might get a beta version of the app (as the upgrade as to be appropriate for the other user too). The warning is displayed so the user doesn't unexpectedly get a beta version.
However, it should only be a warning, it shouldn't stop the user updating.
There's a way to bypass this guys, should you want to install the application. On the app list when you search for the desired application, click on the "..." symbol at the upper right corner of the application, there is an "Install" option for you.
There is a button on left top corner, for google play store options. There, change the user to a the one they say that can use the program (different e-mail adress), and you will be able to download the required app.
I have an unpublished app on Google Play which I want to update for my existing users, but not let new users download it.
The Google Play documentation seems to be saying that this can be done by simply uploading an updated apk (and not re-publishing the app):
Unpublished Apps
Existing app users will still be able to receive app updates, even if you unpublish your app. If you don't want new users to find and download your app but still want to provide updates to your existing users, set your app to Unpublished in the Developer Console.
https://support.google.com/googleplay/android-developer/answer/113476?hl=en
But it seems unintuitive that an "unpublished" application would work that way. If the documentation is correct, how does Google Play tell the difference between an 'existing' user and a 'new' user?
Just a follow up: pushing an update to the unpublished app does make the update available to existing users only, but the app does not update automatically for these users. They must browse to the app page, where the app will have an "Update" button which can be triggered manually.
(This is just speculation, I'm not affiliated with Google in any way or anything)
The existing user probably has the app associated with the Google account they use to log in to the Play store.
If you look at your own profile in the store, there's a list of all the apps you've ever installed. I'm guessing the update would be available only for people who have your app in their lists, and the app will still be invisible for new users.
Whenever a user that has the app installed wants to update it, he requests an update of the app, it's different from re-installing the app as data from the app (a save from a game, or some saved preferences etc) are kept untouched, google play can easily detect that since it can detect what apps you have installed.
I have uploaded android apps using my google play developer account abc#example.com, now I wanted give access to user xyz#example.com as guest user .means he can see data app stats, crash reports, or active installs pie chart, etc. but cannot able add new app or not able to add update of the app. Anyone have an idea how does do it?
or
anyone have an idea how can I access my android app stats information. does google api is useful for this.
Currently, the Android Console does not offer any fine graining on what guest can do on the console. You may have to look into app tracking services like App Annie which could provide statistic info without allowing the user to upload a new version to your app. Altough it would be impossible for another user to update a new version of your app without having access to your developer certificate.