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

Ouverte
#1,136 1 commentaire 1 réaction 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
35/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
android, kotlin

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

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

Langage dominant
Kotlin
Étoiles
303
Forks
182
Merge moyen
18 h 42 min
PR mergées (30 j)
36

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de auth0/Auth0.Android

Toutes les issues de auth0/Auth0.Android

Issues similaires

Plus d'issues Kotlin

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.