I've uploaded the aab file and have entered the emails to access the testing apk, but for some cellphones it displays "something went wrong" in the playstore, I've cleared the playstore cache but still can't. Is there anyone here who can help me?
enter image description here
You also need invite them to join in Tester's list.
On Google Console:
Click in Internal Testing inside Testing menu.
Click in Testers section, right of Releases
Then in Join on the web copy the link and share with your testers.
battling the same issue here but it make sure (if you have multiple versions available for testing) that you're generating a new link from:
Internal testing > Click the '->' on your App bundle > Click the 'Downloads' tab > then Copy the shareable link and share that
Also double check that your user group is set up with that distribution and that the appropriate emails are spelled correctly. I hope this helps.
Had the same issue today and figured out how to fix it.
In 'internal testing' page, click 'view release details', in 'App bundles' section, click the arrow button (Details).
In the App bundle dialog, click 'Downloads'. Then click 'Manage access'. It will redirect to 'Internal app sharing' page.
set up the 'Uploaders and tester' and 'Email lists', then click 'Save changes'
Related
I have successfully deployed my Android production app on Google Play. I want to remove my testers from internal test so can install and use the production app. When I go into Manage internal testers and click on Remove Users its tells me that it has saved. However when I exit from the page, it tells me that it is not saved and if I then exit and return to the page the Remove Testers button is still active. Also previous testers get the following message when they access Google Play and go to the production app download screen:
You're an internal tester. This app may be un-secure or unstable
If any one could help me to remove this message I would really appreciate it. It looks very unprofessional to some high profile clients who were also app testers previously.
Many thanks
The best way to do this is:
Go to Play Console > Testing > Internal Testing.
Under the "Testers" tab scroll to the bottom and you should see this:
Tap on the "Copy link" button. This will copy the Internal testing's binary link. Now send this to your internal testers. Once they open this link make they will get the "Leave the program" option (see picture below).
Once they tap this, they will have opted-out of your internal testing list!
p.s. If the "Leave the program" option doesn't appear on the top right of the screen ensure that the tester has selected the correct account if they have multiple accounts added on their Play store app! (see the picture below, its the square on the right side under the overflow menu).
After completing the accepted answer's instructions, your internal tester may still see the message. To fix this, first confirm that the test version of the app is uninstalled from the phone and that the Google Play Store app has been closed completely. After confirmation, have your internal tester go into their phone's Google Play Store app settings. To get there, open the phone's Settings app, click on Apps, then click on Google Play Store in the list. Your internal tester now needs to clear this app's cache. To do this, click on Storage, then click on Clear cache at the bottom of the page.
Now have your tester open the Google Play Store app and install your app the standard way. They should be able to get the production version of the app!
There's no crash in Logcat.
Both releases were created 24 hours ago.
Public Alpha (closed) track
https://photos.app.goo.gl/mm9DKDDyqkfb4Y6S6
Internal Testing track
https://photos.app.goo.gl/wC95MMdhqzCTrSr9A
P.S.: Would have loved to file a bug report but found no appropriate channel.
I managed to fix this by enabling the internal app sharing option on the play store account I wanted to test the app before accessing the link.
Just open your playstore, click on settings, enable developer mode (by tapping seven times on the Play Store Version) and then enable the internal app sharing.
If it doesn't work, you could change the permissions on "Manage testers (on your internal test playstore console)" from "Restrict access to email lists" to "Anyone you shared the link with can download", after accessing the link for the first time you should have access to it even if you switch back to "Restrict access to email lists".
Ok so after trying multiple solutions the only solution which worked for me is-
First you need to open the invite link from your system not from
the phone(for some reason the accept invitation button is not visible on
phone).
Now you need to click the accept invitation button.
Now you need to authenticate and then you can install the app successfully.
In my case I had to explicitly set who can download & install shared apps (in GooglePlay Console). By default no item was selected...
This issue happens when the option on your testers email list hasn't been checked.
Assuming that you already setup your email list:
Navigate to Google Play Console > Setup > Internal app sharing
Also, assuming that you want to restrict access to only your email list:
Check the Restrict access to email lists option
Go to the 'Email lists' tab and check all or specific emails you want to grant access.
Please see screenshots.
What fixed this to me was first joining on the web(copied link and opened from android) and then using the download link
I'm trying to publish my ionic2 app on Google play.But still, I cannot do that.It doesn't show any errors.Can you tell me how to do this?
When I press the "Ready to Publish" button then it shows below screen.
The accepted answer is now outdated.
On left side menu select 'Publishing overview'.
Click on 'Review and publish'.
Approve publish.
By the way, this is happening because you've turned on 'Managed publishing status'.
I recommend leaving it on, as it lets control when your app will actually be published after Google's review.
Op's feedback:
Press Mange Releases Button -- > Then go to the bottom of the page --> Click Review Button.After that Publish button will be shown.
Original Answer:
It's similar to App store, Your application need to be accepted by tester for review and install on different device.
"Ready to publish" does not mean you can publish it globally unless you define internal or external (Alpha/Beta)tester, and those how choose to install your app need to review your app.
https://support.google.com/googleplay/android-developer/answer/3131213?hl=en
Good Luck
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 have a test draft on Google Play developer console. It is empty, no apk files on it and no description, I just created it for check something.
Now the draft is here and I can't find a button for delete it.
How can I delete that draft? I can't find any documentation about it.
Thanks.
1) if you notice this:
2) go into the release page, then click "discard" as below:
3) then you remove the "draft"
I searched around and find no way to delete a draft.
However, you can change it's name to your future application (go to Store Listing - Title) and leave your worries behind ^^
There is an option to delete app in the menu available in the right upper corner
As of August 2017, the only way to delete the app is to click on the trash can icon in the list view. The previous answers reference UI that has been removed.
Now you have to contact the support to delete an app plus this app needs to be marked as unpublished in Google Play Console > Version > Configuration > Advanced Settings > Application availability.
Delete an app or game
You can permanently remove draft apps or games from your Play Console. You can also delete:
Published apps or games that haven't been installed on any devices
Published apps or games that no users are entitled to re-install
In these cases, contact our support team to request that your app's or game's data be permanently deleted.
Quoted from https://support.google.com/googleplay/android-developer/answer/9023647
On the Apps Listing Page there is a Delete Trash Icon. Click on that and confirm Delete.
View Image
Go to All Applications tab, then click the trash button on your app list to delete the draft app.
there is a way.
Say you already have a draft and you want to upload another draft. Upload the 2nd draft and save it. It might complain that you cant have two drafts as users can have multiple APKs installed ..fine.
Now archive the original APK (press the archive button). Now press save. Now you can use this draft and the other gets archived.