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
With the latest version of Shadowrocket (2.2.31) and the config from this site, Microsoft Authenticator doesn't work properly. When I log into my Microsoft account I receive the notification on my iPhone and approve it, but it keeps failing. With Default Config of Shadowrocket, the Authenticator works properly.
Steps to Reproduce
Please provide the steps you took to encounter the bug.
Expected Outcome
What did you expect to happen?
Actual Outcome
What actually happened?
Additional Information
Version of the repository you are using
Relevant details about your environment (operating system, browser, etc.)
Screenshots or other relevant information to help us understand the bug
The text was updated successfully, but these errors were encountered:
I can confirm that this is right. Microsoft services are broken with the shadowrocket.conf on the application.
With the default config file or proxy mode it's working correctly. but with the shadowrocket.conf the speed is slow and some services like Microsoft are broken.
There is something odd (or bug) for the shadowrocket.conf on ios.
When using it, it's slow and laggy and some services are interrupted!
Also the direct rules "sometimes" work! sometimes the Iranian domains are directed but sometimes they won't open!
Bug Report
Description
With the latest version of Shadowrocket (2.2.31) and the config from this site, Microsoft Authenticator doesn't work properly. When I log into my Microsoft account I receive the notification on my iPhone and approve it, but it keeps failing. With Default Config of Shadowrocket, the Authenticator works properly.
Steps to Reproduce
Please provide the steps you took to encounter the bug.
Expected Outcome
What did you expect to happen?
Actual Outcome
What actually happened?
Additional Information
The text was updated successfully, but these errors were encountered: