> 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

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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.