Bug #6905
File and folder timestamp negative numbers
| Status: | New | Start date: | 03/29/2016 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | 0.3 | |||
| Component: |
Description
Hello,
Development is on Android SDK 23 with gradle dependency: info.guardianproject.iocipher:IOCipherStandalone:0.3
I am creating files in an encrypted file system and when I inspect the timestamp the time is negative like -562935428000.
Creating directories has the same problem, negative timestamps.
The same operations on Android's non-encrypted file system work fine.
Thanks in advance for your help,
Matt
History
#1 Updated by knewye almost 2 years ago
Using file.setLastModfied( System.currentTimeMillis() ) does not correct the problem.
#2 Updated by hans almost 2 years ago
we haven't so far really paid attention to timestamps because we haven't needed them. In theory, they are already supported, but I guess there are bugs.
#3 Updated by knewye over 1 year ago
File timestamps are granular to 1 second and currentTimeMillis to 1 ms, hence divide by 1000.
It should be: Using file.setLastModfied( System.currentTimeMillis()/1000 ) does not correct the problem.