"Missing package product" error for all local Swift Packages when switching git branches

FelixHermann · 2021-12-13T22:47:27.736Z

Yep, SPM seems to be completely broken with 13.2, CLI swift build works tho...

Screenshot 2021-12-13 at 23.43.513104×1836 246 KB

BasO · 2021-12-13T22:51:56.978Z

Same issue with a clean App Store install of Xcode 13.2 in two projects, and I never had this issue before. In addition, adding a package results in an infinite hang on "Preparing to validate...".

Schermafbeelding 2021-12-13 om 23.50.362388×1580 246 KB

tonyarnold · 2021-12-13T23:19:31.943Z

I'm seeing the same issue (FB9807887):

Internal error: missingPackageDescriptionModule

Joseph_Heck · 2021-12-14T01:08:43.028Z

Same here - also reported in FB: FB9807816. I've now wiped my machine and reinstalled from MAS as well as direct downloads.

the RC2 (identical reported build of Xcode) direct download isn't having any issues, but the MAS installed version does. I reinstalled Xcode 13.1 (from XcodeReleases.com) and it's also fine.

The MAS version will also fail to build a brand new swift package from the default template installed with it (e.g. Xcode -> New Swift Project -> ... take all the defaults). Same error message there.

NeoNacho · 2021-12-14T01:13:49.954Z

https://developer.apple.com/forums/thread/696504?answerId=698142022#698142022

macnib · 2021-12-14T04:27:21.673Z

Seeing the same issue after Xcode 13.2 update via Mac App Store. Initially I was getting "Internal error: missingPackageDescriptionModule". Then I removed the package setting from my project settings and selected the same package to start over. But now I get the hang on preparing to validate. Removed only the derived data folder, reset packages caches, rebooted, looked over privacy settings, reset Xcode select path, updated projects to new Xcode version, checked command line tools is 13.2 (13C90). Let Xcode sit hoping for a time out but nothing happened.

I just have one dependency which is Swift Atomics listed under Apple Swift Packages. Never seen this problem prior to the 13.2 final update. M1 Mac. I did see in the macOS 12.1 update a note it was going to update my command line tools too. Just feedback on hot potato.

pchelnikov · 2021-12-14T05:58:24.613Z

I'm seeing this too.

Karl · 2021-12-14T06:40:28.588Z

It's shocking that this is still on the AppStore. Even the release notes admit that it's broken.

I know this forum isn't supposed to be about Apple or their distribution policies, but -- this is the official Swift toolchain, shipped as part of Swift's premier IDE. I think it is reasonable to be a little bit annoyed and feel a little bit like your time is not being valued when your entire workflow is broken by a widely reproducible bug

Not to mention that this follows the launch of Swift Concurrency, which itself miscompiled even the most basic of tasks (like passing an enum to an actor).

It's just not good enough. It just isn't.

vine · 2021-12-17T12:22:42.126Z

Isn't Apple going to fix it? It's been four days.

Joseph_Heck · 2021-12-17T21:27:22.086Z

@vine There's an updated Xcode 13.2.1 that's just been posted. The release notes showing it's explicitly aimed at two fixes - the package resolution issue from above, and another related to libConcurrency and bitcode.

Gavin_Eadie · 2022-05-13T22:16:46.925Z

One thing to try (it worked for me to resolve a very similar problem ["import" failing to be satisfied that the package was in scope] - Xcode 13.3.1 & macOS 12.3.1) is to not use the "Add Local .." button in the "Add Packages .." panel, but to type in a "file://.." URL (like you would "https://github.." for a web based package).

The result is quite different in that the Package is added to the "Package Dependencies" where Xcode sees it, whereas "Add Local .." puts the Package above the "Package Dependencies" where Xcode seems to ignore it. This after six hours of deleting derivatives and caches, removing and re-adding the package and cleaning the project so many times that it shines!

The above resolved the exact same problem on three different Macs - new and old.

So my package list is now:

https://github.com/me/PackOne.git   
https://github.com/me/PackTwo.git
file:///Users/me/Development/PackThree

.. and I've kissed a whole day goodbye, which I will consider worth it if this help someone else.

Gavin_Eadie · 2022-05-13T22:25:00.626Z

I might also have read:

How to link a package locally into my Swift project? Using Swift

If I have a separate Swift package that I am developing but not ready for publish but I want to try it out in a Swift app can I link that into my project locally or do I always have to push to a git repo and tag with a version to install?

Spencer_Kohan · 2022-05-27T05:43:56.127Z

I'm running into this issue with XCode 13.4. Specifically it's my system library packages which are not loading.

danniss10 · 2022-07-06T20:44:26.783Z

My team and I still constantly run into this issue. Using Xcode 13.4. Sometimes it happens with all packages, sometimes with just some. We have a bunch of local swift packages that we use and link to our main target. Sometimes we have to delete derived data, clean builds reset packages caches, and quit Xcode, but it often fails. Sometimes I can add a space in a package.swift and save the file which sometimes triggers Xcode to reevaluate, but its a very flakey fix.

bcichowlas · 2022-10-05T00:52:39.213Z

Whenever this happens to me, I just remove one of my packages and put it back. Then things will get rebuilt, which, of course, can take a little while.

jsq · 2024-05-16T19:44:29.710Z

This is still a problem with Xcode 15.4 (15F31d) with remote packages.

kaiengelhardt · 2024-05-16T21:10:13.891Z

I confirm. This has been for years and still is a problem for us. Once an Xcode project is complex enough with a few SPM dependencies, this error is very easy to run into. This is a daily struggle for my entire development team.

I really hope we can get this escalated to finally have a seamlessly working Xcode / SPM integration.

aurora14 · 2024-05-17T11:10:43.334Z

Yep. Running into this constantly, - at least 3 days of dev effort in our team lost just to this kind of stuff.

Wouldn't go back to Carthage or Cocoapods, but stuff like this is table stakes, and if it isn't working in a real-world project then it needs to be fixed, simple as that. The random ways that it breaks and completely blocks you when you touch anything package-related are just not acceptable if SPM and Swift are to have a life.

mispellingError · 2024-05-22T02:38:44.648Z

Can confirm this is still happening on Xcode 15.4 (15F31d) and a simple project with just 5 dependencies.

Very frustrating.

4Dan4 · 2024-05-22T13:00:45.926Z

U can discard changes in .resolved file, or reset package caches (File -> Packages -> Reset Package Caches)