Commented Unassigned: sometimes remote db and cache are not synced [410]

I am using keepass2andoid 0.9.8c with a remote db on Google Drive (gdrive://user@gmail.com/xxx.kdbx) (Using a passphrase and a composite key that is stored locally.)

Everything wors fine at first but after some weeks, a remotely modified database won't be synced anymore.
Keepass2Android always says "remote database and cache match" or something like that. (My german version says "_Remote-Datei und Cache stimmen überein_".) Selecting synchronize database inside an opened database yields the same message.

I can verify that the remote file is updated by checking the timestamp in the android google drive app.

At this point the only way to switch to the current state of the remote database is to drop the current database cache completely by closing the database, removing it from the recently opened DBs and add it again.

Comments: did you do anything special with the file, e.g. rename it and copy another version to the same location? Note that Google Drive is very special with filenames - multiple files can even have the same name! (They have different IDs internally. In earlier versions I checked for the ID only but that had other issues.)