title: Xcode 10 build fails with 'Command CompileSwift failed with a nonzero exit code
body: <p>I updated Xcode to version 10 recently and started to receive a strange error when trying to build my project. I'm currently on Swift 4.0 and I did try to upgrade to swift Version 4.2. But when I did I received this same error in many of my frameworks.</p>
  
  <blockquote>
    <p>Command Compile Swift failed with a nonzero exit code</p>
  </blockquote>
  
  <p>So far I've deleted the derived folder. Updated all pods, also deleted all pods and reinstalled them using the terminal commands below.</p>
  
  <pre><code>sudo gem install cocoapods-deintegrate cocoapods-clean
  pod deintegrate
  pod clean
  pod install
  </code></pre>
  
  <p>This didn't work to fix my issue. However, I found something that could work which was adding <code>arm64</code> architecture in <code>Build Setting -&gt; valid architectures</code> and enabling automatic code But, when I checked it was already there and code signing was enabled already. </p>
  
  <p>Additionally, I do have a few other build errors that have to do with frameworks. </p>
  
  <p><strong>SwiftMessages</strong>  </p>
  
  <blockquote>
    <p>Value of type 'SwiftMessages.Config' has no member 'presentationContext'</p>
  </blockquote>
  
  <p><strong>WhatsNewKit</strong> </p>
  
  <blockquote>
    <p>Missing argument for parameter 'backgroundColor' in call`</p>
  </blockquote>
  
  <p>I opened issues with the developers of each of these frameworks to seek help with these issues.</p>
  
  <p><a href="https://github.com/SwiftKickMobile/SwiftMessages/issues/229" rel="noreferrer">Issue On SwiftMessage GitHub</a>
  <a href="https://github.com/SvenTiigi/WhatsNewKit/issues/5" rel="noreferrer">Issue On WhatsNewKit GitHub</a></p>
  
  <p>When I click <code>presentationContext</code> it brings me to the struct within the <code>SwiftMessages</code> Framework. Usually, when I've had the "has no member" warning I cannot click to see the original place where it exists.</p>
  
  <p>I assume this has something to do with cocoa pods, but haven't been able to find a solution yet. What can I do to correct this issue? If anyone could help would be deeply appreciated been stuck on this for a day now.</p>
  
  <p>Update:
  The two frameworks latest builds were for swift 4.2. When I changed the version of each framework to one that was built in swift 4.0 I got the project to build.</p>