[eDrive] - help cloud to restore valid timestamp for files

• /e/ version:
• Device model(s):
• Developer mode enabled: yes/no
• Device rooted: yes/no
• Trackers blocker enabled: yes/no

Summary

Unindentified (yet) element causes invalid timestamp on cloud side due to synchronization with eDrive. The invalid timestamp is set to max value of unsigned int 32 for files, on lasModified, creationTime & even uploadTime. This doesn't allow any fix directly on server side.

The only solution is to force reupload of those file with correct values from devices.

The problem

Steps to reproduce Have one file with invalid timestamp (max of uint 32) on cloud

What is the current behavior? invalid timestamp

What is the expected correct behavior? timestamp is restored

Technical informations

4294967295 is the max for 32bit uint

Relevant logs (adb logcat)

Relevant screenshots

Solutions

The solution to force reupload, is to add a check when we scan remote file. If we find a remote file with the invalid timestamp, then we have to force upload request for the file

Workaround

Possible fixes