Creating this issue as something to have on record.
To provide some context:
This application makes use of the 'watcher' package.
Now, this 'watcher' can have some unusual behaviour under Linux. If itself is at fault, I don't know. As you may know, Android utilises the Linux kernel. Android also has its own twists to it, among other things.
Now, the issue. It appears that if the file selection is specifically stored under the application's cache and the application gets put into the background (i.e. multitasking) and maybe switching between apps doing whatever, the 'modify' event can fire off in the background for that file actively being served.
I haven't dug too deep into what actually gets modified, if it even gets modified at all, but I see no reason for the file to get supposedly modified in any way in this case.
This was noticed with two devices now (Pixel 6 [stock], OnePlus 6T [custom ROM]), both on the December 2023 releases of Android 14. The issue was noticed during the development of v2.3.0, but it was very unclear as to what was going on and it looked like it only happened very few times.
The next release, v2.3.1, will exclude this check for files copied into application cache. This means that modifications would only be checked when it comes to files in internal shared storage (through Direct Access Mode).
So, if you had experienced the issue.. whoopsie. Try giving v2.3.1 a shot, once that is out.
Creating this issue as something to have on record.
To provide some context: This application makes use of the 'watcher' package. Now, this 'watcher' can have some unusual behaviour under Linux. If itself is at fault, I don't know. As you may know, Android utilises the Linux kernel. Android also has its own twists to it, among other things.
Now, the issue. It appears that if the file selection is specifically stored under the application's cache and the application gets put into the background (i.e. multitasking) and maybe switching between apps doing whatever, the 'modify' event can fire off in the background for that file actively being served. I haven't dug too deep into what actually gets modified, if it even gets modified at all, but I see no reason for the file to get supposedly modified in any way in this case.
This was noticed with two devices now (Pixel 6 [stock], OnePlus 6T [custom ROM]), both on the December 2023 releases of Android 14. The issue was noticed during the development of v2.3.0, but it was very unclear as to what was going on and it looked like it only happened very few times.
The next release, v2.3.1, will exclude this check for files copied into application cache. This means that modifications would only be checked when it comes to files in internal shared storage (through Direct Access Mode).
So, if you had experienced the issue.. whoopsie. Try giving v2.3.1 a shot, once that is out.