iOS build failing / SDK update problems / CocoaPods trouble

#1

Hi all, thanks in advance for your help and attention.

I’m trying to re-build a project to deploy to testflight/connect/etc. It’s expired, but built fine a few months ago. When I try to rebuild it, I’m told there’s an SDK version issue:

[06:06:44]: [Transporter Error Output]: description length:10500450
[06:08:55]: [Transporter Error Output]: ERROR ITMS-90725: “SDK Version Issue. This app was built with the iOS 11.4 SDK. All iOS apps submitted to the App Store must be built with the iOS 11 SDK or later, included in Xcode 9 or later. Further, starting March 2019, all iOS apps submitted to the App Store must be built with the iOS 12.1 SDK or later, included in Xcode 10.1 or later.”
[06:08:55]: Transporter transfer failed.
[06:08:55]:
[06:08:55]: description length:10500450
ERROR ITMS-90725: “SDK Version Issue. This app was built with the iOS 11.4 SDK. All iOS apps submitted to the App Store must be built with the iOS 11 SDK or later, included in Xcode 9 or later. Further, starting March 2019, all iOS apps submitted to the App Store must be built with the iOS 12.1 SDK or later, included in Xcode 10.1 or later.”

Apart from this error (the last step in the workflow), everything builds successfully – and I’m presented with an .ipa to download if I choose.

Fine, I think, I’ll clone the repo, open up the project in xcode and thereby update the sdk version. This just seems to mean more problems (see log below)… When I try to build this version through bitrise, I encounter the following issue with cocoapods:

Resolving dependencies of Podfile
[!] CocoaPods could not find compatible versions for pod “DoubleConversion”:
In snapshot (Podfile.lock):
DoubleConversion (from ../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec)
In Podfile:
DoubleConversion (from ../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec)
None of your spec sources contain a spec satisfying the dependencies: DoubleConversion (from…/node_modules/react-native/third-party-podspecs/DoubleConversion.podspec), DoubleConversion (from…/node_modules/react-native/third-party-podspecs/DoubleConversion.podspec).
You have either:

  • out-of-date source repos which you can update with pod repo update or with pod install --repo-update.
  • mistyped the name or version.
  • not added the source repo that hosts the Podspec to your Podfile.
    Note: as of CocoaPods 1.0, pod repo update does not happen on pod install by default.

I cannot build the project offline as CocoaPods isn’t locally installed – it only comes in through the bitrise process. My podfile clearly points to (it seems to me) the right location/repo for DoubleConversion.podsec, so I’m baffled as to why it’s now failing to find it.

Curiously, if I do try to install cocoapods locally and build the project through xcode, I encounter the same error. I can override this error by running ‘npm install’ before ‘pod install’ – after this, it seems to find the dependencies just fine.

So yeah, I’m a bit stumped!

Environment:

Where did the issue happen?

Bitrise, Xcode 9.4.x
but I’ve also tried on 11.0.x

Which build Step causes the issue and which version of the step?

cocoapods-install@1.7.2

Reproducibility

  • 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) : NO
  • Does the issue happen sporadically, or every time? : EVERY TIME
  • Does upgrading the build Step to the latest version help? : NO
  • When did the issue start? : LAST WEEK

Build log

Please copy paste the build’s bitrise.io URL here (or if the issue happens somewhere else then the full logs), or if you can’t share the url / log here then send the url or full log through a private channel (e.g. email - https://www.bitrise.io/contact ), with a link to the related Discuss issue.


0 Likes

#2

Here’s the log for the previous build that indicated SDK problems, by the way (but which otherwise built successfully): https://drive.google.com/open?id=1KRwpZWG7Jl97MyLqr1II3T3u_d6MHwRb

1 Like

#3

Hi @davidlebor!

Sorry for the delay here, is this issue still persistent?

Have you tried to run a pod install --repo-update already?

0 Likes

closed #4

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

0 Likes