My app is an unofficial version of Telegram app that has been already published in Play Store. For first publishing and a few updates afterward, there was no problem for login from Google. But my last update was rejected as below:
Issue: Need login credentials for app review
In order for us to review your app for compliance with Developer Program Policies, we will need you to provide valid login credentials for your app.
If users need credentials to access your app, please provide all appropriate credentials via Play Console.
If you previously supplied credentials, please ensure that they have not expired.
If your app normally uses 2-Step Verification (e.g. SMS verification), biometrics (e.g. a fingerprint or face scan) or a location-dependent password (e.g. geo-gate), please provide valid demo credentials that we can use instead.
My question is how to provide an account for Play Store to review my app? or is there any demo account for Telegram to check?
Thanks
I recently faced a similar problem and here is my solution.
First of all, I found this documentation.
Here you can find these test phone numbers/accounts which you can
use.
In the BuildVars file, I've set both DEBUG_VERSION and
DEBUG_PRIVATE_VERSION to "true".
Deploy an app and check how it works with Test Accounts. Don't
forget: It's very necessary to tick the "Test Backend" checkbox,
otherwise, Telegram Test Accounts will not work!
I turned on a "Managed publishing" in the Google Play Console (it
allows you to send a Bundle to review and manually send an app to
production after it if needed).
I described how exactly the Google Play Team should use these
accounts to check my app in App Content -> App access in Google Play
Console.
After I passed the review, I built another Bundle, in which I've set
both DEBUG_VERSION and DEBUG_PRIVATE_VERSION back to "false" and
sent this bundle to the review again (this version will go to
Production)
The application got rejected saying: "Not adhering to Permissions policy" not giving any particular reason as of why it has been rejected but received a mail saying
Action required: Provide instructions for app access
Here’s what to do to help get your app back on Google Play:
Provide access details for your app using the instructions described in this Play Console Help Center article under the “App Access” section.
If your app typically requires a 2-Step Verification code or One Time Password, please provide us with reusable login credentials that do not expire through the Google Play Console.
If your login credentials are not numeric or alphanumeric (for example, QR code, barcode), please generate a static URL and upload it to the Google Play Console.
Resubmit your app for review after double checking that it is compliant with the Developer Program Policies, including the Play Console Requirements.
If your Update status is ‘Ready to send for review’, or if your Publishing overview has a section for ‘Changes ready to send for review’, then you must click ‘Send for review’ from the Publishing overview page to submit your changes for review.
Note: You can complete these steps without contacting our policy support team.
But since the application is a Banking application which requires the user to be registered with the bank and hold a Account in the same bank to be able to Login, we are unable to provide credentials.
(Have already sent a appeal to play store saying the same but was asked to send login credentials none the less, and we have uploaded multiple app which was accepted by play store before, but this issue started occurring from December)
Can anybody give me a solution to this?
Open Play Console and go to the App content page (Policy > App
content). Under "App access," select Start. Note: If you’ve previously
added instructions for app access and you want to make changes, you’ll
see and select Manage instead of Start. Click + Add new instructions
and provide your access details. Note: Use the "Any other
instructions" field to let us know if there’s anything special about
your login mechanisms, such as using a one-time password, multi-factor
authentication, or logins with more than two fields. Save your
changes.
This for point (1)
Point (2) Are you track user location at the background
It has been 1 year since I've used this account to publish an Android app built with React Native. The previous app was disabled during that time. I wanted to start and configure a new app page to prepare for uploading the APK and inviting users to test the new app. When trying to log into the Google Play console a 403 status error page is displayed without any explanation. How do I resolve this issue?
I had this issue today when the link to the Console worked last night and OP's answer wasn't the case with my problem.
Head to https://play.google.com/console/ and log-in from there. In my case, my shortcut I had saved must've been an old URL being deprecated by Google in their process of rolling in the new Console fully (I'm guessing).
The owner of the parent account, logged in and had to pay $2. Although, the child account, mine, was associated with the parent account before neither the previous app existed nor my account associated with the organization. The owner needed to add my account as a user on the permissions page and I now have access.
I have set up an internal testing channel on the Google Play Store. I have added a few testers for my app but could not find a way to check if a particular tester from the list has installed the app or not.
I think this can be found out in Appstore.
We would like to know who has installed the app.
I attempted using the firebase analytics dashboard and play console dashboard for the app as well, app statistics etc, but with no luck.
Is there a way to find this in Playstore?
The best way to distribute an Android or IOS application for testing to users is through Beta Crashlytics.
From there you will be able to see exactly who installed your application and who didn't.
It will let you know from your Fabric panel who has installed the app.
See documentation here on how to distribute your apk.
Google Play does not provide this information. Any feature like this would have to be carefully evaluated on how it affected user privacy.
The signup for internal testing requires the Google Play email address the user will use to install the app. While I have never found anything more than a count of testers who installed, you can retrieve the current account of the user using the app. It isn't exactly a neat and autonomous process, but you could craft a means to compare the list of potential users to the installed account.
The permission required is GET_ACCOUNTS and then you would use AccountManager to retrieve a list of accounts and iterate through them to see if any match a list of testers.
I think I followed all steps which I have found so far but the download link for my alpha test isn't working.
I uploaded the app 3 days ago, created a google group and added the group to the list of alpha testers.
I invited a few members and the app status shows published, after clicking on the link I can signup as alpha tester, but when I click on "Download from the Play Store" the error message "We're sorry, the requested URL was not found on this server" comes.
Did I miss an additional step? Do I have to grant some special rights to the group members somehow?
--- update can this be caused by the permissions of the app?
under the apk info in the developer console I can see:
functions:
android.hardware.LOCATION
android.hardware.location.GPS
android.hardware.location.NETWORK
android.hardware.TOUCHSCREEN
permissions:
android.permission.ACCESS_COARSE_LOCATION
android.permission.ACCESS_FINE_LOCATION
android.permission.INTERNET
-----UPDATE2
Well I don't have any idea what changed but now the download link is working for my alpha testers.
For me, it resulted to be a cache problem so deleting the cache in Setting > Apps > Google Play Services > Storage > Clean Cache and deleting chrome's cache, did the trick.
If your app is published in alpha or beta version :
it won't be shown in search results,
use the link that google play sent you in the group of testers in order to open it in Google Play application.
(see edit below)
You can also open this URL : https://play.google.com/apps/testing/APP_PACKAGE with a browser if the email configured in your phone is a member of the google testers group.
i don't think permissions in manifest can hide an app of the store !
EDIT
After you have uploaded your APK file and published it to Alpha or Beta version, you will see a link "manage testers group" or something like that. Click on that link ... you will be asked to add a google group of testers, below the popup you will see a message like this : "share this link with you testers group". Copy that link and send it to the group by mail.
Sorry I am writing with SO android app, I can't paste screenshots therefore ... may be tomorow ;-)
Hope it's ok.
I don't have any idea what changed but now the download link is working
You issue was just the publish delay -- it takes some time for Google Play servers to pick up your submission (for any publishing operation, even with alpha builds), usually under 24 hours.
Try opening the link on both your test device and in a desktop browser.
I was able to sign up as a tester from the device, but not install the app (said not found), but going to the desktop browser was able to use google pay to install it remotely to the device.
Make sure its the url in the form https://play.google.com/apps/testing/{your.namespace}
Sign in to your Goole Play Console.
Select your app.
On the left menu, Select Release management -> App releases.
Select Manage Alpha or Manage Beta.
Manage testers, click on right side down arrow.(Just below CREATE RELEASE)
Choose a testing method: select Closed Beta Testing.
Next Create list or select the name of your list.
Feedback Channel: Enter your email to get feedback from testers.
Copy Opt-in URL and send it to your testers.
Now once you completed, Google Play servers takes time for any publishing builds alpha or beta. For me it takes 15-20 minutes to available.
Sometime clear cache of your browser and refresh link. will work.
Once link is available, Open it in your testing device and click on below link
Download the *APP NAME* app on Google Play
Press the Update Button. After installation you can test it.
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.
I'm having the same problem, the link simply doesn't work, 36 hours after publishing. Might as well not even provide the alpha/beta features if it's going to be like this.
Anyway, I'm sharing some information provided to me by Google Support, hoping it'll be helpful:
Ensure that you have added a valid Google Group email or Google+ Community URL to the Developer Console and that you are included in the group/community. Once the group/community has been added, the name of the group will display in the “Manage list of testers” link in the testing tab. (Please note when adding a Google Group you need to enter the email address and not the URL).
If you wish to use a Google Group in a Google Apps domain, the Developer Console and Private Channel must be enabled for your domain in the Google Apps Control Panel.
An app must be published for several hours before the opt-in link will become available to testers.
Currently, testers must have only one account on their device. Devices with more than one account will receive the production version of your app. (Please note this requirement is temporary. Stay tuned for updates).
If you followed the mentioned instructions and it's still not working, in 2019 make sure to also check the following:
1) Make sure the testing group is selected, but is also active:
2) Ask your testers to log out of their google account, then to clear the cache of their browser. They should then close/re-open the browser and log in into the invited email address.
There are several causes for the internal/alpha testing link not working:
1-You are on a different google play account
2-Your email is not added at the email list for testers
3-Go to google play console> your app > app releases > internal test > make sure list name is check as if not the testers will not have access to the app
Hope this helps to solve the issue
One of the causes of that issue might be its availability in (one) particular country only. (USA, usually).
In that case you just should go to the app details and allow its distribution to other (local) stores.
My problem was that even though I deinstalled my release version the link from internal testing brought me again to the release version. This fixed it.
I had this problem if I was logged in with multiple different Google accounts. I opened a new private browsing window and logged in with the account that I wanted to use as an alpha tester, and then the download link worked.
I got the same issue, seems a bug. Solved by:
1.Click "unpublish".
2.Wait for a while, click "re-publish".
Then my App became available in a few minutes.
In my case I was listed as tester in several list (alpha and internal test).
I had only joined the alpha testing channel and I had no way to access the app via the link nor via searching the store.
And as soon as I also joined the internal test channel.
The link to the app magically started working.
So I guess the rule is: you need to make sure you have joined the most privileged testing group that you're invited to.
Also make sure the app, you're going to test, is uninstalled from your device.