Hello @srigovindh Sri 

This is expected behavior. Most social media sites (Facebook, Instagram, X/Twitter) block embedded WebViews for security and OAuth policy reasons.

OpenInWebView works for normal websites, but many social platforms detect and reject InAppBrowser/WebView requests.

Recommended solution:

Open social media URLs using the system browser instead of WebView.

Example:

InAppBrowser.OpenSystemBrowser(URL)

instead of:

OpenInWebView()

hope this will helps you..

Thanks and Regards,
Akshay Deshpande

Hi srigovindh Sri ,

Yes, this is a common limitation and may not be related to the InAppBrowserPlugin itself.

Many social media platforms (Facebook, Instagram, X/Twitter, etc.) restrict or completely block their pages from being loaded inside embedded WebViews. They often send security headers such as X-Frame-Options or enforce Content Security Policies, and some also require a full browser context for authentication and tracking protection.

That's why regular websites may open successfully in OpenInWebView, while social media URLs display errors such as 'Page couldn't load' or fail to render correctly.

A few things you can check:

• Test the same URL using OpenSystemBrowser instead of OpenInWebView.
• Verify whether the issue occurs on both Android and iOS.
• Check the device logs (ADB Logcat / Xcode Console) for any WebView-related errors.
• Ensure the URL is the mobile-friendly HTTPS version.
• If the purpose is to open social media profiles, consider launching them in the system browser or native app instead of an embedded WebView.

In my experience, opening social media links in the system browser is usually the most reliable approach, as many of these platforms do not fully support embedded WebViews.