Repository navigation
|
My app was flagged or rejected on Google Play for this. Sign-in state not restored on a new device. Which guideline is this, how do I find it in my project, and how do I fix it before I resubmit? |
Replies: 1 comment
|
Guideline. Play Console technical quality requirements, Zero-Tap Sign-In (Play Console Help answer 17492799) (Google Play) Severity in the playbook. medium What triggers it. From April 2027 any app with user sign-in, optional or mandatory, must restore the sign-in state when the user moves to a new Android device using the Restore Credentials API. Games are currently out of scope. An app with a login flow and no RestoreCredential integration will miss the requirement. What to search your code for. How to fix it. Create a restore credential on successful sign-in through Credential Manager, restore it on first launch after device transfer, and clear it on sign-out. The guard reports this as This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
Guideline. Play Console technical quality requirements, Zero-Tap Sign-In (Play Console Help answer 17492799) (Google Play)
Severity in the playbook. medium
What triggers it. From April 2027 any app with user sign-in, optional or mandatory, must restore the sign-in state when the user moves to a new Android device using the Restore Credentials API. Games are currently out of scope. An app with a login flow and no RestoreCredential integration will miss the requirement.
What to search your code for.
signInWith,CredentialManager,FirebaseAuth,LoginActivityHow to fix it. Create a restore credential on successful sign-in through Credential Manager, restore it on first launch after device tr…