Does your site use SSL, so the address starts with https instead of http? That would be recommendable. However, suppose the HTTPS page contains content (e.g., images, CSS sheets, or JavaScripts) retrieved via regular HTTP (instead of HTTPS). In that case, the connection is only partially encrypted: The unencrypted content is accessible to sniffers and can be altered by man-in-the-middle attacks, so the connection is no longer protected. A website that exhibits this behavior is called a mixed content page, to which WebView is very sensitive. Often the WebView does not load the insecure HTTP content, then the only thing that helps is to upgrade to HTTPS for all content. Please check the source code to see if you still load HTTP content.
- Knowledge Base
- WebViewGold for iOS
- Within my iOS apps, some parts (e.g., images, JavaScript, CSS, slider) of the website are not loaded (correctly).
Article sections
Related Articles
- How to integrate Pushwoosh in WebView-based iOS and Android apps?
- Fixing “white page” CDN issues in iOS & Android WebViews with a workaround
- How do I set up RevenueCat for In-App Purchases / In-App Subscriptions in WKWebView (iOS) or WebView (Android)?
- How does the native footer in iOS WebView looks like?
- How to use GitHub for smart upgrading of WebViewGold app template?
- What should we add/modify in our Privacy Policy / Terms & Conditions if we deploy WebView mobile apps?