Skip to content

Commit e4999cc

Browse files
author
Simonx Xu
authored
Merge pull request #8559 from AmandaAZ/Branch-PostEdit
Update a link
2 parents 24bfb83 + 39cc826 commit e4999cc

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 Being Published to Google Play Sto
33
description: Provides a solution to an authentication failure with an Android app published to the Google Play Store.
44
ms.reviewer: markbukovich, v-weizhu
55
ms.service: entra-id
6-
ms.date: 03/07/2025
6+
ms.date: 03/25/2025
77
ms.custom: sap:Developing or Registering apps with Microsoft identity platform
88
---
99

@@ -51,7 +51,7 @@ To resolve this issue, do the following things:
5151

5252
You can get a new signature hash by using the MSAL Package Inspector tool or from the Google Play Console.
5353

54-
To install and use the MSAL Package Inspector, see [Package Inspector for MSAL Android Native Guide](https://blogs.aaddevsup.xyz/2022/03/package-inspector-for-msal-android-native-guide/).
54+
To install and use the MSAL Package Inspector, see [Package Inspector for MSAL Android Native Guide](package-inspector-msal-android-native.md).
5555

5656
To get the signature hash from the Google Play Console, follow these steps:
5757

0 commit comments

Comments
 (0)