Скачать или смотреть Resolving WKScriptMessageHandlerWithReply Delegate Method Call Issues on Non-Main Thread in Swift

Learn how to ensure that delegate methods in Swift's `WKScriptMessageHandlerWithReply` are called on the main thread, avoiding common pitfalls in iOS development.
---
This video is based on the question https://stackoverflow.com/q/77585249/ asked by the user 'Koen.' ( https://stackoverflow.com/u/189431/ ) and on the answer https://stackoverflow.com/a/77585250/ provided by the user 'Koen.' ( https://stackoverflow.com/u/189431/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, comments, revision history etc. For example, the original title of the Question was: WKScriptMessageHandlerWithReply delegate methods are called on non-main thread

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Understanding the Issue with WKScriptMessageHandlerWithReply in Swift

If you're developing iOS applications using Swift and interacting with WKWebView, you might encounter a frustrating problem. After refactoring your code to separate the handling of view and web-related logic into a WebViewController and WebController, you may find that the delegate methods for WKScriptMessageHandlerWithReply are being called on a non-main thread. This can lead to issues, especially since certain properties of WKScriptMessage must only be accessed from the main thread, triggering warnings or crashes in your application.

In this guide, we will explore a solution to this issue, helping you understand why it occurs and how to manage delegate calls effectively to ensure your app remains stable and responsive.

What Changed After Refactoring?

In the previous setup, your WebViewController or similar class likely subclassed UIViewController, which inherits from UIResponder. This hierarchy results in the delegate methods being naturally called on the main thread, adhering to iOS UI guidelines.

When you refactored your code, your WebController subclassed NSObject instead. This change disrupted the method calls, causing them to execute on random background threads. The error message below illustrates this problem clearly:

[[See Video to Reveal this Text or Code Snippet]]

The Solution: Ensuring Main Thread Execution

To resolve the issue of WKScriptMessageHandlerWithReply delegate methods executing on a background thread, you can use the @MainActor annotation. This Swift feature ensures that code is run on the main thread, effectively solving the problem.

Step-by-Step Implementation

Here’s how you can adjust your code to utilize the @MainActor annotation:

Modify the Delegate Method: Add the @MainActor attribute to your delegate method definition.

[[See Video to Reveal this Text or Code Snippet]]

Maintain Thread Safety: By marking the method with @MainActor, you're ensuring that any UI interactions triggered by this method will run on the main thread, maintaining thread safety in your application.

Summary

Refactoring your Swift code can introduce unexpected behavior, particularly regarding thread execution. By understanding the root cause of the WKScriptMessageHandlerWithReply delegate methods being called on a non-main thread after subclassing NSObject, you can leverage the @MainActor annotation to ensure that your UI interactions occur safely on the main thread.

This solution not only resolves the immediate issue but also enhances the overall stability and reliability of your app.

Conclusion

In conclusion, always remember to consider the implications of threading when refactoring your code, especially in iOS development. By applying the @MainActor annotation judiciously, you can prevent headaches related to thread management and ensure that your application provides a smooth user experience.

Now that you have this knowledge, you can proceed confidently with your Swift applications, making effective use of WKScriptMessageHandlerWithReply without the fear of encountering threading issues.