Closed f00b4r0 closed 9 months ago
Should be fairly simple to verify that there's an active archive at the address, and also handle when an archive starts 404ing later due to it being removed.
There's another fix for this that doesn't require fast clicking - the pocket-sync.json
file contains a fetches
array where they're stored on the device. Removing the invalid fetch from there would also fix it
Describe the bug Pocket Sync becomes unusable if an invalid Internet Archive fetch is setup.
As soon as the Fetch section is opened and the remote fetch is "loaded", the software will error and all interface buttons yield the same error message (Fetch: null, Settings: null, Pocket Sync: null, etc - followed by the same backtrace).
Clicking "Retry" changes the last 4 lines, subsequent clicks trigger no further changes:
To Reproduce Steps to reproduce the behaviour:
Wait for "Loading..." to run in the Fetch list and observe the crash.
To recover from this situation (from the GUI): quit, restart Pocket Sync, click "Fetch" and immediately click "Remove" on the offending fetch before it has time to load. Pocket Sync may still crash once again but after quitting and restarting Pocket Sync once more the offending fetch will be gone and the crash will no longer occur.
Expected behaviour An error message can be reported and the fetch invalidated without crashing the entire software.
Logs The fetch is setup at 10:01:46
After quitting Pocket Sync the following last line is output:
Desktop (please complete the following information):
Additional context There's also a window size / scrolling issue (buttons become unreachable) when setting up this bug that I will report separately (#245)