> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/ios/setup-luciq-for-ios/integrate-luciq-on-ios/migrating-from-cocoapods-to-spm.md).

# Migrating from CocoaPods to SPM

The CocoaPods registry goes read only on December 2, 2026. Move your iOS project from the Luciq pod to Swift Package Manager in four steps.

CocoaPods registry goes read-only on **Dec 2, 2026**. We recommend migrating existing iOS projects to **Swift Package Manager (SPM)**, which is now Luciq's recommended iOS integration method.

If your project currently uses CocoaPods, migrate to Swift Package Manager in four steps:

1. In your `Podfile`, remove the `pod 'Luciq'` entry (and any other Luciq pods you've added).
2. Run `pod install` to remove Luciq from the workspace.
3. In Xcode, choose **File → Add Package Dependencies..** and add `https://github.com/luciqai/luciq-ios-sdk`
4. Clean the build folder (**Product → Clean Build Folder**) and rebuild.

After the rebuild succeeds, your project is fully on SPM and can be updated following the Swift Package Manager (SPM) section of **Updating the SDK**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.luciq.ai/ios/setup-luciq-for-ios/integrate-luciq-on-ios/migrating-from-cocoapods-to-spm.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.