mobile application shows asset is not backed up but web shows it's backed up
I'm using 1.51.2 server with 1.51.0b74, and the thumbnails randomly don't show up, also, the sync status says not synced, but the web application shows those images, I tried to do a manual re sync, but no joy.
19 Replies
When you click on the thumbnail, does it show the actual photo?
No
Something wrong with the mount?
There might be logs in the server indicate error messages
Other images are loading. The ones with the icons showing
unless something that have been modified on the database or file system level, I cannot think of any other reasons
You will have to check the logs
That entire date of yesterday was uploaded together.. 1st image though
What about the sync status ?
What sync status are you mentioning about?
See the original image I mentioned under Wednesday. That shows this image and a few others as not sync.. but you can see in the web browser, its been uploaded
If you reinstall the app, does it help?
If it does not, we just merged an improvement for the local sync process on the mobile app which will be available in the next release
Let me check this later from work... Got a VPN between home and work.. give me a bit, just getting there
How/ what to check here
I have a similar issue. If I delete an image off my device after it's been backed up, it appears as a black square with an uploaded icon, but won't let me preview the file from the server.
It appears fine on the web UI tho
does it help is you log out and log back in? it might be a sync issue
That does work, but I have to do that every time I upload something then delete it off my device to get it working again. It's weird tho because some of the photos (the two appearing in the screenshot) just worked, and idk why.
We will look into this sync issue
thank you for reporting
@zody if you have a better where to look into this, let me know and I can take a look at the code
There are quite a number of possibilities here.
@X̷͝͞҉e͢r̸̢͘a҉̧z҉͟à̶͡l͡ can you check if pull-to-refresh resolves the issue? The first time is a normal refresh. if you do a second pull-to-refresh just after the first has finished, it performs a full re-sync which might already solve your problem (no need to logout+login)
Second pull works and fixes the issue. Didn't know that pull-to-refresh had different functionality like that.
Excellent!
Hidden feature for troubleshooting 🙂
I'll do some digging why the normal refresh might fail to work correctly