I can't pick anything obvious, unless the app is still finding a copy of the database left on the device/workspace
One thing I'd say, is that (Golum voice) 'we hates SQL written like that' - its so error prone, and from a lot of personal experience with SQLite (not Android), it does funny things sometimes with column names and spacing... usually we/I would suggest parameterised queries etc, I don't know if you can in your Android framework - you can tidy the statement up a bit using this technique
https://shyr.io/blog/android-create-tables-in-sqlite-beautifully[
^] which would also make it less error-prone (ie, use a builder to build the SQL