How to delete Swift Package Dependency in Xcode 11?

Question

I have a project in Xcode 11 that I added Swift Package Manager dependencies to. I now realized that I no longer need one of the package dependencies I previously added to my project.

As you can see below, there are no options under File > Swift Packages for deleting a packager from Swift Package Manager for this project.

I have tried removing the package from the array in the project.xcworkspace/xcshareddata/swiftpm/Package.resolved file. But it still doesn't remove it from Xcode, and the next time I Update to Latest Package Versions it readds the entry to the Package.resolved file.

How can I delete a Swift Package Manager dependency in my project?

Slicer

I am unable to follow any of the answers to this question in Xcode 13 – Bayberry

Navigate to the youAppName.xcodeproj file and access the "Package Dependencies" section in the top bar. Once there, open the "Packages" tab, where you'll find a list of packages. You can delete a package there. – Garrote

Answer 1

1. Open Xcode
2. Select your project
3. Look at the top middle
4. Select Swift Package Manager menu

You'll be able to manage your packages (add / remove)

Carcinoma

@CharlieFish You can right-click and delete in the sidebar all you want! It just doesn't do anything. 😂 – Dybbuk

I tried the steps above and I still can't remove the dependency! – Particularize

Warning: Xcode 11.7 (11E801a) crashes when I attempt to remove Swift Packages this way (-[__NSSetM addObject:]: object cannot be nil, sending removeItems: to Xcode3PackageReferenceListViewController from <DVTGradientImageButton: 0x7fce1a7d83d0>) – Westphal

I don't understand the instructions. What window is this? – Freezedry

@xinux, you have to click on your project at the top of the file navigator then it will convert your center view that normally houses code or interface builder into this project view. – Towelling

The fact that I had to google it and that this is actually a stupid issue -> bad apple. – Rollerskate

Update: in Xcode 13.3 the tab is called "Package Dependencies" – Nobe

Too bad I can't upvote this twice. I ran into the same problem a second time; found this answer and realized I have already upvoted it... thanks again. – Garver

Thanks for this. Quite perplexing that Apple makes it easy to Add and Update packages, but not Remove? – Satori

Oh nice why put all relevant controls in in one place when you can scatter them across two interfaces. – Tulatulip

Also nice to see that you can select "add package dependency" from the file menu, then click "recent" (or something like that) and see the package that you just installed, you can right-click and select "remove". It will disappear from the list but remain in your project. Just in case you want to do such a thing. It's one of Xcode's amazing features. – Tulatulip

Answer 2

select your project and move to the package dependencies tab then select and remove

Please follow the image

Caruthers

You'd think there would be a simple "left click -> remove" under the "Package Dependencies" lol – Counterreply

@PaulCarlton brother you are too much genius. But do you know that everything start from zero. I think no one come here for learning shortcut right. I just give a simple solution. Please don't de-motivate anyone. Sorry for interrupt – Caruthers

Answer 3

Swift Package Manager(SPM) Dependency

Add dependency

1. Project Settings contains information about dependencies. 
2. File -> Swift Packages -> Add Package Dependency...
3. Target -> General -> Frameworks, Libraries, and Embedded Content -> Add Items -> Add Other... -> Add Package Dependency...

Target Settings includes product from dependency

Edit dependency

To edit URL you can edit .pbxproj with repositoryURL

Delete dependency

Project -> Packages -> <Select dependency> -> -

[Local Swift Package Manager(SPM)]
[iOS Dependency manager]

Mcpherson

Confirmed this is the most direct answer to the question. Reproducible in Xcode 14 – Wage

Answer 4

Dependencies keep poping up even after remove pod and reinstall pod.

Uncinus

Answer 5

Please follow the steps below to remove a particular package from the Xcode project smoothly.

3d

this is what finally worked for me – Mercer

well explained. – Touraco

Answer 6

In addition to Pierre's answer, this was driving me crazy, I had a sub project that I was editing, I forgot about that (it was in a subfolder). Even though I removed it in the "Swift Packages" pane it kept coming back. Removing that sub folder reference made sure the PM dependencies went away.

Rosas

Answer 7

I removed the swift package, but its dependancies were still showing in the project. I saw the swift package was still in the Frameworks folder at the bottom of left pane,

I removed it from there and the dependencies are gone.

Electrolyze

Answer 8

Firstly I removed it from dependencies and targets in Package.swift, then i regenerated my project file with swift package generate-xcodeproj

Corpulent

Answer 9

Nested Swift Package Dependencies

Background

As other answers have mentioned, we can import Swift Packages into a project very easy through the File -> Swift Packages -> Add Package Dependency workflow, and that works for the majority of applications. I have added this answer as a further optimisation for packages with nested dependencies.

Swift Packages are imported not just with the Git source code checkout, but also with one, or several Package Products. In my case, I wanted to keep the Package because I used it in one target but not in another target. Sometimes a Package contains multiple dependencies which we don't need, and this is a great opportunity to prune unused dependencies.

Unused imports

I recently made a mistake where I automatically imported all the modules referenced by a Swift Package dependency, even those I don't need. This is common because Packages can have multiple Products which each expose different APIs for different applications.

If you aren't sure if you need an import, check it and delete it. For example, a Package could include an Objective-C Module that adds an additional unnecessary import.

In my case, I imported a Swift Package that was exported via multiple nested libraries: OHHTTPStubs and OHHTTPStubsSwift in the above example.

General idea

We can delete nested Swift Package dependencies via Build Phases or the Target General settings tab without deleting the Package itself. Deleting unnecessary dependencies is a good practice to save your app's memory footprint and also streamlines build times.

Nested Dependencies for Unit/UI Testing

Each target should only import the libraries it uses.

Rules:

1. Import only the Swift Package Manager Products you actually need when importing for the whole project. Import only the wrapper subspec if that is all you use.
2. The Host Application Target doesn't need to import UI testing libraries. We can safely delete these libraries from the Target General tab in Frameworks, Libraries, and Embedded Content. This will automatically unlink the Product from the Build Phases tab for this Target.
3. Our UI Testing Target can import the Package Products it needs via Build Phases -> Link Binary with Libraries. If a dependency is only used in UI Tests, delete it from the Host Application Target Frameworks, Libraries, and Embedded Content.
4. The Unit Testing Target can't link to libraries that are not embedded in the Host Application. Thus, we need to add products used in Unit Tests to the Host Application Target in the General settings tab for Frameworks, Libraries, and Embedded Content. We DON'T need to add any Products to Link Binary with Libraries for the Unit Tests Target.

Example from my experience

OHHTTPStubsSwift is the equivalent Swift CocoaPods subspec that adds a nicer API wrapper over the ObjC API but already imports the ObjC API (OHHTTPStubs).

I deleted the Package Products from the Host Target because I was only using it in UI Tests. I then only imported the OHHTTPStubsSwift via Build Phases.

Shipe

This is a better response for me than using "Swift Package" menu, because I did installed FirebaseKit, but needed to add the Database module. With the "Swift Package" menu I just could remove all than install again, choosing Database option at this step. This is not exactly the question above, but your way can do the both. – Schism

Answer 10

There's no answer to what I've found. If the git link has been broken, *.xcodeproj/project.pbxproj must be changed to the proper link. Xcode will catch the modification and update automatically.

Seiler

Answer 11

try deleting the package dependencies and reinstalling using the latest major version (i.e. 10.0.0). i downloaded realm using swift package manager with the latest version 10.48.1 and couldnt import swiftRealm. make sure to add to target. after adding the dependencies it automatically updated to latest version since i used dependency rule "up to next major version"

Scoundrel

This does not provide an answer to the question. Once you have sufficient reputation you will be able to comment on any post; instead, provide answers that don't require clarification from the asker. - From Review – Unciform

Answer 12

Step 1. Navigate to your project directory. Step 2. Find 'your-project.xcodeproj' Step 3. Open it in text editor, not Xcode (you have to use finder and use any text editor by opening with-all applications -> text editor Step 4. Search for all instances of the package in question, for instance...I had a package 'UIKit' that was causing issues, and I just removed any instances of it and made sure not to disturb the rest of the file. Step 4. Open/Re-open xcode project with xcode and enjoy.

Twain