Room cannot verify the data integrity. Looks like you've changed schema but forgot to update the version number

[kuiper-lee]

12-24 21:12:35.920 6675 8461 E AndroidRuntime: FATAL EXCEPTION: pool-8-thread-1
12-24 21:12:35.920 6675 8461 E AndroidRuntime: Process: com.coloros.sceneservice, PID: 6675
12-24 21:12:35.920 6675 8461 E AndroidRuntime: java.lang.IllegalStateException: Room cannot verify the data integrity. Looks like you've changed schema but forgot to update the version number. You can simply fix this by increasing the version number.
12-24 21:12:35.920 6675 8461 E AndroidRuntime: at androidx.room.RoomOpenHelper.checkIdentity(SourceFile:154)
12-24 21:12:35.920 6675 8461 E AndroidRuntime: at androidx.room.RoomOpenHelper.onOpen(SourceFile:135)
12-24 21:12:35.920 6675 8461 E AndroidRuntime: at androidx.sqlite.db.framework.FrameworkSQLiteOpenHelper$OpenHelper.onOpen(SourceFile:195)
12-24 21:12:35.920 6675 8461 E AndroidRuntime: at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:427)
12-24 21:12:35.920 6675 8461 E AndroidRuntime: at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:316)
12-24 21:12:35.920 6675 8461 E AndroidRuntime: at androidx.sqlite.db.framework.FrameworkSQLiteOpenHelper$OpenHelper.getWritableSupportDatabase(SourceFile:145)
12-24 21:12:35.920 6675 8461 E AndroidRuntime: at androidx.sqlite.db.framework.FrameworkSQLiteOpenHelper.getWritableDatabase(SourceFile:106)
12-24 21:12:35.920 6675 8461 E AndroidRuntime: at androidx.room.RoomDatabase.inTransaction(SourceFile:476)
12-24 21:12:35.920 6675 8461 E AndroidRuntime: at androidx.room.RoomDatabase.assertNotSuspendingTransaction(SourceFile:281)
12-24 21:12:35.920 6675 8461 E AndroidRuntime: at androidx.work.impl.model.SystemIdInfoDao_Impl.getWorkSpecIds(SourceFile:120)
12-24 21:12:35.920 6675 8461 E AndroidRuntime: at androidx.work.impl.background.systemjob.SystemJobScheduler.reconcileJobs(SourceFile:298)
12-24 21:12:35.920 6675 8461 E AndroidRuntime: at androidx.work.impl.utils.ForceStopRunnable.cleanUp(SourceFile:245)
12-24 21:12:35.920 6675 8461 E AndroidRuntime: at androidx.work.impl.utils.ForceStopRunnable.forceStopRunnable(SourceFile:212)
12-24 21:12:35.920 6675 8461 E AndroidRuntime: at androidx.work.impl.utils.ForceStopRunnable.run(SourceFile:108)
12-24 21:12:35.920 6675 8461 E AndroidRuntime: at androidx.work.impl.utils.SerialExecutor$Task.run(SourceFile:91)
12-24 21:12:35.920 6675 8461 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
12-24 21:12:35.920 6675 8461 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
12-24 21:12:35.920 6675 8461 E AndroidRuntime: at java.lang.Thread.run(Thread.java:920)
12-24 21:12:39.171 8703 9270 E AndroidRuntime: FATAL EXCEPTION: pool-9-thread-1

workManager version is 2.7.0-alpha05

[alimuhammad1999]

https://stackoverflow.com/questions/44197309/room-cannot-verify-the-data-integrity

[kuiper-lee]

邮件我已经收到

[wilfredgicharu]

If that is the case, most likely you should not increment the database version. Simply clearing app data will move you passed the exception. If your app is live, you will likely need to increment the database version and provide a proper migration.

If you do not increment the database (recommended):

You should clear the application's app data from Android settings. You might alternatively be able to uninstall the previous app version and then install the new version to get passed the exception. This latter approach does not work under certain conditions (such as when allow backup is enabled)

Since clearing application data always works, I take that route every time.

If you do increment the database version:
You will need to write database migration code to account for any changes to the database schema. See here for information on migration.

Alternative to writing database migration code is to call fallbackToDestructiveMigration on the Room database builder. This is probably not a good idea as this change should not be published to actual users. Forgetting to remove this call and then forgetting to upgrade the database will result in data loss for users.

// Using this fallback is almost certainly a bad idea
Database database = Room.databaseBuilder(context, Database.class, DATABASE_NAME)
.fallbackToDestructiveMigration()
.build();
Again, neither incrementing the database version nor falling back to destructive migration is necessary if the previous database schema is not live in the wild.

[kuiper-lee]

邮件我已经收到

[wilfredgicharu]

没关系

…

On Mon, Mar 27, 2023 at 9:09 PM kuiper-lee ***@***.***> wrote: 邮件我已经收到 — Reply to this email directly, view it on GitHub <#283 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOIRMEE2E2KIJDZ5JNZIWADW6HJVBANCNFSM5PHI3L5Q> . You are receiving this because you commented.Message ID: ***@***.***>

[vipulm7]

Simply uninstall the app and reinstall it. Error will be fixed

[kuiper-lee]

邮件我已经收到

[hassanwasfy]

Hey guys, I have got the solution, I faced this issue and the problem was based on how the room works, I did find that room doesn't apply the Migration initially , but it keens on the Room database call back,

so as you can see in next code snippets :

the old code is :

@Database(entities = [User::class], version = 4, exportSchema = true)
abstract class AppDatabase : RoomDatabase() {
    abstract fun userDao(): UserDao

    companion object {
        private var dbInstance: AppDatabase? = null

        fun getInstance(appContext: Context): AppDatabase {
            if (dbInstance != null) {
                return dbInstance as AppDatabase
            }

            dbInstance = Room.databaseBuilder(appContext, AppDatabase::class.java, "Sample.db")
                .createFromAsset("database/myapp.db", Setup())
                .addMigrations(object : Migration(0, 1) {
                    override fun migrate(db: SupportSQLiteDatabase) {
                        db.execSQL("ALTER TABLE user ADD COLUMN email TEXT;")
                    }
                }, object : Migration(1, 2) {
                    override fun migrate(db: SupportSQLiteDatabase) {
                        db.execSQL("ALTER TABLE user ADD COLUMN age TEXT;")
                    }
                }, object : Migration(2, 3) {
                    override fun migrate(db: SupportSQLiteDatabase) {
                        db.execSQL("ALTER TABLE user ADD COLUMN birthDate TEXT DEFAULT 'H';")
                    }
                }, object : Migration(3, 4) {
                    override fun migrate(db: SupportSQLiteDatabase) {
                        db.execSQL("CREATE TABLE TEST (id INTEGER PRIMARY KEY, name TEXT)")
                    }
                })
                .build()
            Log.i("Key_Key", "Data base created successfully.")
            dbInstance!!.openHelper.writableDatabase
            return dbInstance as AppDatabase
        }
    }
}

this if you wanted to add columns like email, age, birthDay, or even add a new whole table.

this code is not going to work at all.

as the room will not see the updates for the first time,

all what you need is only setting up the room call back:

so be something like :

class Setup : RoomDatabase.PrepackagedDatabaseCallback() {
    override fun onOpenPrepackagedDatabase(db: SupportSQLiteDatabase) {
        super.onOpenPrepackagedDatabase(db)
        db.execSQL("ALTER TABLE user ADD COLUMN email TEXT;")
        db.execSQL("ALTER TABLE user ADD COLUMN age TEXT;")
        db.execSQL("ALTER TABLE user ADD COLUMN birthDate TEXT DEFAULT 'Y';")
        db.execSQL("CREATE TABLE TEST (id INTEGER PRIMARY KEY, name TEXT)")
    }
}

and you are ready to go.

i think there is more space to improve this solution , but till now we are so far so good.

happy coding 👍🏻 💯

[kuiper-lee]

邮件我已经收到