X/Twitter v2 iPhone Browser Interception Issue: Correlation failed. about aspnet.security.oauth.providers HOT 7 CLOSED

As a workaround, you could offer a native app to your users, but it's definitely not a cheap option 😅

from aspnet.security.oauth.providers.

Indeed @kevinchalet it would be expensive to both myself in terms of code + managing the different store deployments (+ funny content policies I've heard so much about), and also in terms of application users as they would be paying the store tax I would no doubt pass along to them. 💰

from aspnet.security.oauth.providers.

While I appreciated the amount of details you shared, there's sadly nothing at all that we can do on our side: the aspnet-contrib provider is purely a server-side component and cannot control how cookies are handled by the browser.

I'm afraid you'll have to ask Musk and its minions to take a look at this issue 😄

from aspnet.security.oauth.providers.

And FWIW, I personally do own an iPhone, so I made the test using your website: the Twitter "web view" doesn’t even load properly. All I get is a black screen 🤣

from aspnet.security.oauth.providers.

I'm afraid you'll have to ask Musk and its minions to take a look at this issue 😄

Fair enough. 😊 I was hoping that there may be an "add the DisableNative flag to fix this" or some equivalent, but this appears to be wishful thinking. If anything, I am hoping that this will help others who may be running into the same issue. I have been encountering Correlation failed messages for months but thought they may be due to upgrading from Twitter's Oauth v1. When they persisted after a few weeks, I knew there was something going on here different from that.

All I get is a black screen

Indeed, I have noticed all sorts of problems today myself while trying to figure out what is going on. This occurred several times:

😭

Thank you for the bad news. Closing for now.

from aspnet.security.oauth.providers.

Here goes nothing 😬🤞 https://twittercommunity.com/t/iphone-twitter-application-intercepts-safari-authentication-leading-to-invalid-state/206890

from aspnet.security.oauth.providers.

FWIW I have created a bit of a solution (read: hack) to address this, where if the Correlation Failed error occurs I basically restart the authentication workflow process instead of throwing/showing an error. The user has to press the Authorize app button twice, but that's... ok? 🤔 Better than the alternative.

https://github.com/DragonSpark/Framework/blob/6e692b50dab9173af074846883c233e8f0015e12/DragonSpark.Application/Security/Identity/Authentication/DeviceInterceptionAwareRemoteFailure.cs

from aspnet.security.oauth.providers.