-
-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Refresh fails with SyntaxError: JSON.parse: unexpected end of data #248
Comments
I think there is some intermittent problem with Bing servers. I just clicked on "Refresh Now" and the image was replaced. Restarting the extension to resolve the problem was probably just a coincidence. I'll leave this open for now, perhaps there can be some improvement (retry mechanism?) based on this report, but otherwise this can be closed. |
Yeah the error notifications are new, these wouldn't have been apparent previously. Agree this shouldn't hassle users so much with non-fatal errors. (It should retry in 5 minutes.) |
This hasn't happened anymore since I reported it last week, so I'll close this (can't reproduce; as I already wrote it looks like an intermittent server-side problem). |
@neffo
|
It seems that the wallpaper API is simply blocked in my country, through VPN it works. Although I can still go to the Bing website and I see wallpapers there, apparently a different address is used there. |
Just to confirm, you are in Russia? There might be a redirect occurring that we aren't following. So does opening the link to the API end point give any error messages? One option might be to select a different market in the settings (like English rest of world, etc). |
@neffo |
Describe the bug
The extension is unable to download images anymore (I am guessing that parsing API response from the Bing site is the problem; perhaps something is not working reliably there).
Screenshots
To Reproduce
Steps to reproduce the behavior:
Desktop:
Additional context
This started happening around 1-2 days ago (perhaps with the extension upgrade to version 50?), yesterday I resolved the problem by reloading the extension in the "gnome extensions" dialog (switching it off and then on again), but this does not seem to be working today. The destination directory has all necessary permissions (is user writable).
journal log:
The text was updated successfully, but these errors were encountered: