Related
I am trying to upload my app using internal app sharing last 2 days, but no matter what I do, I cant make it work. This is what I did:
In Console I clicked on app -> release -> internal app sharing
I uploaded apk
I added myself into email list both UPLOADERS AND TESTERS (1st tab) and also EMAIL LISTS -> Downloaders (2nd tab)
I even enabled "Anyone you shared the link with can download"
Here is how it looks in the console.
APK was sucessfully uploaded, and then I copied the link and saved it to Google Keep.
Then I try to open the link on my phone, I click on link, it opens webpage displaying this and when I click on "OPEN IN PLAY STORE", it just takes me to Play Store, but there is only official version available (not the internal version I uploaded).
Am I doing anything wrong? I try almost 2 days to make a simply thing like this work, and it is very frustrating...
Nothing we can do right now - Internal app sharing seems to be totally broken at the moment. Great work Google
You need to turn on the option to use Internal App Sharing in the Google Play app on your phone.
Look under the heading How authorized testers turn on internal app sharing
Before authorized testers can download apps using internal app sharing, they need to turn on internal app sharing on their Google Play Store app.
Open the Google Play Store app Google Play.
Tap Menu Menu > Settings.
In the “About” section, tap the Play Store version 7 times.
After the Internal app sharing setting appears, tap the switch to turn on internal app sharing.
Tap Turn on.
(Note that in 4. above, the option may appear under the "User Controls" section)
Here is something I just noticed. In other words, it might not be applicable to your specific case.
I uploaded my app's aab file to "Internal app sharing". This is something I've done many times in the past, so I expected no surprises. After uploading, I sent the link to my phone and opened it from the phone. Google Play showed up, but it was stuck with the spinning wheel forever. Uploaded the aab file again, and stuck again.
Then I tried previous uploads in "Internal app sharing" one at a time. The one from a few weeks ago worked, but none of the more recent ones did. I'm not entirely sure what happened between a few weeks ago and now, but I couldn't think of anything particular that might be the cause of the problem.
Then I uploaded from a different account that is registered as one of the uploaders. The file uploaded from the secondary account worked. I uploaded the same aab file from my primary account, and now it started to work as well. The links that didn't work before still didn't work.
I'm not sure uploading from a different account has anything to do with it, or perhaps it was just a coincidence, but if you are desperate, you might want to try.
Just want to share my 'misunderstanding' about Internal app sharing.
internal app sharing is different with internal testing.
both have different menu email listing too.
internal app sharing on Setup > Internal app sharing :
internal testing on Testing > Internal testing :
In my case, i have setup testers list on internal testing, but not yet in internal app sharing. The link from internal app sharing not work. After added email list on internal app sharing, the link work and can install from it.
hope it's help.
First Method
I have tried both Internal Testing & Internal App Sharing, both Tester link doesn't work for me, getting
'Can't download the app..Try again and if it still doesn't work, see
common ways to fix the problem'
Turn on Internal App Sharing in playstore, i have followed the steps in below link Google Play not updating internal app automatically
Alternalte Method to test Application for both watch and phone
Install 'Wear Installer' app on watch & phone.
Turn on Developer Options in watch.(Settings->About->build number(press four times)).
Turn on Debug over Wifi.(Settings-> Developer Options-> Turn on Debug over Wifi)
Link to install from phone - https://play.google.com/store/apps/details?id=org.freepoc.wearinstaller&hl=en_IN&gl=US
Open the 'Wear Installer' app on watch, it will show you the IP Address.
Open the 'Wear Installer' app from phone and add the watch IP Address.
Select the watch apk in the phone in Downloads of 'Wear Installer'.
It will start connecting to watch & press 'Allow Debugging from this device' in watch.
Watch will be connected with phone.
enter image description hereClick install in 'Wear Installer' in phone.
Apk will get installed in watch.
I think issue is you open internal app sharing url in google chrome. try to open url with google app with this link https://play.google.com/store/apps/details?id=com.google.android.googlequicksearchbox
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!
The Google Play Developer Console offers the Tracked Channels (UTM) view under User Acquisition → Performance which should be able to show a breakdown of which tagged links users clicked to get to the store listing, etc.
I have generated several different links to my app using the Google Play URL Builder, e.g.:
https://play.google.com/store/apps/details?id=com.vandenmars.colortrek&referrer=utm_source%3Dso%26utm_medium%3Dlink%26utm_campaign%3Dlink%26utm_content%3DTBk
I did a couple of tests last week where I opened the Play Store using these links and installed the app on new devices immediately from there. Still, the Tracked Channels (UTM) list shows no entries.
A bit more background that may be relevant:
My app itself does not use the Google Analytics SDK and does not register a receiver for the INSTALL_REFERRER intentI would assume that the Play Store handles the links directly without requiring app interaction, especially since it can track store listing views that don't lead to installs, but maybe this is incorrect? Or maybe the store disables tracking based on the app manifest?
I opened the links in Chrome on my PC and clicked "Install" thereMaybe the links only get tracked if they are opened in the Play Store App on the actual device? Seems strange, but I am running a test on that right now, the data just hasn't updated yet.
The tagged installations I did were on days that have been processed alreadyIt sometimes takes Google a long time to update the "Performance" data, but the data I can see already includes this Sunday and the tests were done on Friday. So, unless the UTM tracking data takes even longer to get processed, it should already show up.
Do I need to enable something somewhere for this to work? Or am I doing something else wrong?
UPDATE 1:
Meanwhile, one entry has started showing up in the Tracked Channels (UTM) list. Unfortunately, as the help-text states, "UTM-tagged links that have a single store listing visitor [...] are included in the “Other” category." So I have no idea which of my test links it is, if any. The entry is only showing as a Store Listing Visitor, but not as an Installer.
The last day included in the stats is Wednesday (supposedly), which is also the day when I did the test of opening the link directly in the Play Store app on a device for the first time. I did install the app during that visit, but it was after I had uninstalled a previous installation.
So, here's what I learned from this:
It doesn't look like there is some on/off switch for UTM tagging that I need to enable.
Including the Analytics SDK and registering an INSTALL_REFERRER is not strictly needed for just the tracking of Store Listing Visitors, but it might be needed to track Installers/Buyers.
There may be a difference between visits to tagged links from a PC vs. from the Play Store app on a device.
This leaves the following questions:
Are UTM links only tracked by the Play Store app, or also by visits to http://play.google.com/...?
Does an app need to use the Analytics SDK to forward information about installs and purchases to the Play Store, or do these get tracked independently of the app like the store listing visitors?
Is only the first installation of an app on a specific device counted under Installers, or is a fresh install after an uninstall also counted? How about after a factory reset of the device?
Bonus question: Is there a way to expand the "Other" category? :)
UPDATE 2:
Now I'm back to square one: 3 days ago, I opened more test-links on different devices (including the one that I thought was the one that showed up last time), directly in the app store, installing the app immediately. The data shown includes everything up to and including two days ago, so these visits and installs should be tracked by now. Yet, the list does not show any additional entries beyond the one from update 1 above.
So, either I have absolutely no clue what should be going on, or this whole tracking system is one giant buggy mess... Some things I've read in random forums suggest the latter, but maybe I am missing something, too?
UPDATE 3:
This is getting stranger and stranger. Now, all of a sudden, I see an entry showing 14 store visits and 10 installs for "zedge/android"! Why would someone make their own utm tagged link for my app?!? On top of that, none of my other tests have ever shown up (still just the original entry under "Other") and I don't even see the 10 installs in the statistics... Looks like this whole thing is just plain broken... Correction welcome.
We're in the same situation too now. No Google Analytics set up, need to run some ads this weekend, so I'm going to try to use UTM tags to track the app installs.
There may be a difference between visits to tagged links from a PC vs.
from the Play Store app on a device.
Found this in their documentation
"Note: Over-the-air and web (play.google.com) impressions aren’t
tracked on your app’s User Acquisition page at this time."
If you want, send the link over and I can test it out.
Before direct user to Google Play app page, send GET request with UTM params to your own site. Register this site to Google Analitics. It will count page visits only.
I am going through the same problem. I wanted to test if the UTM source and UTM campaign from the new Dashboard required some SDK or API installed in the app itself. So I contacted Google Play Devs, I asked specifically if we needed Google Analytics and their response was:
this not the case and also there is nothing further that you can add to the app itself.
I did try downloading my own app and sent the link over to a couple of dozen people (bare in mind that the app does have a Google Analytics setup, but it is from 2016, so old version) with the following link
Power my Robot with UTM links setup
I put random words, and all the visits and downloads on both UTM Campaign and UTM Source showed under "Other" and not the words I put. I managed to get around 20 downloads from this link.
However, after questioning Google why it was showing under "Other" and not the word I put in the link, they said it is because of a minimum threshold, which they don't know the amount.
As mentioned above, I used this form to get the Google Play with the UTM tags.
And also, I agree with a comment above, that Apple simply works. From the campaign section in the dashboard, you can open the "Link Generator" and they specifically say that the minimum amount in order to show the number is at least 5 installs using the link in order to protect users' privacy. Google Play can learn something from Apple in this case.
I will try to keep this updated if anything changes on my stats. And feel free to click on the link above and install the app, open and then de-install, just to build up the numbers and see if I can cross the threshold and discover what is the minimum amount they require.
I confirm that the Google Play Store UTM tracking doesn't work with your configuration, as I have the same (no Google Analytics SDK, but firebase-core) and I can't see any installation listed in the Acquisition view of the Play Store.
I note that the Play Store documentation part about UTM tag has a link to an url builder on the Google Analytics Guide, so may be the solution in to install GA SDK.
Have found google page that suggest how to build url with utms: https://developers.google.com/analytics/devguides/collection/android/v4/campaigns?hl=es#google-play-url-builder
This is an example:
https://play.google.com/store/apps/details?id={application_id}&referrer=utm_source%3D{source_id}%26utm_medium%3D{medium}%26utm_term%3D{term}
I have published my app for alpha testing, but not able to download it from play store.
I have opened the url "https://play.google.com/apps/testing/com.*" and accepted to be a tester and now it shows me "you are a tester". But when I click on the link "download it from the Play Store", it shows me "Item not found" in my test device play store and "requested URL was not found" in desktop browser.
App is in published state for more than 48 hours.
App is published in all countries.
google groups for testers are added, I can see the group in manage testers tab. Tester account is added to the group ( triple checked it)
test device has only one tester account.
I can access the in-app purchases, which means the app is published properly. Google doesn't support draft mode anymore.
I went through some similar posts in stackoverflow, but there is no definite answer. Looks like for some people it resolved automatically and some people are not lucky enough.
If the app is "Published", but when you click in "View in play store" the site (example: https://play.google.com/store/apps/details?id=com.companyname.appname) show the error:
"We're sorry, the requested URL was not found on this server",
try this:
In "Google Play Console" (https://play.google.com/apps/publish), select your app
goto menu: Release management / App releases
In Aplha, click in the button "Manage Alpha"
Click in "Manage testers" and copy the link "Opt-in URL" (example: https://play.google.com/apps/testing/com.companyname.appname)
Send this link to your alpha users, you and the users need to click in "Became a tester" before access the app in PlayStore.
After this, open the link of app in play store again (View in play store) logged with a user from the testers list.
If the url still don't open, try close your browser, or clear the browser cache and try again. The browser store a cache of redirects.
If you are using Chrome, then it caches redirects. To fix it, clear browsing data. More details on this
In my case, the issue was that I wasn't logged to Google with the proper account in Chrome.
I cleared all browsing data, but un-logging from Gmail/Google and re-logging with the proper #gmail.com account would probably have done the trick.
Another thing to check is whether or not Pricing & Distribution -> Only make this application available to my organization is checked. It seems that this doesn't interact well with Alpha- or Beta-only tests, even if your test account is in the given domain. Once I turned this flag off, my beta-only app became visible via the Play Store link from the testing signup page.
In addition to all the great answers here, I just found out that if you did an internal test before the closed (alpha) test, the Play Store may want you to use the internal test URL instead.
So say you have your great app and you released it to the internal test track. You created a list called "Internal Testers" for that track and it all went swimmingly. When you did this, Google Play gives you a URL for those testers of the form https://play.google.com/apps/internaltest/{id}. Your internal testers joined the program using that URL, downloaded the app no problem and the test went through.
You now upgrade to the closed track (alpha testing). You create a new list called "Alpha Testers" with new people in it and you enable your release both for "Internal Testers" and "Alpha Testers" thinking that you should carry over your internal testers to alpha. When you do this, Google Play gives you a URL of the form https://play.google.com/apps/testing/{package}. Your alpha testers can now join the program using that URL and download the app. But your internal testers have to keep using the internal test URL to join the program.
From testing a variety of scenarios, it looks like moving a tester from on list to another doesn't fix the problem.
As far as I can tell the Google Play documentation doesn't mention any of this.
Where you add groups for test - there have a link for tester (something like terms) you need to click this link on each testing device and say "Yes"
After that link apear in market. I wait 3 days before found it : )
For my part it was due to the fact that I sent the link through SMS. It worked when I sent it by email. This link has the form https://play.google.com/apps/testing/com.*. This is this link that you have to share by email.
This can be due to a silly mistake where you aren't signed in with the appropriate Google Play account in your device's Google Play Store.
Sign in with the testing gmail account into Google Play and then click on the test-link
For more detail check Item not found
allow access to
Settings -> internal access -> Manage users with download rights later
Settings -> Internal Access -> Testers
and the app link will work
I had this similar issue.In my case, I had multiple testers as CSV and there was an space between multiple users tester.Space was the issue in email address.Bad email address may cause this problem.
Also, make sure the device you are using is among the supported devices for your app. For this, check Release management -> Device catalog on play console.
If this is the problem, expect to see a warning similar to the app is not compatible with your device when you visit play store page via a web browser and Item not found error via play store app.
In my case, I had to make some changes in the Manifest to correct the list of supported devices. So, I replaced below line causing the number of supported devices to be 0:
<uses-feature android:name="android.hardware.camera2.full" />
with:
<uses-feature android:name="android.hardware.camera2.full" android:required="false" />
In your case, Manifest may need a different change of course.
In case someone has tried the several suggestions and has not worked, I want to share another situation I haven't seen listed anywhere else.
Make sure the latest build uploaded is not deactivated. The Play Store console doesn't warn you if, for any reason, the release is made unavailable to your testers. It'll show with a greyed out row, like this:
Check on App releases > Manage, in you track dashboard, that the latest build is Added, not Deactivated.
In my case is Android Studio emulator, I relaunch play store after few minutes googling, then no more such error "Item not found".
In my case the emulator had been started a couple of months ago and perhaps cached something wrong.
I kept receiving BillingClient.BillingResponse.ERROR resulting in this message.
After restarting the emulator it started working again.
Simple way is to use incognito mode. Thats it.
I made my test account to be synced in my device and ready to test the app.
While I am about to purchase the product in my app the google play prompts me to continue after entering credit card details.
After entering details of the card in the device it is showing error as
Error while retrieving information from the server [RPC:s-7:AEC-0]
I am using Google play version 3.10.9
And i already tried to uninstall the update of google play removing my account and rebooting device but no use found the same error again and again could any one help me out of this
Check if you are using latest version of Google Play.
OR
Following the steps below.
RPC:AEC:0 error is known as CPU/RAM/Device/Identity failure.
Only possible way you can follow to get rid off this error is,
Go to settings >application > Play Store >Clear Data & Clear Cache.
Go to accounts >Google >Remove account.
Reboot device.
Again Settings>Account >Google >Log In.
Refer to this link
OR
Factory Reset is the last working option, if none of the above worked.
I had that problem too...turns out my credit card info on file needed updated to my new expiration date.
These instructions came from troubleshooting on my phone.
On a computer (not tablet or phone) sign into your Google Wallet, click Payment Methods then edit to edit info. Hope it works for you too!
This worked for me when I encountered the same issue on my KitKat.
Remove your account from the device (Settings > Accounts > Google > Remove Account)
Remove the following data:
Settings> Applications > All> Downloads > delete data.
Settings> Applications > All> Play Store> delete data.
Settings> Apps > All> Google Services Framework (or if they have it in English: Google Service Framework) > delete data.
Log in again and it was fixed for me.
I got similar error while using in-app-purchase in android. My mistake is I used wrong purchase id while instantiating the purchases.
public static final String PRODUCT_ID_ASTRO_Match = "android.test.product";//wrong id not in play store dev console
Replaced it with:
public static final String PRODUCT_ID_ASTRO_Match = "android.test.purchased";
and it worked.
on the BlueStacks emulator worked for me the following solution
Go to ”Settings” -> “Applications” -> “Manage Applications” and select “All”
Go to “Google Play Services Framework” and select “Clear Data” & “Clear Cache” to remove all the data.
Go to “Google Play Store” and Select “Clear Data” & “Clear Cache” to remove all the data regarding Google Play Store.
Go to “Settings” -> “Accounts” -> “Google” -> Select “Your Account”
Go to “Menu” and Select “Remove Account”.
Now “Restart” your mobile device.
Go to “Menu” and “Add Your Account”.
and try to perform update or download.
I had the same issue - it sorted itself out in ~3 hours after I uploaded the app to the Play console. According to Google:
Warning: It may take up to 2-3 hours after uploading the APK for
Google Play to recognize your updated APK version. If you try to test
your application before your uploaded APK is recognized by Google
Play, your application will receive a ‘purchase cancelled’ response
with an error message “This version of the application is not enabled
for In-app Billing.
While the message is not the same, I suspect the root cause to be the same.
Call to your bank and ask them to activate your card to internet-use. Thats what helped me.
Check that the application on the test device and Google Play developer console really match.
I might have a bit of a special case but it might help someone: First, I had uploaded a package to Google Play that I had created with an ant build script. Second, on the test device, I debugged the same application (or so I thought). I got the "Error while retrieving information from server. [RPC:S-7:AEC-0]", and logcat displayed:
Class not found when unmarshalling: com.google.android.finsky.billing.lightpurchase.PurchaseParams, e: java.lang.ClassNotFoundException: com.google.android.finsky.billing.lightpurchase.PurchaseParams
The problem was that in the ant script, I have aapt command for modifying the package name. However, Eclipse does not run that command, so there was a package name mismatch between the applications in Google Play and the test device.
The same problem Error while retrieving information from server. [RPC:S-5:AEC-0] was resolved after these steps:
Change password of your Google account via web.
Wait for a Sign-in error notification on your device.
Type new password and problem should disappeared.
Actually, this helps me.
This error coud be also due to your google account already having Google Wallet/Google Checkout account linked. The existing account cannot be used for example it is a merchant account. Took me 20 minutes to figure out. Add new Google Account to your device, restart. While in Google Play switch to your new account. Buy your app/book/movie.
As a last resort, if all other suggestions fail, then backup all your data and do a factory reset.
If you are in a country such as Argentina, you should call your bank and verify that your card is authorized for international purchases. Certain credit cards in that country (such as pre-paid credit cards) are ONLY authorized for domestic purchases and purchases in bordering countries. They DO work online, but the purchase must be from a bordering country. What this means is that you may get this message because your card is valid but denied. I know, because this has happened to me today. Hopefully this helps someone else understand what their system is telling them.
As I never had a paid app in my google account I don't think its related
to credit cards nor to cache clear in google services.
the trick that worked for me :
change the Android date back and forth once (manually).
re-sync my google account (manually).
go to Play app and download . all worked just fine this time.
I did notice a 2-3 hours idle will also fix it by itself.