Skip to content

Commit 1bdfb37

Browse files
authored
minor change
1 parent 87978ee commit 1bdfb37

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

support/entra/entra-id/app-integration/android-app-authentication-fails-after-published-to-google-play-store.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Android app authentication fails after published to Google Play Store
33
description: Provides a solution to an authentication failure with an Android app that's published to Google Play Store.
44
ms.reviewer: markbukovich, v-weizhu
55
ms.service: entra-id
6-
ms.date: 02/12/2025
6+
ms.date: 02/19/2025
77
ms.custom: sap:Developing or Registering apps with Microsoft identity platform
88
---
99
# Authentication failed after Android app is published to Google Play Store
@@ -57,7 +57,7 @@ To install and use the MSAL Package Inspector, see [Package Inspector for MSAL A
5757
To get the signature hash from the Google Play Console, follow these steps:
5858

5959
1. Go to the Google Play Console and sign in with your Google Developer account.
60-
2. Once you are in the Google Play Console, select the app you works on.
60+
2. Once you are in the Google Play Console, select the affected app.
6161
3. On the left navigation, under the **Release** category, expand **Setup** and select **App Integrity**.
6262
4. Select the **App signing** tab. You will see the fingerprint of the app signing key in three different variations.
6363
5. Copy the **SHA-1 certificate fingerprint** and paste it into the PowerShell script in step 6 as the value of the `$Thumbprint` variable.

0 commit comments

Comments
 (0)