Скачать или смотреть Resolving the Xcode 12 Build Issue on M1 Macs: Running on Devices Instead of Just Simulators

Discover how to fix the build errors when using Xcode 12 on M1 Macs with Cocoapods. Our guide breaks down the solution for smoother development.
---
This video is based on the question https://stackoverflow.com/q/66092043/ asked by the user 'gabriel' ( https://stackoverflow.com/u/14622706/ ) and on the answer https://stackoverflow.com/a/66094161/ provided by the user 'gabriel' ( https://stackoverflow.com/u/14622706/ ) 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 12 Mac M1 with Cocoapods: I can build on simulator but not on device

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.
---
Resolving the Xcode 12 Build Issue on M1 Macs: Running on Devices Instead of Just Simulators

If you're working with Xcode 12 on an M1 Mac, you may have come across a frustrating issue where your project runs fine on the simulator but fails to build on an actual device. This guide will delve into the problem and provide you with a clear, effective solution to ensure your code runs smoothly on both platforms.

Understanding the Problem

As a developer, encountering issues when transitioning from the simulator to a physical device is not uncommon, especially with the new architecture of Apple’s M1 chip. Many users have reported the reverse scenario — they can run their projects on devices but not on simulators. However, your case is different. You can successfully build and run your app on the simulator, but upon trying to deploy it on a device, you receive the following errors:

Red Error: Command PhaseScriptExecution failed with a nonzero exit code

Yellow Warning: None of the architectures in ARCHS (arm64) are valid. Consider setting ARCHS to $(ARCHS_STANDARD) or updating it to include at least one value from VALID_ARCHS (arm64, arm64e, armv7, armv7s) which is not in EXCLUDED_ARCHS (arm64).

These errors can be confusing, especially if you're unsure how to go about troubleshooting them effectively.

Breaking Down the Solution

To resolve these build errors, it's essential to ensure that your architecture settings are correctly configured in both your project file and the Cocoapods setup. Here's how to do it:

Step 1: Review Your Architecture Settings

Open your Xcode project.

Navigate to your project settings.

Under the "Build Settings" tab, locate the section labeled "Architectures".

You need to ensure that the Excluded Architectures setting is properly configured.

Step 2: Configure Excluded Architectures

Since you're using Cocoapods, there’s a critical step that you may have overlooked. Removing arm64 from the excluded architectures in your project is only part of the solution. You also need to do the same in the pods configuration.

Navigate to Pods in your project hierarchy.

Open the build settings for each pod target.

Remove arm64 from the Excluded Architectures similarly as you did for your project.

Step 3: Clean and Rebuild Your Project

After making the necessary changes, perform the following:

Clean the build folder. You can do this by selecting Product Clean Build Folder (or use the shortcut Shift + Command + K).

Next, rebuild your project to see if the changes have resolved the issue.

Conclusion

The journey of developing on the Apple M1 chip with Xcode 12 can present unique challenges, especially with Cocoapods integration. By confirming that excluded architectures are adjusted for both your project and pods, you can seamlessly build and run your application on physical devices.

Remember, when dealing with build or architecture issues, a careful review of your settings often reveals overlooked details. This troubleshooting approach not only resolves the current issue but also equips you with skills to tackle future challenges confidently.

If you encounter any more issues or have questions, don’t hesitate to ask for help from the developer community!