SolvedCocoaPods Pushing spec fails with Xcode 10 GM


pod trunk push fails with Xcode 10 GM with this error:

Validating podspec
 -> Kronos (3.0.0)
    - NOTE  | xcodebuild:  note: Using new build system
    - NOTE  | xcodebuild:  note: Planning build
    - NOTE  | xcodebuild:  note: Constructing build description
    - NOTE  | [iOS] xcodebuild:  note: Using build description '28b601d336dbb5ea0b7317d49a5058ff'
    - NOTE  | xcodebuild:  warning: Skipping code signing because the target does not have an Info.plist file. (in target 'App')
    - NOTE  | xcodebuild:  note: Using eager compilation
    - ERROR | [OSX] xcodebuild: Returned an unsuccessful exit code. You can use `--verbose` for more information.
    - NOTE  | [OSX] xcodebuild:  note: Using build description '832d3ee3de99c1899b48002e8b955a8d'
    - NOTE  | [tvOS] xcodebuild:  note: Using build description 'ac1be6e24fcb8433bfd3b0f07175c2fd'

I was able to work around this by forcing the old build system by changing this line to include -UseNewBuildSystem=NO

What did you do?

pod trunk push Kronos.podspec --swift-version=4.2

CocoaPods Environment

### Stack

  CocoaPods : 1.5.3
        Ruby : ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-darwin17]
    RubyGems : 2.7.6
        Host : Mac OS X 10.13.6 (17G2307)
      Xcode : 10.0 (10A254a)
        Git : git version 2.18.0
Ruby lib dir : /usr/local/Cellar/ruby/2.5.1/lib
Repositories : master - @ 18bd04a45f19f0cc3822aeeb319d35baced41d6d

### Installation Source

Executable Path: /Users/ksmiley/.gem/bin/pod

### Plugins

cocoapods-deintegrate : 1.0.2
cocoapods-plugins     : 1.0.0
cocoapods-search      : 1.0.0
cocoapods-stats       : 1.0.0
cocoapods-trunk       : 1.3.1
cocoapods-try         : 1.1.0

Project that demonstrates the issue

Pushing from this sha MobileNativeFoundation/Kronos@d38491d

19 Answers

โœ”๏ธAccepted Answer

Run gem install cocoapods --pre to install beta version 1.6.0.beta.1 fixes the issue for me

Other Answers:

@keith last thing "I promise"

I think you couldn't repro straight from Xcode because a) you had to select macOS target to build for and b) opening the workspace defaults to "Debug" configuration for the scheme versus the validator in the command line uses RELEASE so you would have to switch it to "Release" which would enable code sign and then eventually fail.

More Issues: