Closed johannesjo closed 4 years ago
Thanks for the report!
Unfortunately, I cannot reproduce this error.
... here's what a normal startup should look like btw:
If you don't see "rs.on ready", that means the entire app wasn't loaded correctly in the first place...
Hmhm after logging back in the webmarks show up, but no rs.on ready
or rs.on connected
. The error is still there.
After that I tried clearing all my storage and logging in. Which works. Then I tried deleting all entries which also works but throws Cannot delete non-existing node /
.
Seems to me that the error only occurs for freshly connected "empty" accounts.
Ooh, could it be that you mixed up steps 1 and 2? That is, it fails when you add bookmarks, and then connect an empty account?
(In that case it is supposed to sync the bookmarks that were created beforehand to the newly connected account.)
Ooh, could it be that you mixed up steps 1 and 2? That is, it fails when you add bookmarks, and then connect an empty account?
No. I am pretty sure I connected before adding some new bookmarks.
I remembered this error from before, and it turns out we fixed that long ago. It's only a log in the console now, but doesn't impact sync anymore:
https://github.com/remotestorage/remotestorage.js/issues/993 https://github.com/remotestorage/remotestorage.js/pull/1031
Btw, what is the source that is linked for that weird 404 in your console?
Actually, if you want, we can jump on a video call for debugging this. Maybe that's more efficient, as I cannot reproduce it on my machine. (I also deleted all bookmarks earlier when I tested this.)
I am unable to reproduce both errors for a second time for some reason :/ Maybe it's possible to reproduce this with a fresh google account. I''ll check with removing the files and acceess for the app.
No luck with that neither. Maybe with a fresh account?
We can do a video call but I am not sure it makes much sense when I am unable to reproduce the issue. Don't know. Maybe I had an ancient version cached locally?
Maybe I had an ancient version cached locally?
Maybe. I switched from AppCache to ServiceWorker at some point after that fix.
As we both can't reproduce it at this point, I'll close this issue for now. Thanks anyway for opening it! And feel free to re-open anytime, of course.
Failed to load resource: the server responded with a status of 404 ()
for archive