Скачать или смотреть Resolving the xcrun: error: Failed to locate 'instruments' Issue in Xcode 13 Beta

Learn why the `instruments` utility is missing in Xcode 13 beta and discover the recommended alternatives for iOS development.
---
This video is based on the question https://stackoverflow.com/q/68872891/ asked by the user 'olha' ( https://stackoverflow.com/u/2567725/ ) and on the answer https://stackoverflow.com/a/68894071/ provided by the user 'olha' ( https://stackoverflow.com/u/2567725/ ) 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, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Xcode 13 beta: "xcrun: error: Failed to locate 'instruments'"

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.
---
Solving the xcrun: error: Failed to locate 'instruments' Issue in Xcode 13 Beta

Developers working with iOS often rely on various tools available in Xcode for effective app testing and performance analysis. One common utility—the instruments tool—has encountered some confusion in the transition to Xcode 13 Beta. If you've experienced the error message xcrun: error: Failed to locate 'instruments', you’re not alone. In this post, we'll break down the issue and provide a solution to keep you on track with your development process.

Understanding the Problem

When attempting to run the command xcrun instruments -w <device id>, many users have reported encountering the error indicating that the instruments utility cannot be found. A user noted that while both Xcode 12 and Xcode 13 Beta were installed, the specific path to the instruments utility (located at /Applications/Xcode.app/Contents/Developer/usr/bin/instruments) was returning no results for Xcode 13 Beta.

Example of the Error

Xcode 12 Command: Successfully locates instruments

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

Xcode 13 Beta Command: Fails to find instruments

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

This raises the question: Where has the instruments utility gone, and what are the alternatives available?

The Solution Explained

Instruments Utility Deprecated

The truth is, the instruments utility was deprecated in Xcode 12, and it has seemingly been completely removed in Xcode 13 Beta. Apple is moving towards modernizing its command-line tools and has recommended alternatives for developers.

Recommended Alternative: Using xctrace

While xctrace was introduced in Xcode 12 as a replacement for instruments, it does not work directly for all use cases, especially for pre-launching the Simulator—something the instruments utility was often used for. Instead, you can use a different method to launch the Simulator with your desired device.

Launching Simulator with Command-line Argument

To successfully launch the Simulator with a specific device ID, you can execute the following command:

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

Replace <device id> with your specific device identifier, and this command will open the Simulator using that designated device without the need for the instruments utility.

Conclusion

Though the removal of the instruments utility in Xcode 13 Beta may seem like an inconvenience, it's part of the continual evolution of Xcode and Apple's developer tools. By utilizing the command open -a Simulator.app --args -CurrentDeviceUDID <device id>, you can continue your development work seamlessly. Remember to keep an eye on future updates from Apple, as they continuously refine their development environment for an even better experience. Happy coding!