Xcode 11.4编译错误“丢失的软件包产品 < 软件包名称 >”

In Xcode go to File > Swift Packages > Update to Latest Package Versions

Worked for me

For me, I needed File > Swift Packages > Reset Package Caches

I'm not sure of the root cause, but I get this quite regularly. Not the most elegant solution, but neither Reset Package Caches nor Update to Latest Package Versions worked for me. For me, I had to quit Xcode, and delete DerivedData.

rm -rf ~/Library/Developer/Xcode/DerivedData/*

Then rebuild.

In Xcode go to Product > Clean Build Folder

This worked for me. The problem originally started when I was trying to solve another issue that came up after I deleted my Derived Data folder.

Restarting Xcode didn't work, but cleaning the build folder did. I don't know if the other answers here would work for me because I didn't try them seeing as cleaning the build folder worked.

In Xcode 12.0.1 (12A7300) this bug has been fixed. It was auto-resolved by the Xcode update for me.

EDIT Xcode 12.5 [beta]

Apple added a SPM cache. See my question here. If you run into this problem with this Xcode version it might help to delete this cache.

None of the answers worked for me on Xcode 12.5 beta. I had to manually remove all spm packages and re add them.

Solution 1: File > Swift Packages > Reset Package Caches

Solution 2: File > Swift Packages > Update to Latest Package Versions

I got this error when having the same local Swift package open in two different instances of Xcode in two different projects. Got it working again by quitting Xcode and only having one project open at a time.

SPM - Reset Package Caches vs Update to Latest Package Versions

File -> Swift Packages -> Reset Package Caches
File -> Swift Packages -> Update to Latest Package Versions

Update to Latest Package Versions

fetch the latest possible version(based on restrictions)

Reset Package Caches

reset cache(derived folder) -> Update to Latest Package Versions

folder

<path_to_derived_data>/<randomizer>/SourcePackages/checkouts/<project_name>
//e.g
/Users/alex/Library/Developer/Xcode/DerivedData/SPM-dpsmlyjrashqjefkfheppizcrgic/SourcePackages/checkouts/SPMExperiments

[Local SPM]

A workaround for me at the moment has been both running Product > Clean Build Folder (cmd-k) and then restarting Xcode. This is an issue in both Xcode 12.4 and 12.5, and 12.5's per user package caching did not resolve the issue.

File > Swift Packages > Reset Package Caches also appears to work but it is slower for me.

Context:

One of my vendors distributes their pre-compiled binary library via SPM. Whenever I switch between git development branches, I get:

"artifact of binary target 'xyz' failed extraction: The operation couldn’t be completed. (TSCBasic.StringError error 1.)"

It also causes these "missing package product" errors for totally unrelated packages presumably because if one package fails the whole SPM process fails ("resolving package graph failed") even if these package are entirely independent.

Edit: With Xcode 12.5 simply quitting Xcode and re-opening seems to be enough.

Xcode Source Control should be enabled to run this. Preference -> Source Control and enable the source control.

I bumped into this issue today on Xcode 13.0 when working on the WooCommerce iOS app after manually deleting the DerivedData folder.

The build was failing like in the questions description: Missing package product '<package name>'

I tried both resetting the packages cache and updating to the latest versions, but neither work. Thinking about it, that's not surprising since the packages Xcode couldn't find were local packages.

What did the trick for me was following this suggestion from an Apple forums thread and remove the local packages references, then adding them back again.

In WooCommerce's case, the local packages are part of a workspace file. Removing then adding them back again in the same order didn't result in a diff in the file. That is, nothing really changed in the workspace setup, but that was apparently the kind of kick Xcode needed to get over that error. 🤷‍♂️

I had this issue after the current branch rename in the project and resolve it by clearing xcuserdata in workspace.

If none of the above answers work, Please refer the solution shared by GravityBytes in this link on Apple Forums.

Eventually he happened to share the below resolution

I eventually got this resolved. What seemed to get it working was re-adding my local packages using the "Add Packages…" menu option on the project that has the framework targets using the local package. This created a new "Packages" group in the project, and eventually started compiling correctly.

Please remove the existing references and try adding them using the above approach.

Just a silly question: did you set up your git account on Xcode preferences?

For Moya I had to edit project file to Xcode heart's content

/* XCRemoteSwiftPackageReference "Moya" */ = {
isa = XCRemoteSwiftPackageReference;
repositoryURL = "https://github.com/Moya/Moya";
requirement = {
kind = upToNextMajorVersion;
minimumVersion = 13.0.2;
};

anything other than 13.0.2 results in unresolutio for the numerous semicircular dependencies that Moya package brings to the table.

This breathes a new life into https://foldoc.org/field+circus

Nothing worked for me except Product -> Clean Build Folder and Restart

Start with the other answers like

• Reset Package Caches
• Product > Clean Build Folder

If this doesn't help...

In my messages I found a hint that I had a dependency to two different version of the same package.

After fixing this, Reset Package Caches suddenly worked for most of my packages.

I could fix the remaining problems by adding

platforms: [
.iOS(.v13),
],

to the corresponding package. Before that, I had no platforms statement.

I tried:

• Clean project
• Clean derived data
• Resolve Package Versions (File > Package)
• Update to Latest Package Versions (File > Package)
• Restart Xcode
• Restart Mac

And restarting the Mac is what worked 🥲

Others say doing "Resolve Package Versions" multiple times also work.

For me, Xcode was opened using Rosetta which wans't enabled before. Re-disable open using Rosetta helped me 💪🏼