On Jan 11, 2016, at 3:43 PM, Brendan Duddridge 
<[email protected]<mailto:[email protected]>> wrote:

So I guess you're also not committing to master at the moment and you're just 
committing to the release/1.2 branch then?

There’s some post-1.2 stuff in the master branch, but most changes have been 
going into the release/1.2 branch. At this point master should be considered 
unstable; also we haven’t merged the latest 1.2 changes back into it yet.

I thought I had everything working with SQLCipher, but for some strange reason 
it's like your framework can find the libsqlcipher.dylib, but my main app 
cannot as I get crashes trying to call setKey (with FMDB) for the encryption 
key. It would be good if it was built-in to the framework and I didn't have to 
worry about it.

Our build engineer is working on an automated build of SQLCipher (for a 
dizzying variety of platforms that we support), and the plan is to include a .a 
file in the iOS archive.

Maybe it's time to just give up on SQLCipher and switch over to ForestDB. Do 
you thin ForestDB is ready for production? I've been using SQLCipher because 
the SQLite admin tools allow me to look into the database more easily to 
diagnose problems.

ForestDB is ready and supported on all 3 codebases in 1.2.
Have you tried the CBL Viewer app? It lets you look at the contents of 
databases.

—Jens

-- 
You received this message because you are subscribed to the Google Groups 
"Couchbase Mobile" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/mobile-couchbase/561C96DE-131A-4725-AA82-B42AA20A7604%40couchbase.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to