AcquireTokenInteractive crashes on UWP app for ARM64

Version of Nuget Microsoft.Identity.Client 4.19.0

Platform: UWP on ARM64

In a UWP Desktop App, running on ARM64, we want to authenticate for OneDrive, using the method IPublicClientApplication.AcquireTokenInteractive(…).ExecuteAsync();

Repro

private readonly string[] m_scopes = new[] { "Files.ReadWrite" };

IPublicClientApplication s_publicClientApp = PublicClientApplicationBuilder.Create("MyAppKeyForOneDrive")
					.WithRedirectUri("https://login.microsoftonline.com/common/oauth2/nativeclient")
					.Build();
IEnumerable<IAccount> accounts = await s_publicClientApp.GetAccountsAsync();
IAccount firstAccount = accounts?.FirstOrDefault();
AuthenticationResult authResult;
if (firstAccount != null)
{
	authResult = await s_publicClientApp.AcquireTokenSilent(m_scopes, firstAccount).ExecuteAsync();
}
else
{
	authResult = await s_publicClientApp.AcquireTokenInteractive(m_scopes).ExecuteAsync();
}

Expected behavior User is shown the login popup to enter credentials, and after successful login, the code receives a valid authResult.

Actual behavior On ARM64, the app crashes with an unrecoverable exception in SharedLibrary.dll.

Additional context/ Logs / Screenshots Please note that the very same code works perfectly in x64.

[tipa]

I am also disappointed to hear this issue has been closed without fixing it. This is especially frustrating for new developers picking up this library - they will all run into the same problem eventually. I have read through the whole thread now and haven’t seen an explanation on why a) this cannot be fixed in the library and b) what UseDotNetNativeSharedAssemblyFrameworkPackage actually does and why it is a functioning workaround

If it’s not a bug in the MSAL library, where is the crash originating from then?

[dpaulino]

@bgavrilMS could your team acquire these arm64 dev kits for testing? https://www.microsoft.com/en-us/d/ecs-liva-mini-box-qc710-desktop/8z247h1h3skp