Try Your Operation Again. If That Fails

Build Errors¶

There are 2 types of build errors that happen: they are yellowish warnings and cherry alerts. You'll see the warnings and alerts in the left-hand column of the Xcode window.

Yellow warnings practise not cause the build to fail, those are simply warnings. You lot will oftentimes see yellowish alerts. Ignore those. Practise not attempt to do annihilation to fix those.

Carmine error alerts will have to be resolved before y'all can successfully build the Loop app. The steps beneath explain how to resolve them based on the messages you lot are seeing.

Start with The Obvious Error Causes¶

New Loop Builders

This page contains build fault help for people updating their Loop app too as brand new Loop app builders. Some of the "obvious" errors causes aren't relevant for make new builders. Check out items iv, 6 and vii in the list beneath. And then, skim the page until your reach Detect Your Error Message. One time yous've identified your error bulletin, try to resolve information technology. Still stuck? Read Posting for Help

Before you start trying to resolve your ruby-red errors, first with the nearly obvious things that tin cause a cherry-red error message:

1. DO NOT USE BETA VERSIONS If you are using an iOS beta version or an Xcode beta version, your Loop will not build. If y'all have Xcode beta, uninstall it and get regular Xcode. If you have iOS beta on your iPhone, you lot will demand to restore your iPhone entirely. Y'all tin restore to either (i) the terminal non-beta fill-in version yous saved or (two) restore as a new iPhone (default settings). Aye, deleting iOS beta is a hurting...then don't install information technology in the first place.

2. Did you check for Xcode updates? This is critical. If you are updating your Loop app, please review the iOS driven requirements for Xcode and macOS.

3. Did you check your Apple developer business relationship for new license agreement? Periodically, Apple will release a new developer license agreement that you need to sign earlier you can build new apps. You lot will get a build failure if in that location is a awaiting license agreement to sign. Login to your Apple tree developer account to bank check if in that location's a new license agreement.

4. Did you reboot, i.due east., restart, your reckoner after updating Xcode? You must reboot post-obit Xcode installation or update and you lot must brand certain your control line tools match the version of Xcode you simply installed. Xcode Command Line Tools

5. Did you become a fresh download of Loop lawmaking? If you tried to build with an old download that you used a long fourth dimension ago, that old version may not exist uniform with the new iOS and Xcode versions. Check also, that you lot are actually using the new download in Xcode. Xcode remembers the project you last opened, you need to tell Xcode virtually the new download.

6. Are y'all are using a gratuitous developer business relationship? Make sure y'all finished the removal of Siri and Push button Notification capabilities.

7. Are you doing a WorkSpace build? Brand sure you selected Loop (Workspace) instead of Loop.

Fix 95% of errors¶

If you have checked all those steps above and recall you have a true build fault, here'due south a tip that resolves 95% of all build errors when updating Loop code.

1. Open your project in Xcode as normal. Then go to the Xcode menu at the top of the screen and find the "Production" menu item. Use the drop down selection for "Clean Build Binder" or press shift-command-Thousand. Either will work the same.
2. On the far right, adjacent to the name Full Path is the binder proper noun that Xcode will be using to build. Brand certain information technology is the new code you just downloaded and not an older folder.
3. If you are updating Loop and did not do Steps 4a and 4b, do it now
4. Return to Xcode and endeavour building your app again.

If the build fails again, wait through the listing below and run across if yous tin friction match your error bulletin with one of the error messages listed later in this page. If you actually can't find your solution, and so post for help. Merely help u.s.a. assistance you.

• Ignore yellowish warning letters - those are not errors - do not attempt to set up them
• Confirm it really is an fault not already on this page; read this page carefully, including all the circled bits in the images in the Specific Error Messages section
• Follow the steps in the Posting for Assistance department
• We CANNOT Aid without version numbers and screenshots
• Do not have pictures of your computer screen with your phone

Posting for assist¶

Stop!! Read this section! Important!

Earlier you post in a Loop Social Media site asking for help with build errors, exercise your work first. The build errors listed below (and the checks listed above) will prepare most of problems you may run across. PLEASE READ THIS Page . The volunteers answering questions online would love to spend more time helping people employ Loop and less time answering questions that can be addressed by using this page.

Therefore, endeavour to resolve your build error yourself. And so, if you need to mail for help, please include enough information with the post and then the volunteers know where you are in your troubleshooting attempts.

Your Mail service Must Include:

• The version of Xcode y'all are using
• The version of Loop yous are edifice with
• The version of iOS on your Loop iPhone
• Free or paid account, and if free, confirmation that you deleted Siri and Push Notification capabilities
• Confirmation that y'all are not using an Xcode beta or iOS beta version (and then we don't have to ask, delight really type "I am not using beta versions")
• Screenshots of your WHOLE Xcode window and/or Concluding window showing your error and any messages you've seen while working through the build errors/solutions. Do NOT use phone photographs of your figurer screen. See beneath for instructions on how to capture a screenshot.
• Land which fixes from the list below you take already tried AND postal service the screenshots of the results of those prepare attempts.

Screenshots¶

Please take screenshots of your issue and use them in your posts. On an Apple computer, press shift-command-iv keys at the same fourth dimension followed by pressing the space bar and and so click on the window of interest. The screenshot will be saved to your desktop with a file name starting with the proper noun "Screen Shot". Utilise screenshots instead of prison cell phone images or words whenever possible. Screenshots are higher resolution and easier to read.

Use the whole Xcode window screenshot when posting for build help.

Find Your Error Message(southward)¶

To begin fixing the mistake, use the Written report Navigator view to find your error message.

The central is to (1) READ THE ERROR Message so (2) Notice YOUR MESSAGE IN 1 OF THE TOPICS BELOW.

Here's a super tip: Merely seeing the "exit code" in Xcode is non enough information to discern what error is causing your build to fail; some exit codes have multiple causes. Look at the detailed message to guide your search for the matching solution.

Notice the screenshots below have red circles highlighting certain error messages. Read your error bulletin(south) from your screen, being guided past the red circles in the screenshots. Once you lot observe your error bulletin (hint: not "exit lawmaking"), you tin either:

• Take the mistake bulletin from your Xcode screen and use LoopDoc's search function to enter in some of that phrase to bring up the appropriate solution topic, or

• Take the error message from your Xcode screen and read through EACH OF THE TOPICS Below. Check each of the red circles to see if you have a match. Kind of like a matching puzzle.

For example, if you run into "Invalid active developer path (/Library/Programmer/CommandLineTools)" in your mistake message, use the search tool in LoopDocs with "invalid active". Yous will get a couple of links and i is the Command Line Tools fix for that error bulletin. Click on the link and you'll discover the solution.

Specific Error Messages¶

Xcode xiii Indexing Not Finished / WatchApp Extension entitlements¶

Error Bulletin:

The solution for this error has been updated with a new, simpler method.

Text in mistake message:

Entitlements file "WatchApp Extension.entitlements" was modified during the build, which is not supported. . .

Solution:

No need to quit Xcode - the graphic below matches the step numbers in the list.

1. Click on Loop binder
2. Click on WatchApp target
3. Click on the Full general tab
4. Click on the App Icons Source dropdown card
5. Click on the detail already selected (the line won't modify in appearance)

• (Optional) Clear the Build Fault (Menu at top of Xcode: Select Production->Clean Build Folder)
• Press build

CompileAssetCatalog Fault¶

This error is institute when there is a space embedded in the path proper name to your LoopWorspace binder. The good news is that LoopWorkspace seems to exist able to build from an iCloud or Dropbox drive.

Text in fault message:

Command CompileAssetCatalog failed with a nonzero exit code. . .

Solution:

This is very similar to the steps for the WatchApp Entitlements Error but you demand to echo it for 2 targets: Loop and WatchApp - the graphic below matches the step numbers in the list.

1. Click on Loop folder
2. Click on Loop target
3. Click on the General tab
4. Click on the App Icons Source dropdown carte du jour
5. Click on the item already selected (the line will alter from red to blank)

• Repeat the App Icons Source dropdown menu choice for the WatchApp target
• (Optional) Clear the Build Fault (Menu at superlative of Xcode: Select Production->Clean Build Folder)
• Press build

Carthage Fault¶

With the new LoopWorkspace download and build method - you should non see carthage errors. If you do meet carthage errors - y'all probably did not select Loop (Workspace) at the height of the Xcode window. This is a new step and easy to forget. Review the graphic from the new Build Instructions

Or maybe you lot are a repeat builder who did non read the updated information and tried to utilize the former zippo-download method. That is no longer supported. Delight read all of the Updating folio.

Advanced builders using dev may demand carthage but they should have followed the directions for Advanced Users Merely

If you previously installed carthage (used to build Loop before mid-Jan 2021) and it was updated to a version newer than 0.36.0, you may get a carthage fault.

If you are using a Loop fork or a Workspace build with the dev branch, you may nonetheless require carthage. This external link explains how to install the correct version of carthage on your estimator.

Fault Message:

Wrong Version of Carthage Error

Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/lipo: one of -create, -sparse , -extract , -remove , -replace , -verify_arch … , -archs, -info, or -detailed_info must be specified.

Solution: Manually uninstall carthage.

• Open a Concluding
• Re-create and paste this command into the terminal and hit enter

                            rm -rf /usr/local/bin/carthage                          

• Copy and paste this command into the concluding and hit enter

                            sudo rm -rf /Library/Frameworks/CarthageKit.framework                          

• Y'all volition be prompted for a password when you hit enter on the second control
• Information technology is the same countersign you use to log into the reckoner; you must have admin privileges to do this pace
• The countersign will not display on the screen as yous type it

Could Not Locate Device Support Files¶

Error Message: "Could not locate device support files." That message is telling yous that your iOS on the Loop phone requires you to get a newer version of Xcode to be able to build Loop onto that phone.

Solution: Update your Xcode version; this may also require a macOS update. Please review the phone iOS driven requirements for Xcode and macOS.

With Xcode 12, the simulators are no longer being downloaded automatically. If you are missing a simulator, follow the steps under Step ix Simulator Download.

No Such Module 'LoopKit' or Similar Bulletin¶

Solution: Y'all probably forgot to select LoopWorkspace. Review the graphic from the new Build Instructions

Error Message: If you see a Cartfile failure and several other red errors (in particular saying there is "no such module 'LoopKit'"), double click on the Cartfile error bulletin. If it says the build failed in one of the schemes, as shown in the screenshot below, so re-run the Carthage Error fix listed above.

Solution: For zero-download (non brash): Make sure to download a fresh version of code! Anything downloaded earlier Jan 21, 2021 will not work. That's when the need for carthage was removed.

Developer License Update¶

Error message: "The Apple Programmer Plan License Agreement has been updated, In order to admission certain membership resource, you must accept the latest license agreement"

Solution: You lot'll need to log onto your programmer account at programmer.apple.com and accept the latest license understanding.

Could Not Get a Container Directory URL¶

Error bulletin: "Could not get a container directory URL. Please ensure App Groups are set up correctly in entitlements."

Solution: To resolve this error, you will need to click on the Loop target's signing area and then the plus-sign in the App Groups area under the signing. Copy and paste the bundle indentifier into the new container that starts with group. and then add together Group to the finish of the name. Click OK to save. Notation, the line will start with lower case group. followed past your bundle identifier and an upper instance Group added to the end of the bundle identifier.

The final App Group should at present take a bluish cheque box, the name should start with grouping and end with LoopGroup. See the screenshot as an example. Click the build button subsequently your App Group is setup similarly and you should exist good.

Missing Command Line Tools¶

Error message: "Invalid agile developer path (/Library/Developer/CommandLineTools)" or "unable to find utility "xcodebuild", not a developer tool or in PATH"

Solution: Become to your Xcode preferences and under the Locations tab, select your Xcode version (the figure shows 12.0.1 - yours should match your Xcode version) in the dropdown bill of fare for Command Line Tools.

Device Management Could Not Launch Loop¶

Fault bulletin: "Could not launch "Loop". Verify the Developer App document for your account is trusted on your device. Open up Settings and navigate to General -> Device Management, so select your Developer App certificate to trust it."

Solution: If you go this message and are unable to notice the Device Management pick in your telephone settings, then we need to do a little extra pace to articulate out some old info.

1. Plug the phone into the computer and open Xcode
2. Click the "Window" menu item in Xcode and so cull "Devices and Simulators"
3. Right click your telephone on the left and selection "Testify Provisioning Profiles"
4. Delete all of the items in the list that take Loop in the name
5. Become to your four signing targets and change the signing team dorsum to "None" for a quick flake, and so change back to your regular signing squad name over again.
6. Rebuild Loop

That should clear the out, problematic profiles and allow a successful build.

If your problem persists after that, and then you lot might need to do total reset of your phone to clear out the pesky problem. Before you do this, yous may want to Post for Assist to brand sure it is really necessary:

1. Wipe the iPhone clean and set it up as a new device
   • FIRST - write downwardly or screenshot all your settings
   • Pod users - yous will take to start a fresh pod subsequently this
   • If you want your old pod to continue giving you basal rate, don't replace the pod before wiping your phone. In one case the telephone is reset and a new Loop app is added, you must start a new pod. The old pod should have the sound connection broken before being discarded considering yous won't be able to deactivate the pod.
2. Delete all certificates from your Developer account (you'll need to login to your Developer account to practise that)
3. Delete your old Loop lawmaking download and get a new one.
4. Rebuild Loop on the phone with the new download of Loop code.
5. Start a new pod with the new Loop app on the reset phone.

Awaiting Certificate Request¶

Error message: "Yous already accept a current iOS Development document or a awaiting certificate request."

Solution: This mistake message has recently started to appear for some new Loop builders. To resolve the issue, please log in to your Developer business relationship at developer.apple.com then click on "Certificates, Identifiers & Profiles". Under that screen, yous volition run across "Development" under the "Certificates" section in the column on the left. You will demand to click on the certificates, and choose "revoke" from the options that bear witness after you click on the document. Confirm the warning bulletin that will appear asking "Exercise yous desire to revoke the certificate?"

After you practice that, return to Xcode and open up Xcode preferences. Under the Accounts section of Preferences, click on the minus sign to delete your Apple tree ID.

Re-enter your Apple tree ID (aye...add that account right back that you literally but deleted), return to your Loop's target signing areas in Xcode and your fault message should have resolved as a new certificate will take been issued and a provisioning profile should have been created automatically.

Yous can verify the iOS evolution certificates are working by clicking on "Manage Certificates" in Xcode Preferences, Accounts and viewing the iOS Evolution Certificates. Yous should have one for your account that has a clean status similar to the screenshot beneath.

Command CodeSign Failed¶

Error message: "errSecInternalComponent, Control CodeSign failed with a nonzero leave code"

Solution: This error message is probable due to inadvertently proverb "no" to allowing Keychain Access or changing your figurer or AppleID password. Regardless, the solution is as follows:

1. Close Xcode
2. Open your Keychain Admission application (plant in Applications within the Utilities folder)
3. In the upper left corner of keychain access, make sure you take the keychain login highlighted and and then right-click the lock next to the login. Click the lock closed, and so click the lock to open it again. You will exist prompted for a password. Enter your computer admin countersign. Shut Keychain Admission app.

1. Open up your Loop project again in Xcode.
2. In the main Xcode menu (grayness menu bar at the very pinnacle of your Apple brandish area), select Production then select the choice for Make clean. (Keyboard shortcut is shift-command-one thousand)
3. Now attempt rebuilding your Loop app. If y'all ever become prompted again to allow Xcode access to Keychain, make sure to click on the option to Always Allow.

Unrecognized Arguments¶

Error message: "Unrecognized arguments: --enshroud-builds"

Solution: This is a homebrew / carthage error, so I don't call back you'll see this. If y'all exercise, download a fresh copy of Loop code and endeavour over again. If it repeats, it is time to asking assistance. Please read Posting for Assist.

Abort with Payload¶

Error bulletin: "Arrest with payload" Your app will only open briefly with a white screen and then close, if you build with this error.

Solution: This mistake message is caused by having the Loop download folder in an iCloud mapped bulldoze when doing the zip download. Motility your Loop download folder back to the Downloads folder, and so rebuild. LoopWorkspace builds with Xcode 13 announced to work fine with an iCloud drive. You may meet the spaces in your path proper noun trouble - which has a different solution.

Apple tree Lookout Bug¶

Apple Spotter: Loop App Not Actualization¶

Mistake: Apple sentinel app is not actualization.

Solution: This error normally appears because y'all have not updated the watchOS prior to edifice Loop, or you didn't have your Apple tree watch paired at the time of building Loop.

Don't forget to open the iPhone's Spotter app, select My Lookout man tab on the bottom left, scroll all the manner down, and click Install for the Loop app listed at the very bottom nether "bachelor apps".

Apple Watch: Loop App Non Installing¶

Error: The Loop app appears on the listing of apps available to install on the lookout man, but when you printing "install", and information technology goes through the animation of filling in the circumvolve while information technology'southward installing, just so at the end it just toggles back to saying "INSTALL".

Solution: Plug your iPhone into the estimator and start Xcode. On your picket, wait for a prompt that says "Trust this computer". Curl downward on the picket face and select the "Trust" button. In Xcode, become to the top menu bar and select "Clean Build Folder" from the Product bill of fare option, and and so rebuild your Loop app.

For an unknown reason, the watch app can still fail to install properly. If the "Clean Build Binder" pace higher up, is bereft, you may need to unpair your watch and then pair as new. Later on this, rebuild Loop on your phone while wearing your watch and "Trust this calculator" when prompted. This typically configures the Loop app to install properly on your watch.

glennbeggall.blogspot.com

Source: https://loopkit.github.io/loopdocs/build/build_errors/

Share this post