The version of CocoaPods used to generate the lockfile (X.X.X) is higher than the version of the current executable (X.X.X)

With Capacitor 5, the CocoaPods lock file, ios/App/Podfile.lock, is no longer included in your ios/.gitignore.

During the build process in Appflow, CocoaPods uses your Podfile.lock to install your dependencies. If the version of CocoaPods used to generate the lock file does not match the version of CocoaPods used in Appflow, your Appflow build may fail with an error like the following:

✖ update ios - failed!
[error] [!] The version of CocoaPods used to generate the lockfile (1.12.1) is higher than the version of the current executable (1.12.0). Incompatibility issues may arise.
        Analyzing dependencies
        Adding spec repo `trunk` with CDN `https://cdn.cocoapods.org/`
        
        CocoaPods 1.12.1 is available.
        To update use: `gem install cocoapods`
        
        For more information, see https://blog.cocoapods.org and the CHANGELOG for this version at https://github.com/CocoaPods/CocoaPods/releases/tag/1.12.1
        
        Verifying no changes
        [!] There were changes to the lockfile in deployment mode:
        COCOAPODS:
        New Lockfile: 1.12.0
        Old Lockfile: 1.12.1

While CocoaPods will fall back to installing dependencies from your Podfile if your Podfile.lock is not committed, it will return an error if the lock file is present but the versions are mismatched. 

To resolve this, you can either remove the Podfile.lock from your repository by adding it back into your ios/.gitignore, or you can locally install the version of CocoaPods used by Appflow and regenerate your lock file. We recommend the latter, as committing the lock file ensures that the same versions of your dependencies are installed each build.

To install a specific version of CocoaPods, you can use the -v flag with gem install.

sudo gem install cocoapods -v 1.12.0

See our build stacks reference to identify the CocoaPods version used in each Mac build stack.