[SOLVED] SwiftUI – iOS 13 UIViewRepresentable of WKWebView gets Thread 1: EXC_BREAKPOINT crash

Issue

I’m trying to port WKWebView over to SwiftUI. Here’s my code:

import SwiftUI
import WebKit

struct ContentView: View {
    var body: some View {
        WebViewWrapper()
    }
}

/**
 WKWebView ported over to SwiftUI with `UIViewRepresentable`.
 */
final class WebViewWrapper: UIViewRepresentable {
    
    /// `UIViewRepresentable` required function #1.
    func makeUIView(context: Context) -> WKWebView  {
        print("make")
        let webView = WKWebView() /// EXC_BREAKPOINT error here
        return webView
    }
      
    /// `UIViewRepresentable` required function #2
    func updateUIView(_ uiView: WKWebView, context: Context) {
    }
}

That’s it. I created a new SwiftUI project and pasted it in. However, I get this error:

Thread 1: EXC_BREAKPOINT (code=EXC_I386_BPT, subcode=0x0)

… with nothing printed in the console. This happened for both iOS 13.0 and iOS 13.1.

Crashing on iOS 13

But, on iOS 14.2, it works fine. The crash also seems to happen only for WKWebView. For example, if I replace it with UITextView, it runs without problems.

import SwiftUI
import WebKit

struct ContentView: View {
    var body: some View {
        TextViewWrapper()
    }
}

/**
 UITextView ported over to SwiftUI with `UIViewRepresentable`.
 */
final class TextViewWrapper: UIViewRepresentable {
    
    /// `UIViewRepresentable` required function #1.
    func makeUIView(context: Context) -> UITextView  {
        print("make")
        let textView = UITextView() /// no error, works fine
        return textView
    }
      
    /// `UIViewRepresentable` required function #2
    func updateUIView(_ uiView: UITextView, context: Context) {
    }
}

UITextView has no problems

I’m running Big Sur 11.0.1 on an M1 Mac, but I don’t think that should be a problem. My Xcode version is 12.2 (12B45b).

Edit: Big Sur / M1 might be the problem.

I just ran it on the same version of Xcode on my Intel Mac, Catalina 10.15.5, and it works fine.

enter image description here

Solution

The problem is due to a combination of running on an M1 Mac and using an iOS version prior to 14. The problem is known to Apple.

Answered By – Norman

Answer Checked By – Senaida (BugsFixing Volunteer)

Leave a Reply

Your email address will not be published.