Neha Goel

icon company @AzureAD

Results 71 comments of Neha Goel

The acquireToken method doesn't work if the app uses "withFragmemt"

@VolodaUa Thanks for the feedback on the documentation and sample. We are taking a look and will provide you with updates.

Updating ADAL SignIn workbook with additional feilds and restructuing

[Feature 2918814](https://identitydivision.visualstudio.com/Engineering/_workitems/edit/2918814): Update SignIn WorkBook with SP Sign Ins

NullPointerException on getLastTelemetryHeaderString()

@choongyouqi Please update your configuration "broker_redirect_uri_registered": true' and test again.

NullPointerException on getLastTelemetryHeaderString()

No response, closing issue.

com.microsoft.identity.client.exception.MsalClientException: The signed in account does not match with the provided account.

@Digipom Can you please share the link to issues?

com.microsoft.identity.client.exception.MsalClientException: The signed in account does not match with the provided account.

@Digipom All of the above mentioned issues doesn't have same environment. Could you provide more details about the specific error message you're encountering and share MSAL logs if possible?

MSAL version 4.6.3 cannot be authenticated on Android 5.0 & 4.4.4

@weedcry The issue is shared with engineering team we will get back to you soon once we have prioritized. Thanks.

MSAL version 4.6.3 cannot be authenticated on Android 5.0 & 4.4.4

Hi @weedcry, Thanks for your patience. The team has been occupied with some high priority work items. Can you please try and upgrading to [latest ](https://github.com/AzureAD/microsoft-authentication-library-for-android/releases)version that is 4.9.0 and...

MSAL version 4.6.3 cannot be authenticated on Android 5.0 & 4.4.4

This was fixed in : https://github.com/AzureAD/microsoft-authentication-library-for-android/pull/2003 Correction 2/5/24: The fix shared above is not for this issue but is for a different open telemetry related issue.

MSAL version 4.6.3 cannot be authenticated on Android 5.0 & 4.4.4

Hi @weedcry and @Aaron-Constance, can you please upgrade to the latest version and let me know if you are still experiencing the issue?