# No callback after sqlite3\_key when using CocoaPods

**URL:** <https://discuss.zetetic.net/t/no-callback-after-sqlite3-key-when-using-cocoapods/1532>\
**Category:** SQLCipher\
**Created:** [July 18, 2016, 8:58am UTC](https://discuss.zetetic.net/t/no-callback-after-sqlite3-key-when-using-cocoapods/1532 "2016-07-18T08:58:59Z")\
**Posts on this page:** 1\
**Showing post:** 23

<div class="post-metadata">

**Author:** ![sjlombardo](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.zetetic.net/sjlombardo/32/3_2.png) [@sjlombardo](https://discuss.zetetic.net/u/sjlombardo)\
**Post date:** [September 14, 2016, 9:48pm UTC](https://discuss.zetetic.net/t/no-callback-after-sqlite3-key-when-using-cocoapods/1532/23 "2016-09-14T21:48:26Z")

</div>

Hello @nullproduction The podspec is already resulting in the inclusion of -framework SQLCipher, however, because of your other dependencies the standard sqlite3 library is being linked first. The manual project level change forces SQLCipher up front. To be frank, this isn’t really a supported scenario, and using this approach is a risk. There could be other undefined behavior. Here is a link to some [guidance we just published about SQLCipher with XCode 8 and iOS 10](https://discuss.zetetic.net/t/important-advisory-sqlcipher-with-xcode-8-and-ios-10/1688), for reference.

---

_[View the full topic](https://discuss.zetetic.net/t/no-callback-after-sqlite3-key-when-using-cocoapods/1532)._