Answers

• saguar ITMember ✭

  November 2018

  UPDATE

  After a deep investigation I've finally found the problem! Actually it seems that after the deprecation of UIWebview when using a custom renderer to handle authentication scenarios you cannot skip the HTTP 200 response (as suggested before) otherwise the component won't load the html contents!

  So this is what I had before in my custom renderer:

  public override void DecidePolicy(WKWebView webView, WKNavigationResponse navigationResponse, Action<WKNavigationResponsePolicy> decisionHandler)
      {
          var url = navigationResponse?.Response?.Url;
          if (url == null) return;
  
          if (navigationResponse.Response is NSHttpUrlResponse)
          {
              var resp = navigationResponse.Response as NSHttpUrlResponse;
              if (resp.StatusCode == 200) return;
              HandleHttpResponse(resp);
              decisionHandler(WKNavigationResponsePolicy.Allow);
  
          }
          else if (navigationResponse.Response is NSUrlResponse)
          {
              //todo handle this case too if we want to open excel files in webview
              //UIApplication.SharedApplication.OpenUrl(url);
              decisionHandler(WKNavigationResponsePolicy.Cancel);
          }
  
      }
  

  and this is what I have changed:

  var resp = navigationResponse.Response as NSHttpUrlResponse;
  //if (resp.StatusCode == 200) return;
  HandleHttpResponse(resp);
  decisionHandler(WKNavigationResponsePolicy.Allow);
  

  Just commenting the if for StatusCode 200 and let contine with decisionHandler it works... Very very weird!

  0
• LandLu Member, Xamarin Team Xamurai

  November 2018

  Thanks for sharing your successful experience.
  Generally, the 200 StatusCode represents a successful call back from server and in that case we should use decisionHandler(WKNavigationResponsePolicy.Allow); to tell wkwebview to load this correct web request. If you do not want to show the following process in wkwebview, we can use decisionHandler(WKNavigationResponsePolicy.Cancel); to intercept it. Do not return when the code is 200, this would also block the process.

  0