You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When downloading files to device, sometimes (after a recent update, very often) the local file's last modification time is reset to the current time, instead of being preserved as it is on the cloud.
A workaround I found is to clear the cache, and then download the oter really quickly.
Reproduction Steps
Go to the photos tab, timeline view.
Click on a photo. View it for a couple seconds, scroll to its neighbors.
Click the download icon in the top right.
Go to the gallery app and observe the file date (likely) set to the current time.
If it didn't work, try again. For me this happens more than half the time now.
Expected behavior
The downloaded photos should have the same mtime as the ones I originally uploaded. This behavior should be consistent every time.
Additional context
I've found out after some quick research that there was, apparently, a bug in Android that sometimes prevented mtime from being updated on an existing file. I don't know it it is related to the problem at hand, but if so, the recommended workaround was to set the correct mtime at file creation, rather than updating it later.
That said, I suspect there's probably an automatic mtime update taking place domewhere along the way when files are downloaded to the cache and then copied from there instead of downloading again. I'd appreciate, if no better solution is found, a configuration option to always redownload files from the cloud when clicking on the download button rather than using the cache. Of course, if you find that the problem is actually elsewhere, please ignore this suggestion.
The text was updated successfully, but these errors were encountered:
I noticed a related issue: even already downloaded photos occasionally seem to have their mtime updated to a later date. I've had it happen twice now. Both times were at least several hours after I last opened the MEGA app, and I have no folder sync active on my phone.
Environment:
Describe the bug
When downloading files to device, sometimes (after a recent update, very often) the local file's last modification time is reset to the current time, instead of being preserved as it is on the cloud.
A workaround I found is to clear the cache, and then download the oter really quickly.
Reproduction Steps
Expected behavior
The downloaded photos should have the same
mtime
as the ones I originally uploaded. This behavior should be consistent every time.Additional context
I've found out after some quick research that there was, apparently, a bug in Android that sometimes prevented
mtime
from being updated on an existing file. I don't know it it is related to the problem at hand, but if so, the recommended workaround was to set the correctmtime
at file creation, rather than updating it later.That said, I suspect there's probably an automatic
mtime
update taking place domewhere along the way when files are downloaded to the cache and then copied from there instead of downloading again. I'd appreciate, if no better solution is found, a configuration option to always redownload files from the cloud when clicking on the download button rather than using the cache. Of course, if you find that the problem is actually elsewhere, please ignore this suggestion.The text was updated successfully, but these errors were encountered: