Pod install failed on ONLY Xcode 11.1 stack

Bitrise Build Issue Report template

Description of the issue

pod install failed on ONLY Xcode 11.1 stack.
When we use Xcode 11.0 stack, it succeeded.

[01:11:37]: -----------------------
[01:11:37]: --- Step: cocoapods ---
[01:11:37]: -----------------------
[01:11:37]: $ bundle exec pod install
[01:11:39]: ▸ Analyzing dependencies
[01:11:39]: ▸ Cloning spec repo `millsdk` from `https://github.com/millsdk/Spec.git`
[01:11:40]: ▸ [!] CocoaPods could not find compatible versions for pod "AlamofireObjectMapper":
[01:11:40]: ▸ In snapshot (Podfile.lock):
[01:11:40]: ▸ AlamofireObjectMapper (= 5.2.1)
[01:11:40]: ▸ In Podfile:
[01:11:40]: ▸ AlamofireObjectMapper
[01:11:40]: ▸ None of your spec sources contain a spec satisfying the dependencies: `AlamofireObjectMapper, AlamofireObjectMapper (= 5.2.1)`.
[01:11:40]: ▸ You have either:
[01:11:40]: ▸ * out-of-date source repos which you can update with `pod repo update` or with `pod install --repo-update`.
[01:11:40]: ▸ * mistyped the name or version.
[01:11:40]: ▸ * not added the source repo that hosts the Podspec to your Podfile.
[01:11:40]: Exit status of command 'bundle exec pod install' was 31 instead of 0.

pod install is ran by fastlane.


ONLY on stack of Xcode 11.1.
It is not happen on stack of Xcode 11.0


  • Does a “Rebuild” help? (You can trigger a rebuild from the Build’s page, by clicking the “Rebuild” button in the top right corner of a finished build) : YES
  • Does a rebuild without caches help? (You can remove the Cache:Pull and Cache:Push steps temporarily to not to use the cache, or you can delete all the caches on the Settings tab of the app. : YES
  • Does the issue happen sporadically, or every time? : every time
  • Does upgrading the build Step to the latest version help? : YES
  • When did the issue start? : 1 weak ago

Local reproduction

Didn’t try it. Because I think, Xcode 11.1 stack has this issue.

Build log

Here is Xcode 11.0 stack log. It is succeeded

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Hi @rikusouda,

Sorry for us leaving your report unattended for so long. Is this problem persistent at all? Seems like Xcode 11.0 has a Cocoapod version of 1.7.5 while 11.1 has 1.8.0 - so possibly a pod repo update might solve this :thinking: