Bugsee Logo
June 16, 2026

CocoaPods is going read-only: Bugsee's last CocoaPods release is August 2026

Alexey Karimov
Alexey Karimov

If you install the Bugsee iOS SDK with CocoaPods, this post is for you. CocoaPods — the dependency manager that has delivered Bugsee to iOS apps since our earliest releases — is winding down, and its central package index is moving to read-only later this year. Here is exactly what that means for Bugsee, the timeline you can plan around, and the two well-supported alternatives we recommend moving to.

What is happening to CocoaPods

The CocoaPods maintainers have announced that the project is entering long-term maintenance mode, and that the CocoaPods Trunk — the central service that hosts every published podspec — will transition to read-only later in 2026. In a read-only world the index keeps serving the versions that are already there, but no new pods or new versions can be pushed. The ecosystem has been consolidating around Apple’s first-party Swift Package Manager for several years, and this is the final step in that shift.

This is an industry-wide change, not a Bugsee-specific one — but it does change how, and for how long, we can publish new SDK releases through CocoaPods.

What it means for Bugsee on CocoaPods

We will keep publishing new Bugsee releases to CocoaPods on our normal cadence right up until the cutover:

  • Through August 2026 — business as usual. Every new Bugsee iOS release lands on CocoaPods exactly as it does today. August 2026 will be the last month we publish to CocoaPods.
  • From September 2026 onward — we stop publishing new artifacts to CocoaPods. New Bugsee versions, fixes, and features will be released exclusively through Swift Package Manager and Carthage.

To be clear about what does not break: because the CocoaPods index becomes read-only rather than disappearing, every Bugsee version we have already published stays installable. An existing pod 'Bugsee' entry pinned to a version released in August 2026 or earlier will continue to resolve and build. What you will not get after August is anything new — no further SDK updates, no bug fixes, no new platform support — for as long as you stay on CocoaPods.

What you should do: move to SPM or Carthage

Both of our other distribution channels receive every Bugsee release and will continue to do so. If you integrate Bugsee through CocoaPods today, we recommend switching before the August cutover so you never miss an update.

Swift Package Manager (recommended)

SPM is Apple’s built-in, first-party dependency manager and the path we recommend for every iOS project. In Xcode, open File → Add Package Dependencies…, paste the Bugsee package URL, and pick the latest version:

https://github.com/bugsee/spm

Once the Swift Package is added, remove the pod 'Bugsee' line from your Podfile and run pod install to drop the old integration. Your code does not change — import Bugsee stays exactly the same.

Carthage

If you prefer Carthage, add the Bugsee binary to your Cartfile:

binary "https://download.bugsee.com/sdk/ios/dynamic/Bugsee.json"

then run:

carthage update

Full, step-by-step integration instructions for all three options live in the iOS installation guide.

Timeline at a glance

  • Now → August 2026 — Bugsee publishes to CocoaPods, SPM, and Carthage as usual. A good window to migrate.
  • August 2026 — the final Bugsee release published to CocoaPods.
  • September 2026 onward — new releases ship via SPM and Carthage only; already-published CocoaPods versions remain installable but frozen.
  • Later in 2026 — CocoaPods Trunk goes read-only ecosystem-wide.

Questions?

If you are unsure which option fits your project, or you hit anything while migrating, we are happy to help — reach out via the in-app support chat or email support@bugsee.com. We would rather help you move now, on your own schedule, than have you discover a missed update later.