I have a small application that reads and writes files using the Google Android Android API. Locally, everything works fine on one client: I store files using the Drive API and read them the next time I run without any problems. However, when I read the same files on another device with the same application, the files sometimes get corrupted. Files are JSON files, and the parser complains about the absence of quotes or curly braces. If I view files using the Google Drive web interface, I can verify that the contents of the file are invalid. It seems that the old content is partially overwritten by the new contents of the file.
Could this be a user problem? I think this could be a Drive Drive problem, because locally everything is fine, and the API does not seem to provide a way to store invalid data remotely, but valid data locally. The first step to file an error against the Google Drive API seems to be to reach a consensus on StackOverflow, so I would also be interested if anyone else sees a similar problem.
So my questions are:
- Perhaps this is a user problem (if so, how)?
- Has anyone else seen similar problems?
android google-drive-android-api
Stefan Haustein Dec 29 '15 at 23:53 2014-12-29 23:53
source share