title: ObjectiveDropboxOfficial.framework fails with dyld`__abort_with_payload
body: <p>I'm upgrading to the new V2 Dropbox API, following the <a href="https://github.com/dropbox/dropbox-sdk-obj-c#carthage" rel="nofollow noreferrer">Carthage install instructions</a>. It compiles fine but when it starts to run, it fails with <code>dyld __abort_with_payload</code>.</p>
  
  <p><a href="https://stackoverflow.com/a/42185158">A similar question</a> indicated to put the framework into <code>Embedded Binaries</code> instead of `Linked Frameworks and Libraries'. I tried this and it worked, sort of. </p>
  
  <p>I then fixed what I thought was a typo in a path, removed it from the <code>Embedded Binaries</code> list and it still worked, but for this target only. Other targets configured in the exact same manner AFAICT still fail.</p>
  
  <p>Is there a subtle configuration I may have missed, or may have automatically been added when I used <code>Embedded Binaries</code>, that may be left over even though it is no longer in use?</p>
  
  <p>I don't think the Embedded Binaries should be needed to link a framework, and it is not documented to be necessary.</p>
  
  <p><strong>Edit:</strong> [adding Obj-C as this is likely a linking problem]</p>
  
  <p>The framework is a dynamic framework, identified using the instructions from <a href="https://stackoverflow.com/a/32591983/5135551">this post</a>. I added the framework to the <code>Embedded Binaries</code> making the app run. However, if I take it out of <code>Embedded Binaries</code>, it still runs, but didn't previously with the same configuration AFAIK. Something subtle I don't understand has been changed.</p>
  
  <p><strong>Edit 2:</strong></p>
  
  <p>I initially used <code>Embedded Binaries</code> as it seemed to work and not have the dyld failure. However, when I built as an archive and validated with the App Store, it failed to validate with several failures: <code>Unsupported Architectures</code>, <code>Invalid Segment Alignment</code>, <code>LC_ENCRYPTION_INFO load command is either missing or invalid</code></p>