AcquireTokenSilentAsync doesn't work on the iOS emulator
See original GitHub issueUsing AcquireTokenSilentAsync
on the emulator always results in a failure, on an actual device the call succeeds (Given a previous successful login)
Issue Analytics
- State:
- Created 6 years ago
- Comments:13 (2 by maintainers)
Top Results From Across the Web
AcquireTokenSilentAsync in iOS App not returning token
AcquireTokenSilentAsync is returning an object with an IdToken most of the time, but when it is on the page that doesn't always work...
Read more >[SOLVED] iOS simulators not showing up
This problem first appeared when I updated Xcode 6.1 to version 6.2. ... was still able to open the iOS Simulator App manually...
Read more >Visual Studio Mac configuration iPhone Simulator is gone
visual studio mac 8.9.1 configuration iphone simulator is gone, it was there last week. Running xcode 12.4, simulator 14.2 is installed.
Read more >[Answer]-Issue with AzureAD Authentication in iOS app-swift
We have created a app that uses Azure AD authentication and now facing issue with acquiring refresh token using MSAL library.
Read more >Is it normal that the ad-hoc url doesn't work in the simulator?
I'd like to test my app's ad-hoc deployment link, but navigating to the URL in the simulator's browser only returns 'Safari cannot open...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Do you know when they are going to fix this or what the work around is?
@7sharp9 @Jeremywhiteley @isangines @wislon @daspuru This has been addressed and the readme updated. Simulator does not use keychain sharing group, but a device will.
Going to close this issue, but feel free to reopen or respond if the issue continues.
cc: @bgavrilMS @jmprieur