Develop Reference

Internal app sharing show downloading error | Error retrieving information from server. DF-DFERH-01

I published my app in internal app sharing. After I shared link to download to myself, but to another account. I turn on internal app sharing in Google Play on my phone. When I click downloading, I catch error -> Error retrieving information from server. DF-DFERH-01
I tried to test in two phones, but with same google account.

There is a step I missed - testers have to opt in to the test program before they can use the shared link, and until they do they get the opaque DF-DFERH-01 error. On the Play Console under Release Management, select App releases. In Internal test track, click Manage. Under Manage Testers click the drop arrow. This opens up a panel, and near the bottom is an opt-in URL. Copy this and send it to testers. They have to click on this link and agree to opt in to the test program. They can then download the current version. After this they can also use internal app sharing links for new builds.

In my case, I was trying to access the internally shared debug app not a production testing app. For this, I was using Internal App Sharing feature. To be able to install and use such apps one's email needs to be added to an email-list(as per the settings we had) otherwise, anyone with the link can install.
Problem
The problem is despite having my email in the list, and email representing a google account I was not able to install it. I faced this error.
Click here to see the Screenshot
Cause
I maintain about 8 google accounts on my mobile and I was logged in to all of them. I realized having multiple accounts is causing the issue.
Solution
Instead of logging out from all the google accounts, I simply created a new user in my mobile and set it up. Then I opted-in to Internal App Sharing in the App store. Then shared the app link via google-keep. Voila, I was able to install it.

In my case I just had to wait ~48 hours and it Just Worked with no other changes.

A few more silly things to consider if you are new to Google Play Console.
You need to make sure to enable Internal App Sharing on Google Play Settings, here is a tutorial for that.
Do not forget to publish your modifications by clicking on publication overview (sorry for the Portuguese language on the pic, but you can find through the icon):
And then publishing it by clicking on the blue button (publish modifications or something like that):
After doing this, try to clean the cache of your play store and remove all updates from play store (after doing this you'll need to enable Internal App Sharing again).

I was able to get rid of the error by clearing the storage of the google play store app then open the play store app again and enabling the internal app feature then opening the internal app sharing link again.
sometimes if that didn't work , restarting the device does the trick!

Accessing future Google-Play URL for app before pubhlishing

I am developing an application in which the user has the opportunity to share some data to facebook.
In this data that will be shared, a link to the application is provided.
However, the application is obviously not yet published yet. So I have had to "guess" what the URL will be. I have set it in this format:
https://play.google.com/store/apps/details?id=com.mycompanyname.appname ,
where mycompanyname is my name, and appname is my application name (i.e. using my real bundle id, or packet name). This is is the suggested way according to the answer to this question.
Now, my question is simply if there is this a proper way of doing this without assuming the link will always be the same? I do not want to risk publishing an app with a link that doesn't lead anywhere. Can I instead add some kind of placeholder that will automatically change to the actual play store URL?

Google play link always contains your package name after [id=]
https://play.google.com/store/apps/details?id=yourpackagename
Because on google play package name is unique for the same app, you can't find two apps with the same package name.
So it's ok to publish your app like you said, also if there anything wrong for any reason you can always update your published APK without any problem.
So you can for sure publish your app with it's link without no problem.

App updates in different appstores

I uploaded my app in Google Playstore. So, there are other third party appstores(side-loaded) like Appbrain, which automatically pull apps from Google Play store. My queries are:
Will my app get updated automatically in those markets, when I update it in Google Playstore? If yes, how long it takes to get updated?
I programmatically check my app version every time(I don't want users to use old version) and take user to Google Play store asking to update my app. So, if user downloaded my app from any other store, how to take him to the corresponding one to update the app or is it ok to take him to Google Play Store irrespective of where it is downloaded from?
Edit:
After going through documentation, getInstallerPackageName() gives package name of installer.
startActivity(new Intent(Intent.ACTION_VIEW, Uri
.parse("market://details?id="
+ appPackageName)));
So the above code takes user to my app's screen in GooglePlaystore as appPackageName is passed. So, even knowing installer's package name wouldn't help as I can't send user to the same screen.

According to the User FAQ on Appbrain in the Copyright infringement question:
AppBrain extracts content from the Android market. ... As soon as Google removes the app from the Android market, it should also be gone from AppBrain in the next 5-7 days.
So the sync time is around 5-7 days. I think other third-party stores should require the same amount of time to sync their store.
I think it is a good idea to direct your users to Google Play as it is the up-to-date, official source. Also if you notify your user of the new version, he/she may still choose to dismiss your notification/dialog window and use his/her preferred third-party source to install the update. Anyways if you get the package name for the installer app, you may create an Intent which can be caught by that app. (e.g Samsung Galaxy Apps store should/will handle any URL intent pointing to an app within it: http://apps.samsung.com/mars/topApps/topAppsDetail.as?productId=000000660227)

AppBrain only lists your app information (description, screenshots), it does not provide the APK file.
For downloading the app it links directly to the latest version in Google Play.
To update the app description on AppBrain or to add a new app you go here:
http://www.appbrain.com/info/addapp

I cannot find my app on Google Play with app name. I can find using package name

I have uploaded an app on Google Play "First Steps" two days back. When I try to find the app on Google Play using the name, I cannot find it. The package name is com.systology.firststeps. Using "systology", I am able to find it.
I gave the app name properly in Google Console. Also, in description, I have put the app name.
Can someone help in telling me what am I missing on?
Thank you

As you have given the name of your application First Steps so the google will always look for the first word to search for and will give you the result according to the first word of your application which matches the most of the application's on the playstore.
If you want to get the exact result of your application on play store you will have write First Step Systology then you will get your application only.
Check out https://play.google.com/store/search?q=First%20Steps%20systology&c=apps

Google Play Alpha App BM-PPH-01 Error

I have an app that I am making and have uploaded to the Google Play through my console and would like some people to test it.
I have created a Google Group and also added a different account for myself but get the following error:
BM-PPH-01
Has anyone else seen or know what this means?

I had the same problem after paying for an app and after that the download process didn't start.
My solution:
I visited the http://play.google.com/ website through my PC, searched for the app and selected the target device through the install-button.

BM-PPH-01 error message is usually shown when there is an incompatibility between any of the three App,Google Pay, Device.
The incompatibility can be the device's location such as Google play features not available when device is in China . An app can be restricted for downloading in US only.
The following links might provide some insights about this problem and possible workarounds.
http://forum.xda-developers.com/showthread.php?t=2181359
http://codekiem.com/2013/02/13/market-helper/

I just now received the same error code [BM-PPH-01] when trying to push a paid app from the Play Store using my desktop web browser to my compatible mobile device.
As a workaround I was able to visit the Play store from my compatible mobile device - the app began downloading as soon as I opened the Play Store app. I had planned to click the app's Install button from the Play Store app but didn't need to.

I think I found the solution.
Change your main address in Google Wallet according to the country whose store your are trying to buy/download.
Ex: I was trying to download a film using the German store but my main Google wallet address was set to Portugl. I changed the address and now it works.