updating to sqlcipher-android from android-database-sqlcipher file is not a database (code 26)

[xuhongchang]

from android-database-sqlcipher 4.5.4 to sqlcipher-android4.5.6
receive some error
If it is a new installation, it is not a problem, only the overlay installation is a problem
here is log:
Failed to open database
android.database.sqlite.SQLiteException: file is not a database (code 26): , while compiling: SELECT COUNT(*) FROM sqlite_schema;
at net.zetetic.database.sqlcipher.SQLiteConnection.nativePrepareStatement(Native Method)
at net.zetetic.database.sqlcipher.SQLiteConnection.acquirePreparedStatement(SQLiteConnection.java:973)
at net.zetetic.database.sqlcipher.SQLiteConnection.executeForLong(SQLiteConnection.java:628)
at net.zetetic.database.sqlcipher.SQLiteConnection.open(SQLiteConnection.java:240)
at net.zetetic.database.sqlcipher.SQLiteConnection.open(SQLiteConnection.java:202)
at net.zetetic.database.sqlcipher.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java:475)
at net.zetetic.database.sqlcipher.SQLiteConnectionPool.open(SQLiteConnectionPool.java:189)
at net.zetetic.database.sqlcipher.SQLiteConnectionPool.open(SQLiteConnectionPool.java:181)
at net.zetetic.database.sqlcipher.SQLiteDatabase.openInner(SQLiteDatabase.java:1028)
at net.zetetic.database.sqlcipher.SQLiteDatabase.open(SQLiteDatabase.java:1013)
at net.zetetic.database.sqlcipher.SQLiteDatabase.openDatabase(SQLiteDatabase.java:840)
at net.zetetic.database.sqlcipher.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:359)
at net.zetetic.database.sqlcipher.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:278)

[xuhongchang]

sqlcipher-android4.5.6 version
use code :
public SQLiteOpenHelper(Context context, String name, byte[] password, CursorFactory factory,
int version, int minimumSupportedVersion,
DatabaseErrorHandler errorHandler, SQLiteDatabaseHook databaseHook,
boolean enableWriteAheadLogging)

android-database-sqlcipher 4.5.4 version
use code:
public SQLiteOpenHelper(Context context, String name, SQLiteDatabase.CursorFactory factory, int version, SQLiteDatabaseHook hook) {
this(context, name, factory, version, hook, new DefaultDatabaseErrorHandler());
}

public synchronized SQLiteDatabase getWritableDatabase(String password) {
    return this.getWritableDatabase(password == null ? null : password.toCharArray());
}

[developernotes]

Hi @xuhongchang,

What happens when you retrieve your existing database file off the Android device and attempt to access it within DB Browser for SQLite ¹?

Footnotes

1. https://nightlies.sqlitebrowser.org/latest/ ↩

[xuhongchang]

how to upgrade android-database-sqlcipher 4.5.4 to sqlcipher-android4.5.6 ? Android system.
I referenced the migration documentation：https://www.zetetic.net/sqlcipher/sqlcipher-for-android-migration/

If it is a new installation, it is not a problem, only the overlay installation is a problem

here is log:
Failed to open database
android.database.sqlite.SQLiteException: file is not a database (code 26): , while compiling: SELECT COUNT(*) FROM sqlite_schema;
at net.zetetic.database.sqlcipher.SQLiteConnection.nativePrepareStatement(Native Method)
at net.zetetic.database.sqlcipher.SQLiteConnection.acquirePreparedStatement(SQLiteConnection.java:973)
at net.zetetic.database.sqlcipher.SQLiteConnection.executeForLong(SQLiteConnection.java:628)
at net.zetetic.database.sqlcipher.SQLiteConnection.open(SQLiteConnection.java:240)
at net.zetetic.database.sqlcipher.SQLiteConnection.open(SQLiteConnection.java:202)
at net.zetetic.database.sqlcipher.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java:475)
at net.zetetic.database.sqlcipher.SQLiteConnectionPool.open(SQLiteConnectionPool.java:189)
at net.zetetic.database.sqlcipher.SQLiteConnectionPool.open(SQLiteConnectionPool.java:181)
at net.zetetic.database.sqlcipher.SQLiteDatabase.openInner(SQLiteDatabase.java:1028)
at net.zetetic.database.sqlcipher.SQLiteDatabase.open(SQLiteDatabase.java:1013)
at net.zetetic.database.sqlcipher.SQLiteDatabase.openDatabase(SQLiteDatabase.java:840)
at net.zetetic.database.sqlcipher.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:359)
at net.zetetic.database.sqlcipher.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:278)

[developernotes]

Hi @xuhongchang,

What happens when you pull the existing database off the Android device and access it with the password using DB Browser for SQLite ¹?

Footnotes

1. https://nightlies.sqlitebrowser.org/latest/ ↩

[andzhangs]

我结合Room数据库使用时，也遇到了同样的问题，你最后是怎么解决的了？
android.database.sqlite.SQLiteException: file is not a database (code 26): , while compiling: SELECT COUNT(*) FROM sqlite_schema; at net.zetetic.database.sqlcipher.SQLiteConnection.nativePrepareStatement(Native Method) at net.zetetic.database.sqlcipher.SQLiteConnection.acquirePreparedStatement(SQLiteConnection.java:973) at net.zetetic.database.sqlcipher.SQLiteConnection.executeForLong(SQLiteConnection.java:628) at net.zetetic.database.sqlcipher.SQLiteConnection.open(SQLiteConnection.java:240) at net.zetetic.database.sqlcipher.SQLiteConnection.open(SQLiteConnection.java:202) at net.zetetic.database.sqlcipher.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java:475) at net.zetetic.database.sqlcipher.SQLiteConnectionPool.open(SQLiteConnectionPool.java:189) at net.zetetic.database.sqlcipher.SQLiteConnectionPool.open(SQLiteConnectionPool.java:181) at net.zetetic.database.sqlcipher.SQLiteDatabase.openInner(SQLiteDatabase.java:1028) at net.zetetic.database.sqlcipher.SQLiteDatabase.open(SQLiteDatabase.java:1013) at net.zetetic.database.sqlcipher.SQLiteDatabase.openDatabase(SQLiteDatabase.java:840) at net.zetetic.database.sqlcipher.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:359) at net.zetetic.database.sqlcipher.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:278) at net.zetetic.database.sqlcipher.SupportHelper.getWritableDatabase(SupportHelper.java:60) at androidx.room.RoomDatabase.inTransaction(RoomDatabase.kt:638) at androidx.room.RoomDatabase.assertNotSuspendingTransaction(RoomDatabase.kt:457) at androidx.room.RoomDatabase.compileStatement(RoomDatabase.kt:502)

[xuhongchang]

@andzhangs 后来我没升级库了 从 android-database-sqlcipher 4.5.4 到sqlcipher-android4.5.6
继续使用的
android-database-sqlciphe 只是升级了一下版本
这是两个库

[EpariNigam]

Hi I am also facing same issue. I tried opening with DB browser, I am able to open though.

I tried migrating from net.zetetic:android-database-sqlcipher:4.5.4 to net.zetetic:sqlcipher-android:4.5.4.

Here is a sample repo, I have created

https://github.com/EpariNigam/SQLCipher

[developernotes]

Hi @EpariNigam,

Your demo application does not call System.loadLibrary("sqlcipher");.

[EpariNigam]

Hey @developernotes

I created 2 branches the main branch uses the old library, the new branch sql_cipher_migration uses the new library.

I request you to run the app from main branch, do click insert and fetch. See, entries got created.

Now from the sql_cipher_migration just click fetch, you will be able to reproduce the issue.

[EpariNigam]

Hi @developernotes hope with the mentioned provided steps, you are able to reproduce this issue.

[developernotes]

Hi @EpariNigam,

In your branch sql_cipher_migration, your implementation of getBytes is incorrect. You are converting the string, to a char array, then converting the char array to a string (which no longer represents the original string), then requesting the bytes for that string ¹. SQLCipher is not able to open an existing encrypted database with invalid password material.

If you change the EncryptedAppDatabase.kt file to define the passphrase as follows it works properly:

val passPhrase = "mydatabasekey".toByteArray(Charsets.UTF_8)

Footnotes

1. https://github.com/EpariNigam/SQLCipher/blob/sql_cipher_migration/app/src/main/kotlin/com/nigam/dbsqlcipher/db/EncryptedAppDatabase.kt#L53-L56 ↩

[EpariNigam]

Thanks @developernotes I will give it a try and let you know.

[EpariNigam]

Thanks @developernotes, it worked. I though toString() will just give the output of String. But, forgot that it is an array and will give hashcode 🤦‍♂️.

[developernotes]

Hi @EpariNigam,

No problem at all, glad the issue is resolved for you!