Library on NAS shows "new files" every scan/update

Library and comic files on a NAS share, previously local but was running low on space

Every library "scan" results in all titles being marked new (yellow)

Things I've tried:
Setting to "compare modified dates of files--not recommended"
Setting to "consider recent items added XX-days" Several values

Thanks,
G~

How long does it take to update? Does the app show the covers of previously added comics in the importing view?

Whats the local path to the library?

Disable the dates checking. And put the slider to the left (1 day), if you wait 24h without doing an update do the recent added marks go away?

It sounds like the app is having troubles reading some information about the files. When the dates checking is disabled the app just compares file sizes to decide if a comic file has changed or not.

I noticed it takes quite longer on the share vs local. Opening a book doesn't take long, but scanning does.

1200 files/ 65 folders takes 50 seconds

Path to the library: L: \\192.168.1.75\comics Microsoft Windows Network

I had only toggled the date checking for one test. It's disabled.

Slider is set to one day.

Yes if I wait 24hours without scan, the recently added marks go away.

Just a note that problem still exists. Any logs or debugging setup I could perform?

Scheduled scans will also trigger the "new mark" for all files.

I think that the network file system may be providing the wrong file size. Can you send me the .ydb file inside .yacreaderlibrary (this folder is inside your library)

Thanks! Sent via email to support email.

Apologies for a bump of an old thread, but wanted to record a solution as found.

It makes zero sense to me as to why. But a simple copy of the exact files to a new share folder along with metadata file and creation of a new library solved the problem.

Only ONE thing changed. The previous files/metadata were in the root of a shared filesystem and this one I created a folder called COMICS to move all of them into.

Anyways. Thanks for the troubleshooting on this when it first popped up. Appreciated.

G~