One error that can occur when trying to launch an application based on WebViewGold for macOS (not iOS!) is the “Launch failed” (e.g., Could not launch “WebViewGold” / Could not launch “Your app name” ) error. The error detail data can look like this:
Could not launch “WebViewGold” Domain: IDELaunchErrorDomain Code: 20 Recovery Suggestion:
The LaunchServices launcher has returned an error.
Please check the system logs for the underlying cause of the error.
This message is accompanied by several other error codes and domains, such as “RBSRequestErrorDomain” and “NSPOSIXErrorDomain”, which provide additional information about the failure of the launch process.
The error message suggests that the problem lies with the LaunchServices launcher, which is responsible for launching applications on a Mac. However, by looking at the system logs, you might also get the response that the error was related to a missing framework or library that the application needed to launch.
There is an easy fix for this error message as deactivating “Open with Rosetta” on macOS for the Xcode app can help ensure that the app runs smoothly and without errors. Here’s a step-by-step guide on how to do it:
- First, open the Finder and navigate to the Applications folder.
- Locate the Xcode app and right-click on it.
- Select “Get Info” from the context menu.
- In the Info window, scroll down to the “Open with Rosetta” checkbox and uncheck it.
- Close the Info window.
- Double-click on the Xcode app to launch it. The app should now run natively on your Mac’s processor without the need for Rosetta. WebViewGold for macOS should run smoothly.
A thing to keep in mind is that deactivating “Open with Rosetta” may cause issues with other app templates & Xcode projects (e.g., some versions of WebViewGold for iOS) that depend on Rosetta, so it’s a good idea to re-check this for your other app templates & Xcode projects later to ensure that everything is working as expected.
In conclusion, encountering the “Launch failed” error can be frustrating, but by understanding the root cause and troubleshooting accordingly, it can be resolved within a minute. Of course, it’s also always a good idea to check for updates, consult the system logs, and reach out to us for support if you still need help.