Repository navigation
|
How can a team catch Sign-in state not restored on a new device automatically before a build goes to review? |
Replies: 1 comment
|
The quick check. Run this from the project root and read what it prints. grep -rqn 'signInWith\|CredentialManager\|FirebaseAuth\|LoginActivity' --include='*.kt' --include='*.java' --include='*.xml' --include='*.gradle' --include='*.kts' . && ! grep -rqn 'RestoreCredential' --include='*.kt' --include='*.java' --include='*.xml' --include='*.gradle' --include='*.kts' .Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as What the hit means. 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. The fix. 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. Recipe source. data/detection-recipes.json This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
The quick check. Run this from the project root and read what it prints.
Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as
ANDROID-RESTORE-CREDENTIALS-REQUIREDwith a coverage line and a proper exit code.What the hit m…