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

Offen
#1,136 1 Kommentar 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
35/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
android, kotlin

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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

Vorherrschende Sprache
Kotlin
Sterne
303
Forks
182
Ø Merge
18 Std. 42 Min.
Gemergte PRs (30 T.)
36

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus auth0/Auth0.Android

Alle Issues in auth0/Auth0.Android

Ähnliche Issues

Weitere Issues zu Kotlin

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.