Thanks @sjlombardo. Would be great to get the list of known issues & fixed bugs in 4.4.2 (reported from previous versions). This will help us make a more informed decision on consuming newer versions.
Hello @rsarma - I’d be happy to provide some additional details. The main issue that was resolved in 4.4.2 had to do with a potential corruption bug. It has the potential to affect applications using WAL journal in circumstances where the underlying cryptographic provider encountered an error during an encryption operation inside a WAL frame write. We are only aware of incidents occurring in Electron-based applications, but would recommend that any applications using WAL journal mode upgrade.
In addition, while there are no known issues with the OpenSSL cryptographic provider, we did make some simplifications in this version. We would therefore recommend upgrading for applications using OpenSSL, i.e. for any non-iOS and non-macOS platforms.
Hi, is there any dependency list for sqlcipher 4.4.2?
I tried to find out which version of openssl sqlcipher is denpends on.But nothing relative mentioned in release note.
Hello @Simson - SQLCipher should work with any modern version of OpenSSL, there isn’t a specific dependent version. If you are building SQLCipher yourself you’ll need to provide link and compile time information to the version installed. If you are using Commercial Edition packages everything is statically linked so there are no runtime dependencies.
I struggling with similar issue esp. on BlueStacks 4 (Nouget framework) in which when I try to install any sort of 3rd party virtual space ( you name them, Parallel Space, Virtual Xposed, Go Multiple). After installation, when trying to launch application I get below hard error:
Detected problem with app native libraries
(please consult log for details)
libsqlcipher_android.so: unauthorized access to libutils.so"
libsqlcipher_android.so: unauthorized access to libcutils.so"
libdatabase_sqlcipher.so: unauthorized access to libnativehelper.so"
libdatanase_sqlcipher.so: unauthorized access to libandroid_runtime.so"
libdatabase_sqlcioher.so: unauthorized access to libbinder.so"
The next thing, application tend to close. I have been going through threads linked to this issue dated back from origin year of 2016. I am not a qualified techie, not sure how can I run sqlcipher on BlueStacks. Where can I find console of BlueStacks to write and execute the script?
I would really appreciate your input ang guidance here.
Our most recent release was SQLCipher 4.4.3. If you were on a previous 4 series release of SQLCipher you can upgrade by adjusting your reference to the latest release version. If you were using a previous major version of SQLCipher, you will want to investigate the migration and compatibility options available to determine your upgrade approach.
Would you try reviewing the SQLCipher for Android integration documentation? Are you using the Community edition, or Commercial edition of the software? It may be helpful to create a separate thread that details any additional questions you may have after reviewing the documentation. Thanks!
E/ROOM: Invalidation tracker is initialized twice :/.
E/AndroidRuntime: FATAL EXCEPTION: arch_disk_io_1
Process: net.mysample.sampledatabase, PID: 7150
net.sqlcipher.database.SQLiteException: no such table: room_table_modification_log: , while compiling: SELECT * FROM room_table_modification_log WHERE invalidated = 1;
at net.sqlcipher.database.SQLiteCompiledSql.native_compile(Native Method)
at net.sqlcipher.database.SQLiteCompiledSql.compile(SQLiteCompiledSql.java:89)
at net.sqlcipher.database.SQLiteCompiledSql.(SQLiteCompiledSql.java:62)
at net.sqlcipher.database.SQLiteProgram.(SQLiteProgram.java:91)
at net.sqlcipher.database.SQLiteQuery.(SQLiteQuery.java:55)
at net.sqlcipher.database.SQLiteDatabase.query(SQLiteDatabase.java:2958)
at net.sqlcipher.database.SQLiteDatabase.query(SQLiteDatabase.java:2948)
at androidx.room.RoomDatabase.query(RoomDatabase.java:328)
at androidx.room.RoomDatabase.query(RoomDatabase.java:311)
at androidx.room.InvalidationTracker$1.checkUpdatedTable(InvalidationTracker.java:414)
at androidx.room.InvalidationTracker$1.run(InvalidationTracker.java:388)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:764)
Is that exception somehow addressed by the updates:
The following summarizes the most substantial changes to SQLCipher core:
Improved error handling to resolve potential corruption if an encryption operation failed while operating in WAL mode
Changes to OpenSSL library cryptographic provider to reduce initialization complexity
Is this the first version that includes Apple M1 (arm64) processors support?
In that case, is supported only by Commercial and Enterprise packages or Community too?
Hello @rcalderon Yes, 4.4.2 was the first version to include the support in Enterprise and Commercial packages. Community Packages are compiled from source by the developer and as a result the supported platforms depends on how they are built.