# App keeps getting rejected due to being unable to log in (auth0) **URL:** \ **Category:** Get Help\ **Tags:** login-experience, new-universal-login-experience\ **Created:** [March 28, 2025, 3:06pm UTC](https://community.auth0.com/t/app-keeps-getting-rejected-due-to-being-unable-to-log-in-auth0/184653 "2025-03-28T15:06:47Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![stuttskl](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/stuttskl/32/59893_2.png) [@stuttskl](https://community.auth0.com/u/stuttskl)\ **Post date:** [March 28, 2025, 3:06pm UTC](https://community.auth0.com/t/app-keeps-getting-rejected-due-to-being-unable-to-log-in-auth0/184653/1 "2025-03-28T15:06:47Z")
My app updates are getting rejected due to the following policy violation: **App is not responding** - The app freezes or becomes unresponsive. - Users cannot scroll while using the app. After investigating, I discovered the issue occurs during the login process. We use **Auth0 with a passwordless one-time passcode (OTP) flow**, meaning users must receive an email to log in. However, Google Play testers **cannot access the email inbox** associated with the provided test account, preventing them from logging in. Initially, my app was rejected for not providing a test account. I explained that our authentication flow doesn’t use traditional test accounts, as each login requires access to the email inbox to receive an OTP. Now, the issue is that multiple testers cannot share access to the same inbox due to security restrictions, leading to app rejection because they cannot proceed past the login screen. Since many apps use passwordless authentication, how do others handle this situation to avoid rejection? ---
**Author:** ![rueben.tiow](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/rueben.tiow/32/11646_2.png) [@rueben.tiow](https://community.auth0.com/u/rueben.tiow)\ **Post date:** [March 28, 2025, 7:47pm UTC](https://community.auth0.com/t/app-keeps-getting-rejected-due-to-being-unable-to-log-in-auth0/184653/3 "2025-03-28T19:47:15Z")
Hi @stuttskl, Thanks for your question. It seems that you have identified the issue with using a passwordless authentication flow where the email inbox cannot be shared among multiple testers. If it helps, one option you could try is to use a database connection to temporarily allow these testers to test the login using an email + password, just to meet the Google Play Store requirements. Cheers, Rueben ---
**Author:** ![stuttskl](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/stuttskl/32/59893_2.png) [@stuttskl](https://community.auth0.com/u/stuttskl)\ **Post date:** [March 28, 2025, 10:33pm UTC](https://community.auth0.com/t/app-keeps-getting-rejected-due-to-being-unable-to-log-in-auth0/184653/4 "2025-03-28T22:33:17Z")
Hi @rueben.tiow , thanks for your reply. Yes, I have identified the issue and see in the auth0 logs the testers attempting to use the email address I have provided, but of course they aren’t reaching a successful login state because they can’t access the email inbox. I was hoping there may be other auth0 users who have a similar use case and could share what they are doing. Could you please elaborate on your suggestion? Thanks, Katie ---
**Author:** ![rueben.tiow](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/rueben.tiow/32/11646_2.png) [@rueben.tiow](https://community.auth0.com/u/rueben.tiow)\ **Post date:** [March 31, 2025, 11:58pm UTC](https://community.auth0.com/t/app-keeps-getting-rejected-due-to-being-unable-to-log-in-auth0/184653/5 "2025-03-31T23:58:37Z")
Hi @stuttskl, Thanks for the reply. Sure, I can elaborate. Essentially, for the testing phase, you could create a temporary [database connection](https://auth0.com/docs/authenticate/database-connections) with test users using regular email and a password to allow these testers to test your app. You can create a new database connection by going to your [_Auth0 Dashboard \> Authentication \> Database_](https://manage.auth0.com/#/connections/database) and clicking on the **Create DB Connection** button. Then you can create some test users going to the [_Auth0 Dashboard \> User Management \> Users_](https://manage.auth0.com/#/users) and clicking on the **Create User** button. Let me know if you have any additional questions. Thanks, Rueben ---
**Author:** ![stuttskl](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/stuttskl/32/59893_2.png) [@stuttskl](https://community.auth0.com/u/stuttskl)\ **Post date:** [April 8, 2025, 6:43pm UTC](https://community.auth0.com/t/app-keeps-getting-rejected-due-to-being-unable-to-log-in-auth0/184653/6 "2025-04-08T18:43:27Z")
Thanks for the explanation, @rueben.tiow . That seems a bit hacky so unfortunately that won’t work for us… To your knowledge, what are other auth0 users doing in this very common use case? ---
**Author:** ![rueben.tiow](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/rueben.tiow/32/11646_2.png) [@rueben.tiow](https://community.auth0.com/u/rueben.tiow)\ **Post date:** [April 9, 2025, 9:08pm UTC](https://community.auth0.com/t/app-keeps-getting-rejected-due-to-being-unable-to-log-in-auth0/184653/7 "2025-04-09T21:08:45Z")
Hi @stuttskl, I completely understand. Would it be possible to create a test account with shared inbox access that you can provide to multiple testers as a workaround? As far as I know, we must adhere to the Google Play Store app testing requirements to get apps approved. Therefore, in this scenario, we are limited by options. Specifically, to allow these testers access to the email inbox from the provided test account or allow email + password or social logins temporarily. Kind regards, Rueben ---
**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\ **Post date:** [April 23, 2025, 9:09pm UTC](https://community.auth0.com/t/app-keeps-getting-rejected-due-to-being-unable-to-log-in-auth0/184653/8 "2025-04-23T21:09:35Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.