Support/guidance on the new zero-tap sign in requirement from Google

Open
#1,136 1 comment 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
android, kotlin

Research direction

Start by reviewing the linked Android Restore Credentials API implementation guide and the Auth0.Android SDK documentation to understand the existing sign-in and token restoration flows. The issue asks whether support is planned and what pattern developers should use today; completion would require a maintainer response or an agreed implementation scope, since the issue does not specify a code change.

Written by the indexing model from the issue text.

Description

feature request
Checklist
  • I have looked into the Readme, Examples, and FAQ and have not found a suitable solution or answer.
  • I have looked into the API documentation and have not found a suitable solution or answer.
  • I have searched the issues and have not found a suitable solution or answer.
  • I have searched the Auth0 Community forums and have not found a suitable solution or answer.
  • I agree to the terms within the Auth0 Code of Conduct.
Describe the problem you'd like to have solved

From April 2027, Google Play requires apps with user sign-in to restore the signed-in state when a user moves to a new Android device (device-to-device transfer or cloud restore). Google's stated way to meet this is the Credential Manager Restore Credentials API. Not meeting the requirement can affect an app's visibility and publishing capabilities on Play.

From April 2027, apps that support user sign-in (optional or mandatory) must support Zero-Tap Sign-In restoration when a user moves from their previous Android device to a new one and selects to restore their data either from a device-to-device transfer or cloud backup. Manual sign-ins during device setup doesn't just create onboarding friction and decrease user retention, it actively exposes apps to critical security vulnerabilities like phishing and credential theft during setup. The Android Restore Credentials API is the primary method to solve these problems and meet this requirement, and is available from Android 9 and above.

Describe the ideal solution
  1. Is first-party support for Restore Credentials planned (server-side and in the Android SDK)? If so, is it expected before April 2027?
  2. Is there a recommended pattern today for supporting this with the existing SDK/APIs? Or a plan to provide guidance before the deadline?

Thanks!

Alternatives and current workarounds

No response

Additional context

No response

Dominant language
Kotlin
Stars
303
Forks
182
Avg merge
18h 42m
Merged PRs (30d)
36

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from auth0/Auth0.Android

All issues in auth0/Auth0.Android

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.