Xcode 11.4 compile error 'Missing package product '

Question

When I integrate a local package in my Xcode project everything is fine initially but when i switch branches and want to run the app Xcode gives me the compile error Missing package product <package name>. When I quit Xcode and re-open it everything is fine again. Any idea what this can be? An Xcode bug?

We also integrate external packages via Swift Package Manager which works perfectly fine. No issues there.

The issue is also well described in a post by Jesse Squires.

This is not the asnswer that states the best way. It even brings a huge waiting time with it. Especially now that the issue is fixed for me I would like to wait for more confirmation the the issue is solved instead of accepting an answer that requires re-downloading of all dependencies. To support this last week I put ALL of our dependencies in SPM and doenloading all of them is so slow that this is not an option and resetting the cache would trigger a re-download. — blackjacx, Nov 09 '20 at 11:14
Sure its not beautiful, but I guess its more of a Xcode bug than anything. And I think it is the cleanest, albeit brute approach.. — Nicolas Degen, Dec 30 '20 at 08:54

score 108 · Accepted Answer · answered Feb 24 '21 at 03:31

108

Solution 1: File > Swift Packages > Reset Package Caches

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

answered Feb 24 '21 at 03:31

XpressGeek

1,963
2
19
23

1

I'm totally new on this and that helped a lot – JBarros35 Jun 25 '21 at 15:24
It works for me but if I turn off my VPN connection, seems like some VPN servers have some issues with the swift package manager. – Ahmadreza Aug 04 '21 at 05:49
And when this does not help, restart xcode – kuzdu Sep 13 '21 at 14:01
This is the correct answer if you used "pod deintegrate" to clean your project from cocoapods. – Diogo Nunes Oct 20 '21 at 09:25
Xcode 13, solution 1 fix my issue. – ChuckZHB Nov 03 '21 at 08:15
Yes, totally worked for me too! Thanks – Natalia Terlecka Nov 25 '21 at 11:44

score 56 · Answer 2 · answered Jun 21 '20 at 13:08

56

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

answered Jun 21 '20 at 13:08

Nicolas Degen

1,150
1
11
18

score 26 · Answer 3 · answered Apr 08 '20 at 00:31

26

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

Worked for me

answered Apr 08 '20 at 00:31

gexhange

288
2
6

LondonGuy · Answer 4 · 2020-09-11T12:53:10.577

10

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.

edited Sep 11 '20 at 12:53

answered Aug 04 '20 at 11:48

LondonGuy

10,199
10
73
147

1

Even with a local package, I get the (misleading) error message whenever something is changed in the 'platforms' part of the package in Package.swift. This fixes it for me. – HendrikFrans Sep 11 '20 at 08:21

score 8 · Answer 5 · answered Sep 24 '21 at 02:07

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. ‍♂️

score 6 · Answer 6 · answered Feb 12 '21 at 14:11

6

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

answered Feb 12 '21 at 14:11

yzoldan

178
2
13

Xcode 12.5 caches dependencies somewhere. This is new in this beta version. See https://stackoverflow.com/questions/66143815/xcode-12-5-spm-dependency-cache-location. If you find out where, it would help me a lot and also yourself since re-adding packages should not be necessary at all. You might just miss deleting the cache. – blackjacx Feb 12 '21 at 14:33
Thanks, mate! This answer saved me a lot of time! – oskarko Apr 28 '21 at 13:43
In Xcode 13, all the other offerings didn't help me. Deleting and re-adding a local package resolved the complaint. – bshirley Nov 26 '21 at 19:52

score 5 · Answer 7 · answered Jul 06 '20 at 06:34

5

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.

answered Jul 06 '20 at 06:34

Matt Comi

531
5
9

1

Okay this is hardcore, close/repoen xcode is enough :D – blackjacx Jul 07 '20 at 12:15
1

That's what everyone else was telling me too lol. In my case, it just wouldn't budge, so I decided to blow it all to hell. – Matt Comi Jul 08 '20 at 02:10
Reopen was in fact enough for me. – nayan9 Feb 06 '21 at 22:50
Make sure Source control is enabled in XCode – Ishara Meegahawala Jul 14 '21 at 10:43

yoAlex5 · Answer 8 · 2022-02-04T10:07:17.083

4

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]

edited Feb 04 '22 at 10:07

answered Mar 31 '21 at 16:39

yoAlex5

21,739
5
148
151

basically exclude derived data folder – JBarros35 Jun 25 '21 at 15:43

slythfox · Answer 9 · 2022-01-04T20:14:21.740

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.

score 0 · Answer 10 · answered Mar 17 '21 at 14:34

0

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.

answered Mar 17 '21 at 14:34

Kent Robin

1,636
17
18

score 0 · Answer 11 · answered Jul 14 '21 at 10:42

0

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

answered Jul 14 '21 at 10:42

Ishara Meegahawala

647
7
12

score 0 · Answer 12 · edited May 21 '22 at 15:33

0

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

edited May 21 '22 at 15:33

halfer

19,471
17
87
173

answered Nov 25 '21 at 23:37

happycoder

917
3
13
27

score 0 · Answer 13 · answered Feb 03 '22 at 14:44

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.

score 0 · Answer 14 · answered Feb 11 '22 at 14:57

0

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

answered Feb 11 '22 at 14:57

Gastón Antonio Montes

2,474
2
11
13

score 0 · Answer 15 · answered Mar 21 '22 at 14:15

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

blackjacx · Answer 16 · 2021-02-12T14:35:27.930

-2

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.

edited Feb 12 '21 at 14:35

answered Sep 30 '20 at 18:00

blackjacx

7,448
5
42
50

1

Not fixed in my case. This solution https://stackoverflow.com/a/62498968/1358117 worked for me. – Hello world Oct 05 '20 at 00:46
Is it really not fixed for you?! I never had this issue again after Xcode 12 upgrade... Can somebody confirm this? – blackjacx Nov 09 '20 at 11:10
1

I'm not sure but seems like the link above is more likely a solution. – Hello world Nov 12 '20 at 01:49
The links solve it for the buggy Xcode version <12.0. Meanwhile the problem is gone wothout the need of intermediate fixes. This is why this one is my accepted answer. – blackjacx Jan 01 '21 at 16:29
updated the accepted answer, you're where right the answer to this question for Xcode 11 is actually not this one. But this answer is correct anyways so it shouldn't receive a downvote. – blackjacx Feb 24 '21 at 10:16
why you picked the new answer? its the same as i wrote a year ago... – Nicolas Degen Mar 10 '21 at 08:53
because it answers the question. especially since the question states Xcode 11.4 explicitly. so this answer is correct for this Xcode version. – blackjacx Mar 10 '21 at 14:12

Xcode 11.4 compile error 'Missing package product '

16 Answers16

Linked