{"id":3824,"date":"2025-12-05T05:46:41","date_gmt":"2025-12-05T05:46:41","guid":{"rendered":"https:\/\/www.devopsconsulting.in\/blog\/?p=3824"},"modified":"2025-12-05T05:47:41","modified_gmt":"2025-12-05T05:47:41","slug":"errormissing-login-credentials-in-google-play-console","status":"publish","type":"post","link":"https:\/\/www.devopsconsulting.in\/blog\/errormissing-login-credentials-in-google-play-console\/","title":{"rendered":"Error:Missing Login Credentials” in Google Play Console"},"content":{"rendered":"\n
\n\n\n\n

How to Fix “Missing Login Credentials” in Google Play Console (For OTP-Based Apps)<\/strong><\/h2>\n\n\n\n

Is your app getting rejected by Google Play because of “Missing login credentials”?<\/strong><\/p>\n\n\n\n

If your app uses OTP (One-Time Password)<\/strong> or Phone Number Login<\/strong>, you are not alone. This is one of the most common rejection reasons for mobile apps in 2024-2025. Google reviewers often see a login screen, try to enter a number, and get stuck because they cannot receive the SMS verification code on their device.<\/p>\n\n\n\n

This guide will show you exactly how to solve this issue by creating a “Backdoor Access” for Google reviewers and updating your Play Console settings correctly.<\/p>\n\n\n\n

\n\n\n\n

The Core Problem<\/h2>\n\n\n\n

Google\u2019s review team is human. They download your app on their test devices to check for crashes and policy violations. When they see a login screen requiring a phone number, they cannot verify the account because:<\/p>\n\n\n\n

    \n
  1. They do not have a SIM card that can receive your OTP.<\/li>\n\n\n\n
  2. They cannot contact you in real-time to ask for the code.<\/li>\n<\/ol>\n\n\n\n

    If they cannot log in, they cannot review your app, resulting in an automatic rejection.<\/p>\n\n\n\n

    \n\n\n\n

    The Solution: The “Hardcoded OTP” Method<\/h2>\n\n\n\n

    You cannot disable login for them, but you can<\/em> create a permanent “Test Account” that bypasses the SMS process.<\/p>\n\n\n\n

    Step 1: Update Your Backend Logic (For Developers)<\/h3>\n\n\n\n

    You need to create a specific phone number that accepts a fixed<\/strong> OTP. This allows the reviewer to log in instantly without waiting for an SMS.<\/p>\n\n\n\n

    The Logic:<\/p>\n\n\n\n

    Instead of generating a random 4-digit code and sending it via SMS, your server should check:<\/p>\n\n\n\n

    \n

    “Is the phone number 9999999999<\/strong>? If yes, accept the code 1234<\/strong> immediately.”<\/em><\/p>\n<\/blockquote>\n\n\n\n

    Example Pseudo-Code:<\/strong><\/p>\n\n\n\n

    JavaScript<\/p>\n\n\n\n

    function verifyLogin(phoneNumber, enteredOtp) {\n    \/\/ SPECIAL GOOGLE REVIEWER ACCOUNT\n    if (phoneNumber === \"9999999999\") {\n       if (enteredOtp === \"1234\") {\n           return \"Login Successful\"; \/\/ Bypass SMS verification\n       } else {\n           return \"Invalid OTP\"; \n       }\n    }\n\n    \/\/ REGULAR USERS\n    \/\/ ... proceed with normal SMS verification logic\n}\n<\/code><\/pre>\n\n\n\n
    Note: Ensure this test account has data populated (e.g., a dummy profile picture, name, and history) so the reviewer sees a working app, not a blank screen.<\/em><\/p>\n\n\n\n
    \n\n\n\n
    Step 2: Configure Google Play Console (2025 UI)<\/h2>\n\n\n\n
    Once your code is updated, you must tell Google about this special account.<\/p>\n\n\n\n
      \n
    1. Log in<\/strong> to your Google Play Console<\/a>.<\/li>\n\n\n\n
    2. On the left menu, scroll down to the Policy<\/strong> section.<\/li>\n\n\n\n
    3. Click on App content<\/strong>.<\/li>\n\n\n\n
    4. Find the App access<\/strong> section (it may say “Action required”) and click Manage<\/strong>.<\/li>\n\n\n\n
    5. Crucial Step:<\/strong> Select the option “All or some functionality is restricted”<\/strong>.\n
        \n
      • Do NOT select “All functionality is available…” if you have a login screen. That guarantees rejection.<\/em><\/li>\n<\/ul>\n<\/li>\n\n\n\n
      • Click + Add new instructions<\/strong>.<\/li>\n<\/ol>\n\n\n\n
        \n\n\n\n
        Step 3: Fill Out the Access Form<\/h2>\n\n\n\n
        Fill in the credentials exactly as you coded them in Step 1.<\/p>\n\n\n\n
          \n
        • Name:<\/strong> Google Reviewer Test Account<\/code><\/li>\n\n\n\n
        • Username \/ Phone Number:<\/strong> 9999999999<\/code> (Your dummy number)<\/li>\n\n\n\n
        • Password \/ OTP:<\/strong> 1234<\/code> (Your hardcoded PIN)<\/li>\n\n\n\n
        • Any other instructions:<\/strong>“This is a pre-configured demo account for Google Reviewers. Please use the phone number 9999999999. We have hardcoded the OTP ‘1234’ for this number to bypass SMS verification. Do not use a real phone number.”<\/li>\n<\/ul>\n\n\n\n
          \n\n\n\n
          Summary Checklist<\/h2>\n\n\n\n
          Before you resubmit, check these three boxes:<\/p>\n\n\n\n
            \n
          • [ ] Code:<\/strong> Does the number 9999999999<\/code> log in successfully with code 1234<\/code> on your own device?<\/li>\n\n\n\n
          • [ ] Console:<\/strong> Did you select “All or some functionality is restricted”?<\/li>\n\n\n\n
          • [ ] Data:<\/strong> Does the test account have a valid profile inside the app?<\/li>\n<\/ul>\n\n\n\n
            Once verified, go to your Publishing Overview<\/strong> and click Send for Review<\/strong>. Your app should pass the login check smoothly!<\/p>\n\n\n\n
            \n