Develop Reference

Unable to See the Internal/Alpha app listing on Play Store

Problem Statement
I have setup my already published app for an internal test track according to the instructions provided by Google. However, I do get redirected to the page as shown in the image below. When I click on download it on Google Play, I am always redirected to the public version of my app instead of the internal testing version.
Background
I have introduced a functionality in the app that redirects the user to update the app. Prior to releasing to production, I would like to test this functionality with a group of internal testers.
What I've already tried
I have setup the testing users correctly by creating a list of such users.
I have referred to this question and have completed all the steps of publishing and shared the opt-in URL with my testers.
I have also referred to this question and have waited for multiple hours, as well as cleared Play Services/Browser cache on the devices that have the invited testing account set as the primary account
What I really want
What I would like to happen is to gain access to the Play Store listing page of the internal testing app and redirect to it from another build so that it can be ensured that after the update, the app works as required.

I'm not sure exactly what you mean. The listing for your internal version of your app is exactly the same as the listing for your public version. The user gets a small notification "you are a Beta user", but that's the only difference.
What do you expect different in the Internal listing?

My internal test version became visible on Play Store after 72 hours, which seems to be far too long for an app that has been in the market since the last 1.5 years. The answer provided by Nick Fortescue is correct in essence since I was expecting a different channel where I could access the internal test build.

Is it possible to just 'hide' an app from the All Applications list in Google Play Console?

I'm currently working on the Android version of an iPhone app.
It's my first time using Android Studio, the Google Play Console, battling Gradle, etc and because of this inexperience I accidentally published the app for a brief period (less than an hour) and have since unpublished it. It was not downloaded by anyone in that period.
I understand from these questions (1, 2, 3, 4) that it is not possible to delete an app that has been published.
I also checked Google Play Console's help pages, but there was no indication either way on whether hiding an app was possible.
However, since it can't be deleted, is there a way (official or otherwise) to just hide it from the Google Play Console list?

You can put your app in a close test, only e-mail that you give access will be able to download.
Today you have 4 types of App Releases in Google Play:
Production: when you real release the app for everybody;
Beta: App is not ready, open test;
Alpha: App is not ready, close test;
Internal Test: App is not ready, "close test";
In your case you can use Alpha or Internal Test.
Internal Test should be use for company test, it is launch very fast and work for marketing people download, you boss or some testers.
Alpha it should be more like you have a group of "trust" users that will like to test your app.
In both cases you need to create a list of gmail accounts, so it is not open for public yet.
You can read more here

This is not currently possible. However, if you are really bothered, there is one way you could do it. Google offers the ability to do "App transfers" (instructions).
This is typically used when one company sells an app to another. But you could create a new developer account and transfer the app to that account, which would get it out of your list. But it probably isn't worth it.

App cannot be downloaded from Google Play because "another account has joined the beta program"

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.

No automatic update of my launcher app

I make an Android launcher app and I published this app in the store.
The problem is it seem the people don't receive the update of the app automatically...
They have to go to the store and click to the update button.
It's the same when Sync is enabled in settings & background Data is not restricted.
Maybe because it's a launcher and the Google Play Store doesn't update the app who are being used (to not reload it) ?

Google Play can take upto 24 hours to push application updates across all its servers.
Just wait for a while, and all your eligible users should receive the update. However, if your update adds feature requests that some devices don't support, they will not get the update. And one more thing you must make sure that the app u have installed in ur mobile is not apk built with debug keystore.. the play store will show always as "Open" button instead of "Update" if the play store app certificate doesn't match with installed app certificate. I realized this when i did trial and error with debug and signed apk's. Only signed apk worked. And use versionCode for comparing versions instead of version Name.

Google Play - update an unpublished app for existing users but not new users?

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.