If you manage an iOS project or develop apps using Google Maps, the window for action is rapidly closing. On August 18, 2025, Google officially placed CocoaPods support into maintenance mode. We have now reached the final phase.
By Q2 2026, Google will stop releasing new versions of the Maps, Places, and Navigation SDKs via CocoaPods entirely. Version 11.0 and all future updates will be exclusive to Swift Package Manager (SPM).
Failing to migrate leaves your app stuck on an outdated SDK, missing new features, performance improvements, and vital security updates. Staying with old dependency managers poses both technical debt and security risks in the fast-paced iOS landscape.
What is Inside This Guide
Strategic Audit: Deciding between a full or hybrid migration.
Step by Step Execution: Stripping legacy files without breaking the build.
Official Sources: Verified links to Google’s announcements and documentation.
1. Choose Your Migration Path
Depending on your project's complexity, you have two ways to handle this.
Option A: The Full Migration (Preferred)
Use this if all your dependencies support SPM. We highly recommend deleting CocoaPods entirely to reduce build overhead and simplify your CI/CD pipeline.
Run these in your terminal:
sudo gem install cocoapods-deintegrate cocoapods-clean
pod deintegrate
pod cache clean --all
rm Podfile Podfile.lock
rm -rf Pods/
rm -rf YourProject.xcworkspace
From now on, use your .xcodeproj file to manage the project.
Option B: The ‘Hybrid’ Approach
Use this if you have legacy pods that do not support SPM yet. You can keep CocoaPods for those specific libraries while moving Google Maps over to SPM.
Modify your Podfile: Delete only the Google Maps related lines (e.g., pod 'GoogleMaps').
Update your pods: Run pod install in the terminal. This removes the Google Maps binary while leaving your other pods intact.
Clean Cache: In Xcode, press Cmd + Shift + K to ensure no old headers remain.
2. Integration via Swift Package Manager
Now that the old SDK is removed, follow these steps to link the modern version:
Open your project in Xcode.
Navigate to File > Add Package Dependencies.
Enter the URL: https://github.com/googlemaps/ios-maps-sdk.
Set the Dependency Rule to Up to Next Major Version (target 11.0.0 for the Q2 release).
Select the specific SDKs your app needs.
CocoaPods vs. SPM for Google Maps SDK: The 2026 Breakdown
While CocoaPods served us for years, Google’s shift to SPM is required to unlock Version 11.0+
| Feature | CocoaPods (Legacy) | Swift Package Manager (2026) |
| Max SDK Version | Stuck at v10.x | v11.0+ (Latest) |
| OS Support | Legacy focus | iOS 26/27/28 Optimized |
| Maintenance | Ruby/Manual updates | Native Xcode integration |
| Build Speed | Slower (Dynamic) | Faster (Static/Native) |
| Security | Frozen/Critical Risk | Active Patching |
Official Sources and Documentation
For technical verification and deeper reading, consult these primary sources:
Need more guidance?
If your team is facing complex dependency conflicts or needs help refactoring a legacy map implementation, I’m available for technical consultation.
Reach out at: hello@sajidhasan.com
