Sync not working from iOS

Hello, I just set up my library with YACReader and I really like your software. Thanks for your work!
I am running a YACReaderLibraryServer on Ubuntu via Docker image, and updating the library with YACReaderLibrary on macOS. Sync is working perfectly when using the macOS reader.

I also bought the iOS app and, while I can successfully connect to the server and pick up a comic from the last page synced from the macOS YACReader, I cannot seem to update my read status from the iOS app. Whenever I close a comic, the "Loading... synchronizing" indicator appears but then the comic always remains at the last page set by the macOS reader.

I checked the permissions of my Docker image and they should be ok, as I can successfully create a file in the comics folder from inside the Docker image.

Any idea on how I can fix this?

Thanks

I just think the docker container can’t write to disk. Can you try to use touch to create a file from the container in /comics/.yacreaderlibrary

If the volume where the comics are is SMB share in Ubuntu then the cause would be the database not being able to create a lock file, you need to mount the volume using the nobrl option.

Hello,
thank you for your reply.

I can successfully create a file from the container; I used
sudo docker exec YACReaderLibraryServer touch /comics/.yacreaderlibrary/foo

the file "foo" is created with the correct user/group.

I also tried to add the nobrl option to the fstab entry, but the problem still occurs.

Can you succesfully update the library from the container instead of from macos?

I am going to add some tools/checks to the next version to make all this easier to diagnose.

Actually it seems like updating the library from the docker container doesn't work.
I added a few files in the folder and started the update process; it reports the correct number of new comics found, but the db is not updated. Looking at the folders' timestamps, it seems that the main folder ".yacreaderlibrary" gets updated and the "covers" folder gets updated too, but the db file remains with the date of the last successful update.

Then the problem is 100% the database not being able to create the lock file, make sure that you are using nobrl correctly or you can also try with nolock

It worked with nobrl! I just needed to restart the container after remounting the samba network.
Thank you for your help!