title: Consequences of "Embedded dylibs/frameworks only run on iOS 8 or later" warning
body: <p>With Xcode 6.x we can use CocoaTouch Framework template to build a framework library and Xcode will create the .framework for us when we build, which is awesome. In our framework we want to support iOS 7.1 and up, so for Deployment Target (in our framework) we specified 7.1. Now when we build we see a warning: "Embedded dylibs/frameworks only run on iOS 8 or later". I've since read a number of blog posts on the subject that as far as running it on iOS 7.1 this warning can be ignored because it will run fine (still need to test to make sure). What concerns me is that I read a post on Stack Overflow which says an app may be rejected by Apple in the App Store (see: <a href="https://stackoverflow.com/questions/25909870/xcode-6-and-embedded-frameworks-only-supported-in-ios8/25910262#25910262">Xcode 6 and Embedded Frameworks only supported in iOS8</a>)</p>
  
  <p>Does it only apply when in Xcode the app links to it in General > Embedded Libraries?</p>
  
  <p>The way we want our customers to link to our framework is:</p>
  
  <ol>
  <li>Via CocoaPods</li>
  <li>By referencing .framework in Build Phase > Link Binary With Libraries</li>
  </ol>
  
  <p>I need to understand under what conditions App Store will reject an app which uses our CocoaTouch framework and supports 7.x iOS.</p>