User Experience Issue with Twitter OAuth in H5 App Within Twitter's WebView

[Siykt]

Hello,

I'm encountering a user experience issue with my H5 application's Twitter OAuth process when accessed within Twitter's WebView. Here's a detailed description of the problem:

1. Users open our H5 page within the Twitter app.
2. They choose to log in using Twitter. This action opens their default web browser.
3. In the web browser, they don't have an active Twitter session (despite being logged into the Twitter app), so they have to log in again.
4. After logging in through the browser, the flow doesn't redirect back to the Twitter app; users are left in the browser.

This creates a disjointed experience, as users expect to remain within the Twitter app environment after logging in. Any guidance on how to ensure that users stay within the Twitter WebView throughout the entire login process would be greatly appreciated.

Thank you for your assistance!