[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-04-15 (世界標準時間)。"],[[["Some Google Play services require the SHA-1 of your app's signing certificate to create an OAuth2 client and API key."],["When using Play App Signing, the SHA-1 can be found in the Google Play Console."],["If self-signing your application, Keytool or Gradle's Signing Report can be used to get the SHA-1."],["`keytool` provides both release and debug certificate fingerprints."],["Gradle's `signingReport` command offers signing information for each app variant."]]],["Google Play services need the SHA-1 of your signing certificate to create OAuth2 clients and API keys. If using Play App Signing, retrieve the SHA-1 from the Google Play Console's App Integrity page. Otherwise, use Keytool or Gradle's Signing Report. Keytool commands can retrieve release and debug certificate fingerprints, including from APK/AAB files. Gradle's `signingReport` task displays signing information for each app variant. Note that the upload key differs from the app signing key when using Play App Signing.\n"]]