You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am encountering an issue when changing the MSALAuthority URL in an iOS application. The error occurs because the environment is different from the previous one, and I receive the following error message:
Could not acquire token: Error $Domain=MSALErrorDomain$$Code=-50002$ "(null)" UserInfo={$MSALErrorDescriptionKey=No$ token matching arguments found in the cache, user interaction is required, $MSALCorrelationIDKey=549E6D93-FC68-4BA5-9E1D-B13BD87EE102$}
Steps to Reproduce:
Change the MSALAuthority URL in the iOS application to a new environment.
Attempt to acquire an authentication token.
Expected Result:
The application should be able to acquire a new authentication token without errors.
Actual Result:
The application fails to acquire a token and presents the error message mentioned above.
Additional Information:
MSAL Version: 1.6.2
iOS Version: 17.2
The text was updated successfully, but these errors were encountered:
I am encountering an issue when changing the MSALAuthority URL in an iOS application. The error occurs because the environment is different from the previous one, and I receive the following error message:$Domain=MSALErrorDomain$ $Code=-50002$ "(null)" UserInfo={$MSALErrorDescriptionKey=No$ token matching arguments found in the cache, user interaction is required, $MSALCorrelationIDKey=549E6D93-FC68-4BA5-9E1D-B13BD87EE102$ }
Could not acquire token: Error
Steps to Reproduce:
Change the MSALAuthority URL in the iOS application to a new environment.
Attempt to acquire an authentication token.
Expected Result:
The application should be able to acquire a new authentication token without errors.
Actual Result:
The application fails to acquire a token and presents the error message mentioned above.
Additional Information:
MSAL Version: 1.6.2
iOS Version: 17.2
The text was updated successfully, but these errors were encountered: