Resolving CocoaPods Dependency Conflicts in Flutter iOS Projects: Firebase/CoreOnly Version Incompatibility

Problem Background and Error Analysis

During Flutter project development, when upgrading Flutter packages to the latest versions, iOS platforms often encounter CocoaPods dependency management errors. A typical error message shows: [!] CocoaPods could not find compatible versions for pod "Firebase/CoreOnly". This error typically occurs when multiple Firebase-related plugins have different version requirements for the core library Firebase/CoreOnly.

Root Cause Analysis

From the provided error logs, we can see that the project contains two plugins with conflicting version requirements for Firebase/CoreOnly:

• cloud_firestore plugin requires Firebase/CoreOnly (= 6.0.0)
• cloud_functions plugin requires Firebase/CoreOnly (= 5.18.0)

CocoaPods, as an iOS dependency management tool, cannot simultaneously satisfy these two conflicting version constraints, thus throwing a compatibility error. This issue is particularly common when mixing different versions of Firebase plugins.

Core Solution

Based on the Stack Overflow answer with a score of 10.0, the following systematic solution steps are recommended:

Step 1: Update CocoaPods Repository

First execute the pod repo update command to ensure the local CocoaPods repository contains the latest dependency version information. This step can resolve version resolution issues caused by outdated local repository information.

Step 2: Clean and Reinstall Dependencies

If the first step doesn't resolve the issue, perform a more thorough cleanup operation:

1. Delete the Podfile.lock file in the project root directory
2. Run the pod install command to regenerate dependency relationships

The Podfile.lock file records the exact versions of currently installed dependencies. Deleting this file forces CocoaPods to re-resolve all dependency relationships, which typically resolves version conflicts.

Supplementary Solutions

Based on practical experience from other answers, the following methods can serve as effective supplementary solutions:

Adjust iOS Platform Version

In some cases, adjusting the iOS platform version in Podfile can resolve compatibility issues. For example, changing platform :ios, '9.0' to platform :ios, '10.0', then re-running pod install.

M1 Chip Mac Specific Solutions

For developers using Apple Silicon Macs, additional steps may be required:

1. Install x86 architecture ffi library: sudo arch -x86_64 gem install ffi
2. Update repository using x86 architecture: arch -x86_64 pod repo update
3. Install dependencies using x86 architecture: arch -x86_64 pod install

Preventive Measures and Best Practices

To avoid similar dependency conflict issues, developers are advised to:

• Regularly update all Firebase-related plugins to compatible versions
• Check version compatibility between plugins before upgrading
• Use the flutter pub outdated command to check for outdated dependencies
• Maintain timely updates of CocoaPods and Flutter toolchains

Technical Principle Deep Analysis

CocoaPods uses semantic version control to manage dependency relationships. When multiple dependencies impose conflicting version requirements on the same library, the dependency resolver cannot find a solution that satisfies all constraints. In such cases, either the conflicting dependencies need to be upgraded to compatible versions, or cache cleaning and re-resolution are required to find feasible version combinations.

The modular design of the Firebase ecosystem allows different services to be updated independently, but also increases the complexity of version management. Developers need to ensure that all Firebase-related plugins use compatible SDK versions to avoid version conflicts in core libraries.