FMDB w/SQLCipher and an App Clip about fmdb HOT 6 OPEN

@knightcode

This is most likely an integration issue rather than a defect with either FMDB or SQLCipher. When using FMDB in conjunction with SQLCipher you'll want to use the FMDB/SQLCipher suspec rather than standalone FMDB with SQLCipher separately. Using SQLCipher with other libraries/frameworks which have a dependency on standard sqlite carries multiple inherent risks, including undefined behavior, deadlocks, loss of data, loss of encryption functionality, etc.

When using SQLCipher it is recommended that you check the result of the cipher_version PRAGMA to confirm that your application is actually using SQLCipher. There's an example of doing that with FMDB in my comment here: #821 (comment)

from fmdb.

@R4N is that available through SPM? I have to downgrade to cocoapods? ... I was so close getting use of my xcconfig back :/

from fmdb.

@knightcode

SQLCipher isn't available through SPM. There's discussion about that in this post: sqlcipher/sqlcipher#371 which links over to the Swift forums which explains the blocker: https://forums.swift.org/t/plugin-generated-header-files-are-not-available-from-project/56875

from fmdb.

It's not that hard to wrap the headers in a framework. Do they just want to hold us hostage?

from fmdb.

@R4N I still don't see what's stopping you from publishing a properly linked framework as a swift package

from fmdb.

@knightcode Please see me colleagues comment in the other thread linked in my earlier comment: sqlcipher/sqlcipher#371 (comment)

from fmdb.