File is corrupt; length stored in header is 0, how to detect issue?

[danvinokour]

Regarding a previously closed issue:
#135

We uploaded the file, it has a size of 4k and it has only zero's there.
a valid file has 1000 in the second column, first row.
We dont have any clue why it is corrupt.

we have also more info about the path and the permissions is has and everything seems legit:
taskqueue.db File exists, getAbsolutePath=/data/data/com.XXX/files/taskqueue.db
canRead=true
canWrite=true
canExecute=false
getAbsolutePath=/data/data/com.XXX/files/taskqueue.db
length=4096
taskqueue.db.tmp File does exist=false
getAbsolutePath=/data/data/com.XXX/files
getFreeSpace=6080581632
getTotalSpace=12802191360
getUsableSpace=6058561536
canWrite=true
canRead=true
getPath=/data/data/com.XXX/files
getCanonicalPath=/data/data/com.XXX/files

what can we do to analyze it further?

[guillaumelachaud]

I can report the same. I have two users to whom this also happens. A few details:

User1:
Model: SM-S820L
OS: Android 4.4.4

User2:
Model: SAMSUNG-SM-G920A
OS: Android 7.0