[admin edit: I’ve moved your topic to its own topic as you have CLZ Comics, and sync issues can be various things, it is highly unlikely the same issue]
I am using clz comics and having the exact same issue. It keeps giving a time out synch error when I try uploading to the cloud 50+ changes.
This error has been occurring for about a month now. I have previously wiped the data from the app, which didn’t help, and even uninstalled/reinstalled the app, which also didn’t help.
I had left the app in auto-synch but that didn’t seem to be uploading.
What happened exactly when you removed and reinstalled the app, and then synced? Did it complete at all at that point?
How is your internet connection? I see you are on “5G UC” which is “ultra capacity” but I’m also seeing threads on Reddit that say that for some people it means spotty/slow and problems with big data transfers.
Can you try with WiFi and see if it finishes then? If not, read on:
I see 772 comics in your Cloud, is that correct? Is that your entire database?
If so, can you try the reinstall again?
reinstall the app again
sync, using wifi.
do not use auto sync, just leave the app on the sync screen.
When I removed the app all data on the phone was wiped. It would be a fresh install at that point. I would download from CLZ cloud and start again. The error seems to be when making edits to characters / creators that affect more than 50 books. When I have many changes to upload, it has the error.
Normally the internet connection seemed to be fine. But home has WiFi and work sometimes does not. I’ll try to make note of that in the future. My home PC never has time out errors.
Yes, that’s my entire database.
Following the advice of the prior thread, I previously would start the app in manual synch, then switch to auto-synch and leave it alone for 10+ mins. It will eventually synch. I was not giving the app enough time previously when I thought the auto-synch was not working.
No, when I switched it to Auto-synch and let it sit for 10 mins it finally did it’s job. But this kept happening many times in the prior month… when I wasn’t on WiFi.
As you pointed out, that might be a culprit. I’ll monitor where I am and the type of connection present from here forward.
