Fixed
Status Update
Comments
ku...@google.com <ku...@google.com>
mg...@google.com <mg...@google.com> #2
Some additional observations:
- It seems it has only a chance to happen on the first start after fresh install
- According to Crashlytics the number of crashes = number of affected users. Which could mean it only happens once on the first run and never again.
- Also we do have backups disabled
Can there be a race? Given the code of the Okio ReadScope
seems the file doesn't exist when it's tried to be opened, but exists shortly after that
return try {
fileSystem.read(
file = path
) {
serializer.readFrom(this)
}
} catch (ex: FileNotFoundException) {
if (fileSystem.exists(path)) {
throw ex
}
serializer.defaultValue
}
ku...@google.com <ku...@google.com> #3
Any update on the issue?
mg...@google.com <mg...@google.com> #4
We have the same issue. Did you try to update to 1.1.1?
ku...@google.com <ku...@google.com> #5
Update to 1.1.1 doesn't help.
ap...@google.com <ap...@google.com> #6
Any updates on that issue?
ku...@google.com <ku...@google.com>
na...@google.com <na...@google.com> #7
exact same issue, we went from 1.0.0 to 1.1.1 and are encountering this!
Description
- getBoolean
- getChar
- getDouble
- getFloat
- getInt
- getLong
It should be better if the behavior is consistent across different types on all platforms.