Migrating to SQLDriver with Room3

[InputOutputZ]

Hi there,

I'm not sure from where to start but I have two questions that will determine if there is a bug, documentation is not complete or this issue ticket should be a feature request.

Here is a context, I have checked the source code of Room3 and sqlcipher-android, it doesn't look like it has addressed the removal of openHelperFactory as part of SupportSQLiteOpenHelper.

If this is true, will sqlcipher-android support Room3 and when?
if this is false, is there anyone knows and can hint out how to configure sqlite database with SupportOpenHelperFactory i.e. encryption key using Room3 and allows overriding create function so encryption key can be cleared from memory after use?

Setting driver have only one option that is the name of the database file, which can be set. Also, there is only option to change password after building the database, anyone have an idea better than me?

With thanks.

Zakaria.

Refer to
https://android-developers.googleblog.com/2026/03/room-30-modernizing-room.html
https://developer.android.com/jetpack/androidx/releases/room3

[sjlombardo]

Hello @InputOutputZ - we're aware of the upcoming changes in Room 3. However, SQLCipher does not support Room 3 at this time due to the changes. Since Room 3 is still in alpha status it is still on our pending list. We will work on updating the integration as Room 3 stabilizes.

[InputOutputZ]

Hello @InputOutputZ - we're aware of the upcoming changes in Room 3. However, SQLCipher does not support Room 3 at this time due to the changes. Since Room 3 is still in alpha status it is still on our pending list. We will work on updating the integration as Room 3 stabilizes.

Thanks for clearing the confusion. Btw, I actually managed to get Room 3 working with SQLCipher, but just failed clearing the key from the initialised variable it holds, while I tried using postKey function with SQLiteDatabaseHook, but it fails decrypting database in subsequent keying calls. While it works using Room 2 and openHelperFactory method.

Please if you can do take note of this, and I hope when SQLCipher team is going to package for Room 3 to address this issue, since it really hurts keeping the encryption key in memory loaded for as long as the database connection is needed, sometimes like all the time and this is a huge security risk.

Zakaria.

[InputOutputZ]

Also, debugging SQLCipher encrypted database using Android Studio Database inspector, I think if you provide support for this, it would be a great feature. Please do take note of this as well,

With thanks.

Zakaria.