-
Notifications
You must be signed in to change notification settings - Fork 16
all syncs failing (even creating new autoplaylists) #192
Comments
I have this issue and I'm using a Google Music free account. |
Huh, that's interesting. Can you email me logs from each account after triggering a sync? The possible link to something in Chrome isn't something I'd considered before, but makes sense in the context of the auth problems from a few weeks ago (that's managed entirely by Chrome). |
@simon-weber after the last batch of disabling/enabling the extension, revoking auth token / re-auth, and checking "enable change batching", the sync problems have disappeared. I still have a few errors and plenty of warning in my logs, I'll send them to you shortly. |
Everything has seemed to be working pretty smoothly lately. These changes ought to help prevent issues from popping up again. |
Simon,
Sadly I still have the same problem, on all PCs/laptops.
|
Gotcha. Can you export your logs and send them my way when you have a chance? |
Well... sigh, good timing: the first sync in about a month just completed
an hour ago without doing anything. So maybe it's fixed. Let me keep an eye
on it, and if it breaks again, I'll send them over.
I did try to manually sync just now and I got the typical "likely due to
problems on Google's end" warning message, is that expected?
|
Haha, excellent. That error isn't too surprising - if this is the first sync in a while it'd have a lot of changes - but let me know if you see it consistently. I've also got some new docs here that hopefully explain it more thoroughly. |
This consolidates multiple older issues (#189, #188, #187), all of which describe these symptoms:
These are all consistent with the usual "Google is overloaded" hypothesis from years ago, but seems different now since pausing syncs for a few days doesn't seem to help. It does not seem to be related to auth problems, which are all fixed now (according to my reporting).
I still don't have a great solution since I haven't been able to reproduce this myself yet. The best ideas I've got are:
The text was updated successfully, but these errors were encountered: