I am uploading app on Play Store. I have completed all required forms and inputs however when I go to App Content -> Ads, it doesn't show any input field. Is there any issue or I need to first complete something else?
I have opted App Alpha Testing track and uploaded App Bundles. However, only this Ads thing is left for Alpha Rollout.
Disable adblocker in your browser
Related
Problem Statement:
I published App on Google Play but can't see it there - instead it shows error message saying that Item Not Found.
Summary:
I published an App on Play Store. Its current status is Published as can be seen from following snapshot.
https://drive.google.com/open?id=171vhJJ5ED_g1v2ElD5xBwdRAcrW0RoNF
When i tap on VIEW ON GOOGLE PLAY, I can see it there as well with Published status.
https://drive.google.com/open?id=16Zy7GXhreeSdli7IBrhFBvwNP51m8HTm
Problem is, when i tap VIEW ON GOOGLE PLAY in Android Phone, i can't see there any App and see following
https://drive.google.com/open?id=12Pa7ITr93OlQJQV5UXbJfNYI8fEG66LR
Although App is allowed in ALL countries, but still i can't see it in Play Store.
I believe the issue you're having is when you search Google Play Store for your app's name, your app doesn't come up although, but you can download it if you had the app's direct link in the Play Store and even shows published on your developer portal.
Publishing an app to the Google Play Store doesn't have a fixed/specific time before it becomes downloadable (search and download) from the Play Store. Sometimes, it takes few hours while other times it could take days. This is because it is being deployed to all the Google Play servers worldwide. Mine takes about 2-3 days sometimes. Just be patient and wait for some time.
If the status of an app is PUBLISHED, then it is actually published.
The answer to your question lies in the nature of the algorithm the Google Play store uses for their search/query. You probably used a common app name (or the variant of a common app name). Generally, apps with a large number of active users top the list in search results. Your app is on the list, it's just at the bottom of the list.
This article sheds a little light on how the search algorithms work and what you should always look out to ensure your app's immediate visibility.
I hope this helps. Merry coding!
I had a build of my app in Google Play Open Beta. I released it to Production. Now, even though my friends are downloading it from the Google Play store, and they are not in my beta, it seems to be telling them that they can only use a test card for purchasing! How do I:
1) Close the beta completely.
2) Change it so people are spending real money in my app, when they download it from my app store?
It looks like people should be spending real money, from my beta page -- I've just removed all the testers and changed the country availability to just Aruba. My beta track page looks like this:
Have I made the right change? Am I just waiting for everything to propogate, now?
The actions I took after posting this question solved the problem. I needed to remove testers, and turn off the open beta test by restricting it to only one country, I guess. All done!
I was running an app in the Google Play in Beta and then just recently "released to production" using a higher version APK.
However when I go to Google Play listing my app still says AppName (Beta)? I thought it just needed some time to propagate but I made the change 2 days ago and its still showing like that.
Anyone know how to correct this?
It actually looks like its some kind of caching issue or user specific issue.
I decided to open Google Play store from a different browser (where I was not logged in) and the app was no longer showing as Beta.
Only when viewing Play store from my logged in account and from my phone is it showing (BETA).
So for any non-beta testers viewing it for the first time on their phone or via browser I assume its going to show up correctly, which is good enough for me.
It seems that this is from the user's account side. If one specific account subscribed to a beta program it will show as (BETA) on the Google Play Store.
So to remove the beta the user just has to do the following:
Open the Google Play Store on the device.
Find the app he wants to leave.
Tap the app to open the detail page for the app.
Scroll down to find the section on beta testing.
Tap Leave.
Note: I Didn't find out a way to remove this on the Play Console but google i think they should have an option to do it.
I face the same issues . I have published my app two days before but it still showing that App Name(Beta). This happens due to only if you are the beta tester of that app .When you see it from another browser or other google play store ,It won't show beta.But keep in mind that you aren't a member of tester for this app.
To resolve this problem do these things:-
Please remove your account as beta tester from that app.
Or, Log out from device.Again login google account in your device .
3) Clear cache of Google Play Store.
Perhaps ,this will help you. Thanks..
It is due to Play Store caching , clear data of the Play Store , you will no longer see it as beta, plus make sure you are trying to see app on play store from a non-beta account.
It's simple l, just delete the tester list from testers in internal testing console, then clear cache from playstore, your good to go.
I had this problem and it turned out to simply be that I was logged in to google with an account that had signed up as a beta tester. I logged out of google and then the page displayed correctly. So it seems to me the (beta) is related to your account and not the software release which is sub-optimal coding on the part of google.
It showing AppName(Beta) just because of you are a Beta tester for that app.
There are two options:
Logout from browser and then check(different user that should not be a tester)
copy URL and open in in different browser
In my case I had to clear storage of play store application on my device.
Somehow I could not update, my test track was paused, there was no way to opt out so out of desperate I just cleared storage of play store app and done, everything back in normal. PS: Yeah I also deleted app and reinstalled before that maybe this was not necessary, don't know.
Although #Ruben Miquelino's answer is correct, it is not practical to ask every user (users already on beta) to go to a link and remove beta.
I have found a better solution for this problem, If we deactivate the beta track and change target countries(only for beta) then those users will automatically be moved to Production (after Google's review process & Play store cache expiry)
I have a dev version of my app that is not published in the Play Store. I would like to test dynamic links with it, but whenever I click a dynamic link, it opens the play store, and I get a not found error (because there is no corresponding package in the Play Store).
What's the recommended way of testing this? It would also apply to staging environments, etc... that are not published.
I was able to test it like this:
I published a closed alpha version of an app - open only to my email (beta should work just the same)
Opted in via the opt-in link in the developer console (it's on the APK section)
After that, clicking the dynamic link I created on the Firebase console worked as expected, without having my app out in the open.
Caveats:
Connected Google users - might cause a problem if only one is on the alpha group list
It takes a bit of time to get started. Make sure you can see the app in Google Play before trying to click the link
Updates, fixes and changes take time until they actually appear on Google Play. Google Play now offers internal testing, a level below alpha that propagates updates quicker.
The other answer above is technically correct, but you can get close to simulating the real behavior without putting anything on the Google Play Store.
If your application is installed, the dynamic link will open your application. This is true even if your app is not listed on the Play Store. If this is not working for you, your app is not properly set up to receive dynamic links.
If your application is not installed, you will be taken to the Play Store and you will see app not found. After, you can sideload the app to simulate a Play Store install.
How to publish beta test-version in Android play store ?
I'm trying to allow beta test my phonegap build app in the android play store. I already uploaded a signed apk in the beta tab and added a google+ group with some users inside ... but I'm slightly surprised that I cannot find how to install or even find this app on the testers smartphones. I opted myself as user in the group but cant see a link to the app or something like that. Shouldn't the app be already visible to beta users in the app store? Or do I have to push the publish button? The info popup tells:
"Your app can only be used by your testers when it is published to Google Play.
If your app has no production APK then it will only be visible to Alpha and Beta
testers. The link that your testers can use to opt-in will be displayed here when
you have published your app."
Sounds to me that it should be published. But doesn't it mean that the beta apk will be moved to the published-area and not being then a beta any more? I'm afraid that the app will be then visible to all users in the play store not only for my beta testers.
Could someone explain me how to publish a beta for my testers only?
EDIT:
It seems that everything I need is the opt-in link that is missing. Any idea why?
In order to be able to get the link to share with your group you have to first press the "Publish" button in the upper right. After doing this you will see the link to share with users appear as brheal shows above.
I'm adding this graphic to the discussion to help clarify exactly which one to press and which to not press.
Per the discussion above I was still a bit worried about pressing the publish button. I just did it and it works.
For more clarity I thought I'd share what it looks like. After publishing your beta apk you have to wait up to 24 hours (it took mine about 12) and then go to 'Manage list of testers' in your 'Beta Testing' tab. When it's ready you will see the opt in link available to share:
This is really an issue Google should address ASAP. You enter the console hoping to find the sections but the documentation says something else altogether. I just solved this and found the link, here are the steps updated with the current UI of the console which is not matching the documentation:
Open Google Play Console
Open your app
In the left panel go to Release management -> App releases
Scroll down to Open track, Closed track or Internal test track section according to your case, click Manage
Go to the section Manage testers and click Internal test
At the bottom you will see the link if everything is properly configured and the app is published.
VERY IMPORTANT
You need to configure the internal test list, I assume that if you
are looking for the link you've already done this.
The app needs to be published, remember it takes some hours, otherwise you won´t be able to see the link.
Here are the screenshots:
Not enough points to comment, hence a separate answer.
My suggestion is to upload a new build after setting up the beta testing.
I created a new app and rolled out the Beta version of the app.
After that I enabled the "Closed Beta testing" for a list of users - alas no opt-in link was ever generated.
After scratching my head a bit I released a NEW build which generated the opt-in link immediately.
I figured that enabling the "Closed Beta testing" AFTER the Beta version was released could have caused the issue and is maybe why the UI is constructed the way it is.... just a guess.
Try and release a new build.