Xcode 16.x never finds a new Swift package when Searching All Sources

Development Package Manager
1

I'm on a new Mac M4 using GitHub SSH, but when I try to find a Swift Package on GitHub in Xcode 16.2 (latest) the package is never found.

I can load a package that I've previously used, such as AVCam. The spinner never stops when searching for a new package, in this case ViewInspector or RevenueCat's purchases-ios.git. (I don't have a problem working with purchases-ios.git on an existing Xcode project where that package is linked.)
It seems that Xcode cannot find packages on my Mac (others have tried to find the packages the same package successfully.)

I have done all the things that I know of:

  • Restart Xcode and try again.
  • Clean Build Folder.
  • Ensure Xcode is updated.
  • Delete DerivedData .
  • Check the package URL and version.

no love.

2

What error does Xcode give? Does building from the command line work? Can you clone the repositories from the machine using git?

3

No error from Xcode. It just spins forever. Never finds the package.

I can clone and use the package by adding locally. Also all previously used packages work in other projects.

I was able to install the package on another Mac running Sonoma and Xcode 15.4. So it appears to be an Xcode 16.x or Sequoia issue. Two of my Macs running Sequoia/Xcode 16 have the same issue.

4

Solved:
I deleted all of my Xcode preferences after removing several swiftpm files & folders. I suspect it was the Xcode Preferences, since removing the github account had no effect.

Longer story: I have a second ID on this Mac that I use to record Kodeco videos. Earlier I switched to that account and tried to import the package. It worked, so it had to be some crap from the Mac Migration to this new M4 that was fubar.

1 Like
5

Actually - It’s my Bitbucket credentials which I need for jobby job!. As soon as I enter them in Xcode, Searching for Packages breaks. Remove the bitbucket credentials and it works again.

There was a SourceTree conflict a while back. I wonder if this is related.