IssueTracker

Component used: androidx.room:room-compiler

Version used: 2.5.0-alpha02, 2.5.0-alpha03

Devices/Android versions reproduced on: Samsung Galaxy S21 / Android 12

I've updated the Room version from 2.4.3 to 2.5.0-alpha03 and after the last migration, the JSON generated will once in a while fail with

Caused by: java.lang.IllegalStateException: Cannot parse existing schema file: C:\mypath\com.example.MyDatabase\74.json. If you've modified the file, you might've broken the JSON format, try deleting the file and re-running the compiler. 
If you've not modified the file, please file a bug at 
https://issuetracker.google.com/issues/new?component=413107&template=1096568 
with a sample app to reproduce the issue.   
    at androidx.room.vo.Database.exportSchema(Database.kt:111)  
    at androidx.room.DatabaseProcessingStep.process(DatabaseProcessingStep.kt:123)  
    at androidx.room.compiler.processing.CommonProcessorDelegate.processRound(XBasicAnnotationProcessor.kt:123)     
    at androidx.room.compiler.processing.javac.JavacBasicAnnotationProcessor.process(JavacBasicAnnotationProcessor.kt:71)   
    at org.jetbrains.kotlin.kapt3.base.incremental.IncrementalProcessor.process(incrementalProcessors.kt:90)    
    at org.jetbrains.kotlin.kapt3.base.ProcessorWrapper.process(annotationProcessing.kt:197)    
    at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:985)    ... 44 more

After checking out the differences between the last schema file 73.json and the new one, 74.json, apart from the changes I've wanted to make, there's this block:

    "SHADOW_TABLE_NAME_SUFFIXES": [
      "_content",
      "_segdir",
      "_segments",
      "_stat",
      "_docsize"
    ],
    "shadowTableNames$delegate": {
      "initializer": {},
      "_value": {}
    },

inside the only ftsVersion block I have. Whatever I write in the migration script doesn't matter, I always get the same issue. If I delete the .json, an identical one regenerates, which works fine the first time but then crashes the second time. What I've found is that if I delete the SHADOW_TABLE_NAME_SUFFIXES and shadowTableNames$delegate blocks from 74.json, I don't get the issue anymore.

I've attached a demo app in which I've reproduced the issue, however, I must mention that initially, it worked fine up to the 3rd database version. How I've managed to reproduce the issue on the demo app is as follows:

1. run the app with 2.5.0-alpha03
2. updated room to 2.4.3
3. rerun it with 2.4.3, worked fine,
4. uninstalled the app
5. reinstalled it with 2.5.0-alpha03, crashed.