starred/floccus
1
0
Fork 0
mirror of https://github.com/floccusaddon/floccus.git synced 2026-04-25 22:26:06 +03:00
Code Issues 167 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #138] Chrome 68: Network error synchronizing #128

New issue
Closed
opened 2026-02-25 22:36:14 +03:00 by kerem · 16 comments
kerem commented 2026-02-25 22:36:14 +03:00
Owner
Copy link

Originally created by @dkaparis on GitHub (Jul 31, 2018).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/138

Software versions

  • Browser: Chromium 68.0.3440.75 (Official Build)
  • Nextcloud: 13.0.4 (Snap)
  • Nextcloud Bookmarks app: 0.11.0
  • Floccus: 2.2.8, 3.0.0-beta5

Steps to reproduce

  1. Enter nc URL and credentials as prompted to create a new account
  2. Click "Sync Now"

Expected outcome

Bookmarks to be synchronized successfully

Actual outcome

Error message: Network error: Check your network connection and your account details

Checking the network requests in the development console, I see a long series of requests to https://<URL_REDACTED>/index.php/apps/bookmarks/public/rest/v2/bookmark?page=-1 with 302 result and finally a failure: net::ERR_TOO_MANY_REDIRECTS

Here is a relevant part of the console output:

Nextcloud.js:411 GET https://<URL_REDACTED>/index.php/apps/bookmarks/public/rest/v2/bookmark?page=-1 0 ()
Account.js:168 Error: Network error: Check your network connection and your account details
    at NextcloudAdapter._callee14$ (Nextcloud.js:421)
    at tryCatch (polyfill.js:6900)
    at Generator.invoke [as _invoke] (polyfill.js:7138)
    at Generator.prototype.(anonymous function) [as throw] (chrome-extension://djejpebekaoommcjfeaiipdikmdjkblg/dist/js/polyfill.js:6952:21)
    at step (background-script.js:25144)
    at background-script.js:25144
Account.js:170 Syncing failed with Network error: Check your network connection and your account details

If I clear browser cookies, the sync succeeds once and on the next and subsequent tries the same error occurs.

Originally created by @dkaparis on GitHub (Jul 31, 2018). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/138 <!-- Hello there! Thank you for providing feedback! Please answer the below questions to allow for as smooth a process of tackling the issue as possible :) (Note: Everything surrounded by arrows, like this text for example, will not be visible.) --> ### Software versions <!-- Please provide the versions of the following software products in your set up --> * Browser: Chromium 68.0.3440.75 (Official Build) * Nextcloud: 13.0.4 (Snap) * Nextcloud Bookmarks app: 0.11.0 * Floccus: 2.2.8, 3.0.0-beta5 ### Steps to reproduce <!-- What did you do? Be as specific as possible --> 1. Enter nc URL and credentials as prompted to create a new account 2. Click "Sync Now" ### Expected outcome <!-- What did you think was going to happen or what do you think should have happened? --> Bookmarks to be synchronized successfully ### Actual outcome <!-- What actually happened after you did the above steps? --> Error message: Network error: Check your network connection and your account details Checking the network requests in the development console, I see a long series of requests to https://<URL_REDACTED>/index.php/apps/bookmarks/public/rest/v2/bookmark?page=-1 with 302 result and finally a failure: net::ERR_TOO_MANY_REDIRECTS Here is a relevant part of the console output: ``` Nextcloud.js:411 GET https://<URL_REDACTED>/index.php/apps/bookmarks/public/rest/v2/bookmark?page=-1 0 () Account.js:168 Error: Network error: Check your network connection and your account details at NextcloudAdapter._callee14$ (Nextcloud.js:421) at tryCatch (polyfill.js:6900) at Generator.invoke [as _invoke] (polyfill.js:7138) at Generator.prototype.(anonymous function) [as throw] (chrome-extension://djejpebekaoommcjfeaiipdikmdjkblg/dist/js/polyfill.js:6952:21) at step (background-script.js:25144) at background-script.js:25144 Account.js:170 Syncing failed with Network error: Check your network connection and your account details ``` If I clear browser cookies, the sync succeeds once and on the next and subsequent tries the same error occurs. <!-- Thanks! Now, hit Submit and wait for a reply :) -->
kerem closed this issue 2026-02-25 22:36:14 +03:00
kerem commented 2026-02-25 22:36:14 +03:00
Author
Owner
Copy link

@florealcab commented on GitHub (Jul 31, 2018):

This problem occurs since chrome 68, for me too (for all I think). There is something broken with this new version.

Problem also present for passman (which also interacts with nextcloud...)

<!-- gh-comment-id:409322263 --> @florealcab commented on GitHub (Jul 31, 2018): This problem occurs since chrome 68, for me too (for all I think). There is something broken with this new version. Problem also present for passman (which also interacts with nextcloud...)
kerem commented 2026-02-25 22:36:14 +03:00
Author
Owner
Copy link

@marcelklehr commented on GitHub (Jul 31, 2018):

mhh, any coherence among nextcloud versions? @florealcab Which one do you have in use?

<!-- gh-comment-id:409385166 --> @marcelklehr commented on GitHub (Jul 31, 2018): mhh, any coherence among nextcloud versions? @florealcab Which one do you have in use?
kerem commented 2026-02-25 22:36:14 +03:00
Author
Owner
Copy link

@Ra72xx commented on GitHub (Aug 2, 2018):

I have the same problem. Chromium 68.0.3440.75 and Nexcloud 13.0.5, openSUSE packages for both.

<!-- gh-comment-id:409875095 --> @Ra72xx commented on GitHub (Aug 2, 2018): I have the same problem. Chromium 68.0.3440.75 and Nexcloud 13.0.5, openSUSE packages for both.
kerem commented 2026-02-25 22:36:14 +03:00
Author
Owner
Copy link

@jlbprof commented on GitHub (Aug 2, 2018):

My Nextcloud has a self-signed certificate and I get that from time to
time. When that happens I just login to my Nextcloud Files section on
that browser and then I can sync. I think Firefox allows you to remember
that certificate but Chrome/Chromium does not, so you have to redo the cert
periodically.

On Thu, Aug 2, 2018 at 5:02 AM Larx notifications@github.com wrote:

I have the same problem. Chromium 68.0.3440.75 and Nexcloud 13.0.5,
openSUSE packages for both.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/marcelklehr/floccus/issues/138#issuecomment-409875095,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJS39QIbpWdaWMpVfNsR0aOGPu3fP5lQks5uMs4wgaJpZM4Vn23Y
.

<!-- gh-comment-id:409905240 --> @jlbprof commented on GitHub (Aug 2, 2018): My Nextcloud has a self-signed certificate and I get that from time to time. When that happens I just login to my Nextcloud Files section on that browser and then I can sync. I think Firefox allows you to remember that certificate but Chrome/Chromium does not, so you have to redo the cert periodically. On Thu, Aug 2, 2018 at 5:02 AM Larx <notifications@github.com> wrote: > I have the same problem. Chromium 68.0.3440.75 and Nexcloud 13.0.5, > openSUSE packages for both. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/marcelklehr/floccus/issues/138#issuecomment-409875095>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AJS39QIbpWdaWMpVfNsR0aOGPu3fP5lQks5uMs4wgaJpZM4Vn23Y> > . >
kerem commented 2026-02-25 22:36:14 +03:00
Author
Owner
Copy link

@Ra72xx commented on GitHub (Aug 2, 2018):

My certificate is a regular CertBot one, so it should be valid.

<!-- gh-comment-id:409922616 --> @Ra72xx commented on GitHub (Aug 2, 2018): My certificate is a regular CertBot one, so it should be valid.
kerem commented 2026-02-25 22:36:14 +03:00
Author
Owner
Copy link

@marcelklehr commented on GitHub (Aug 2, 2018):

for reference: The relevant passman issue is this one: https://github.com/nextcloud/passman-webextension/issues/269

<!-- gh-comment-id:409973481 --> @marcelklehr commented on GitHub (Aug 2, 2018): for reference: The relevant passman issue is this one: https://github.com/nextcloud/passman-webextension/issues/269
kerem commented 2026-02-25 22:36:14 +03:00
Author
Owner
Copy link

@marcelklehr commented on GitHub (Aug 3, 2018):

I can reproduce this with Version 68.0.3440.75 (Official Build)
However, it seems to be fixed with Version 68.0.3440.84 (Official Build) (64-bit)

<!-- gh-comment-id:410109239 --> @marcelklehr commented on GitHub (Aug 3, 2018): I can reproduce this with Version 68.0.3440.75 (Official Build) However, it seems to be fixed with Version 68.0.3440.84 (Official Build) (64-bit)
kerem commented 2026-02-25 22:36:14 +03:00
Author
Owner
Copy link

@darrellittle commented on GitHub (Aug 3, 2018):

I have the same issue on two separate PCs using Chrome Version 68.0.3440.84 (Official Build) (64-bit).
Firefox works fine on both PCs

<!-- gh-comment-id:410134754 --> @darrellittle commented on GitHub (Aug 3, 2018): I have the same issue on two separate PCs using Chrome Version 68.0.3440.84 (Official Build) (64-bit). Firefox works fine on both PCs
kerem commented 2026-02-25 22:36:14 +03:00
Author
Owner
Copy link

@marcelklehr commented on GitHub (Aug 3, 2018):

Mh, weird.

I've found the following issue which looks like it describes what we're experiencing. https://bugs.chromium.org/p/chromium/issues/detail?id=784528

Let's see, what'll happen.

<!-- gh-comment-id:410265695 --> @marcelklehr commented on GitHub (Aug 3, 2018): Mh, weird. I've found the following issue which looks like it describes what we're experiencing. https://bugs.chromium.org/p/chromium/issues/detail?id=784528 Let's see, what'll happen.
kerem commented 2026-02-25 22:36:14 +03:00
Author
Owner
Copy link

@jlbprof commented on GitHub (Aug 6, 2018):

I am getting the problem using beta6 and either a Nextcloud account or
Webdav, for a few days. I think Nextcloud did something in a recent
update as I recently updated.

Latest Chrome (68.0.3440.84) on Mac
Also latest on Windows.

Nextcloud: 13.0.5 stable
It is on CentOS 7 updated this weekend.

I am gonna try a cPanel Account WebDAV account later today, will let you
know how that goes.

Oh I see the Chrome bug you just referenced that makes sense. I will still
try a cPanel WebDAV later.

Julian

On Fri, Aug 3, 2018 at 9:22 AM Marcel Klehr notifications@github.com
wrote:

Mh, weird.

I've found the following issue which looks like it describes what we're
experiencing. https://bugs.chromium.org/p/chromium/issues/detail?id=784528

Let's see, what'll happen.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/marcelklehr/floccus/issues/138#issuecomment-410265695,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJS39fEP7h5WIdT2h7uu_iKq3BDV9HY8ks5uNFyUgaJpZM4Vn23Y
.

<!-- gh-comment-id:410686549 --> @jlbprof commented on GitHub (Aug 6, 2018): I am getting the problem using beta6 and either a Nextcloud account or Webdav, for a few days. I think Nextcloud did something in a recent update as I recently updated. Latest Chrome (68.0.3440.84) on Mac Also latest on Windows. Nextcloud: 13.0.5 stable It is on CentOS 7 updated this weekend. I am gonna try a cPanel Account WebDAV account later today, will let you know how that goes. Oh I see the Chrome bug you just referenced that makes sense. I will still try a cPanel WebDAV later. Julian On Fri, Aug 3, 2018 at 9:22 AM Marcel Klehr <notifications@github.com> wrote: > Mh, weird. > > I've found the following issue which looks like it describes what we're > experiencing. https://bugs.chromium.org/p/chromium/issues/detail?id=784528 > > Let's see, what'll happen. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/marcelklehr/floccus/issues/138#issuecomment-410265695>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AJS39fEP7h5WIdT2h7uu_iKq3BDV9HY8ks5uNFyUgaJpZM4Vn23Y> > . >
kerem commented 2026-02-25 22:36:14 +03:00
Author
Owner
Copy link

@florealcab commented on GitHub (Aug 6, 2018):

The problem does not comes from nextcloud, but from a change in Chrome.

So, we need to change the nextcloud extension (or nextcloud server?) to adapt to the new chrome behavior...

6 août 2018 14:09 "jlbprof" <notifications@github.com (mailto:notifications@github.com?to=%22jlbprof%22%20notifications@github.com)> a écrit:
I am getting the problem using beta6 and either a Nextcloud account or
Webdav, for a few days. I think Nextcloud did something in a recent
update as I recently updated.

Latest Chrome (68.0.3440.84) on Mac
Also latest on Windows.

Nextcloud: 13.0.5 stable
It is on CentOS 7 updated this weekend.

I am gonna try a cPanel Account WebDAV account later today, will let you
know how that goes.

Oh I see the Chrome bug you just referenced that makes sense. I will still
try a cPanel WebDAV later.

Julian

On Fri, Aug 3, 2018 at 9:22 AM Marcel Klehr <notifications@github.com (mailto:notifications@github.com)>
wrote:

Mh, weird.

I've found the following issue which looks like it describes what we're
experiencing. https://bugs.chromium.org/p/chromium/issues/detail?id=784528 (https://bugs.chromium.org/p/chromium/issues/detail?id=784528)

Let's see, what'll happen.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/marcelklehr/floccus/issues/138#issuecomment-410265695 (https://github.com/marcelklehr/floccus/issues/138#issuecomment-410265695)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJS39fEP7h5WIdT2h7uu_iKq3BDV9HY8ks5uNFyUgaJpZM4Vn23Y (https://github.com/notifications/unsubscribe-auth/AJS39fEP7h5WIdT2h7uu_iKq3BDV9HY8ks5uNFyUgaJpZM4Vn23Y)>
.

—

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (https://github.com/marcelklehr/floccus/issues/138#issuecomment-410686549), or mute the thread (https://github.com/notifications/unsubscribe-auth/AQLd4r--IuqVpx72lCBjKkXSPkvx1T5hks5uODH9gaJpZM4Vn23Y).

<!-- gh-comment-id:410689525 --> @florealcab commented on GitHub (Aug 6, 2018): The problem does not comes from nextcloud, but from a change in Chrome. So, we need to change the nextcloud extension (or nextcloud server?) to adapt to the new chrome behavior... 6 août 2018 14:09 "jlbprof" <notifications@github.com (mailto:notifications@github.com?to=%22jlbprof%22%20<notifications@github.com>)> a écrit: I am getting the problem using beta6 and either a Nextcloud account or Webdav, for a few days. I think Nextcloud did something in a recent update as I recently updated. Latest Chrome (68.0.3440.84) on Mac Also latest on Windows. Nextcloud: 13.0.5 stable It is on CentOS 7 updated this weekend. I am gonna try a cPanel Account WebDAV account later today, will let you know how that goes. Oh I see the Chrome bug you just referenced that makes sense. I will still try a cPanel WebDAV later. Julian On Fri, Aug 3, 2018 at 9:22 AM Marcel Klehr <notifications@github.com (mailto:notifications@github.com)> wrote: > Mh, weird. > > I've found the following issue which looks like it describes what we're > experiencing. https://bugs.chromium.org/p/chromium/issues/detail?id=784528 (https://bugs.chromium.org/p/chromium/issues/detail?id=784528) > > Let's see, what'll happen. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/marcelklehr/floccus/issues/138#issuecomment-410265695 (https://github.com/marcelklehr/floccus/issues/138#issuecomment-410265695)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AJS39fEP7h5WIdT2h7uu_iKq3BDV9HY8ks5uNFyUgaJpZM4Vn23Y (https://github.com/notifications/unsubscribe-auth/AJS39fEP7h5WIdT2h7uu_iKq3BDV9HY8ks5uNFyUgaJpZM4Vn23Y)> > . > — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub (https://github.com/marcelklehr/floccus/issues/138#issuecomment-410686549), or mute the thread (https://github.com/notifications/unsubscribe-auth/AQLd4r--IuqVpx72lCBjKkXSPkvx1T5hks5uODH9gaJpZM4Vn23Y).
kerem commented 2026-02-25 22:36:14 +03:00
Author
Owner
Copy link

@jlbprof commented on GitHub (Aug 6, 2018):

Is it possible there is a "new permission" that needs to be set in the
extension?

On Mon, Aug 6, 2018 at 7:22 AM Floréal Cabanettes notifications@github.com
wrote:

The problem does not comes from nextcloud, but from a change in Chrome.

So, we need to change the nextcloud extension (or nextcloud server?) to
adapt to the new chrome behavior...

6 août 2018 14:09 "jlbprof" <notifications@github.com (mailto:
notifications@github.com?to=%22jlbprof%22%20notifications@github.com)>
a écrit:
I am getting the problem using beta6 and either a Nextcloud account or
Webdav, for a few days. I think Nextcloud did something in a recent
update as I recently updated.

Latest Chrome (68.0.3440.84) on Mac
Also latest on Windows.

Nextcloud: 13.0.5 stable
It is on CentOS 7 updated this weekend.

I am gonna try a cPanel Account WebDAV account later today, will let you
know how that goes.

Oh I see the Chrome bug you just referenced that makes sense. I will still
try a cPanel WebDAV later.

Julian

On Fri, Aug 3, 2018 at 9:22 AM Marcel Klehr <notifications@github.com
(mailto:notifications@github.com)>
wrote:

Mh, weird.

I've found the following issue which looks like it describes what we're
experiencing.
https://bugs.chromium.org/p/chromium/issues/detail?id=784528 (
https://bugs.chromium.org/p/chromium/issues/detail?id=784528)

Let's see, what'll happen.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<
https://github.com/marcelklehr/floccus/issues/138#issuecomment-410265695 (
https://github.com/marcelklehr/floccus/issues/138#issuecomment-410265695
)>,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AJS39fEP7h5WIdT2h7uu_iKq3BDV9HY8ks5uNFyUgaJpZM4Vn23Y
(
https://github.com/notifications/unsubscribe-auth/AJS39fEP7h5WIdT2h7uu_iKq3BDV9HY8ks5uNFyUgaJpZM4Vn23Y
)>
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (
https://github.com/marcelklehr/floccus/issues/138#issuecomment-410686549),
or mute the thread (
https://github.com/notifications/unsubscribe-auth/AQLd4r--IuqVpx72lCBjKkXSPkvx1T5hks5uODH9gaJpZM4Vn23Y
).

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/marcelklehr/floccus/issues/138#issuecomment-410689525,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJS39aAwAMFfsMnuu6nhxqSe-4TZcQhHks5uODTrgaJpZM4Vn23Y
.

<!-- gh-comment-id:410718989 --> @jlbprof commented on GitHub (Aug 6, 2018): Is it possible there is a "new permission" that needs to be set in the extension? On Mon, Aug 6, 2018 at 7:22 AM Floréal Cabanettes <notifications@github.com> wrote: > The problem does not comes from nextcloud, but from a change in Chrome. > > So, we need to change the nextcloud extension (or nextcloud server?) to > adapt to the new chrome behavior... > > 6 août 2018 14:09 "jlbprof" <notifications@github.com (mailto: > notifications@github.com?to=%22jlbprof%22%20<notifications@github.com>)> > a écrit: > I am getting the problem using beta6 and either a Nextcloud account or > Webdav, for a few days. I think Nextcloud did something in a recent > update as I recently updated. > > Latest Chrome (68.0.3440.84) on Mac > Also latest on Windows. > > Nextcloud: 13.0.5 stable > It is on CentOS 7 updated this weekend. > > I am gonna try a cPanel Account WebDAV account later today, will let you > know how that goes. > > Oh I see the Chrome bug you just referenced that makes sense. I will still > try a cPanel WebDAV later. > > Julian > > On Fri, Aug 3, 2018 at 9:22 AM Marcel Klehr <notifications@github.com > (mailto:notifications@github.com)> > wrote: > > > Mh, weird. > > > > I've found the following issue which looks like it describes what we're > > experiencing. > https://bugs.chromium.org/p/chromium/issues/detail?id=784528 ( > https://bugs.chromium.org/p/chromium/issues/detail?id=784528) > > > > Let's see, what'll happen. > > > > — > > You are receiving this because you commented. > > Reply to this email directly, view it on GitHub > > < > https://github.com/marcelklehr/floccus/issues/138#issuecomment-410265695 ( > https://github.com/marcelklehr/floccus/issues/138#issuecomment-410265695 > )>, > > or mute the thread > > < > https://github.com/notifications/unsubscribe-auth/AJS39fEP7h5WIdT2h7uu_iKq3BDV9HY8ks5uNFyUgaJpZM4Vn23Y > ( > https://github.com/notifications/unsubscribe-auth/AJS39fEP7h5WIdT2h7uu_iKq3BDV9HY8ks5uNFyUgaJpZM4Vn23Y > )> > > . > > > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub ( > https://github.com/marcelklehr/floccus/issues/138#issuecomment-410686549), > or mute the thread ( > https://github.com/notifications/unsubscribe-auth/AQLd4r--IuqVpx72lCBjKkXSPkvx1T5hks5uODH9gaJpZM4Vn23Y > ). > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/marcelklehr/floccus/issues/138#issuecomment-410689525>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AJS39aAwAMFfsMnuu6nhxqSe-4TZcQhHks5uODTrgaJpZM4Vn23Y> > . >
kerem commented 2026-02-25 22:36:14 +03:00
Author
Owner
Copy link

@marcelklehr commented on GitHub (Aug 8, 2018):

@jlbprof I doubt it. At least the chrome changelog doesn't mention anything.

@florealcab I've tried adjusting the floccus code, but haven't had any luck so far, which makes me think it's a bug in chrome.

<!-- gh-comment-id:411513921 --> @marcelklehr commented on GitHub (Aug 8, 2018): @jlbprof I doubt it. At least the chrome changelog doesn't mention anything. @florealcab I've tried adjusting the floccus code, but haven't had any luck so far, which makes me think it's a bug in chrome.
kerem commented 2026-02-25 22:36:14 +03:00
Author
Owner
Copy link

@marcelklehr commented on GitHub (Aug 8, 2018):

I've just released v2.2.9 which should fix this. (It was a spec change of the fetch API, introduced in Chrome 68)

<!-- gh-comment-id:411536555 --> @marcelklehr commented on GitHub (Aug 8, 2018): I've just released v2.2.9 which should fix this. (It was a spec change of the fetch API, introduced in Chrome 68)
kerem commented 2026-02-25 22:36:14 +03:00
Author
Owner
Copy link

@jlbprof commented on GitHub (Aug 8, 2018):

That worked for me, let me know when the beta is updated. :)

On Wed, Aug 8, 2018 at 3:12 PM Marcel Klehr notifications@github.com
wrote:

I've just released v2.2.9 which should fix this. (It was a spec change of
the fetch API, introduced in Chrome 68)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/marcelklehr/floccus/issues/138#issuecomment-411536555,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJS39SNNRFQstcuYCe6Tb3TPYv1beO6Rks5uO0YZgaJpZM4Vn23Y
.

<!-- gh-comment-id:411547845 --> @jlbprof commented on GitHub (Aug 8, 2018): That worked for me, let me know when the beta is updated. :) On Wed, Aug 8, 2018 at 3:12 PM Marcel Klehr <notifications@github.com> wrote: > I've just released v2.2.9 which should fix this. (It was a spec change of > the fetch API, introduced in Chrome 68) > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/marcelklehr/floccus/issues/138#issuecomment-411536555>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AJS39SNNRFQstcuYCe6Tb3TPYv1beO6Rks5uO0YZgaJpZM4Vn23Y> > . >
kerem commented 2026-02-25 22:36:14 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Mar 21, 2023):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

<!-- gh-comment-id:1477740013 --> @github-actions[bot] commented on GitHub (Mar 21, 2023): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
develop
dependabot/npm_and_yarn/fast-xml-parser-5.7.0
dependabot/npm_and_yarn/xmldom/xmldom-0.8.13
dependabot/npm_and_yarn/protocol-buffers-schema-3.6.1
master
fix/xml-entity-limit
all-contributors/add-aaryanvangari
fix/subscanner-residuals
test/subscanner-residuals
test/problematic-seeds
perf/improve-build-time
perf/native-startup
fix/continuation-null-cheks
dropbox
fix/clear-indexeddb-after-sync
dependabot/npm_and_yarn/vuetify-3.11.4
fix/slim-down-continuation
test/background-worker
refactor/fail-build-if-native-uses-browser-api
feat/improve-failsafe-wording
dependabot/npm_and_yarn/multi-0520f5abeb
feat/release-build
fix/more-mapping-errors
dependabot/npm_and_yarn/intl-messageformat-10.7.18
enh/split-sync-interval-and-auto-sync
enh/gdrive-timeout
feat/safari
feat/capabilities
feat/xxhash3
feat/murmur3
fix/gdrive-error-handling
fix/correctness-fixes
fix/linkwarden
feat/orion
fix/nocache-tests
feat/tab-groups
fix/git-never-force-push
fix/xbel-parse-errors
fix/git-push-errors
fix/chrome-main-folder-ids
dependabot/npm_and_yarn/multi-a9f852c250
chore/use-local-linkwarden-container-in-ci
all-contributors/add-balthanon
dependabot/npm_and_yarn/multi-7c5da94753
fix/revert-indexeddb-logger
fix/acknowlegde-abuse
dependabot/npm_and_yarn/eslint-import-resolver-webpack-0.13.10
fix/rip-out-continuations
fix/webdav-filesize-depth-header
fix/changes-while-syncing
fix/addition-failsafe-minimum
feat/indexeddb-logs
feat/addition-failsafe
fix/webdav-check-filesize
fix/orion
fix/bounded-exponential-backoff
fix/dont-repeat-on-sync-fail
fix-tests
fix/speedup-tab-update-cb
all-contributors/add-andybalaam
all-contributors/add-macrogreg
fix/parse-tag-value
fix/cleanup-deps
refactor/partial-set-data-with-lock
fix/nc-bookmarks-update
fix/move-stabiltiy-same-titled-folders
fix/ios-share-extension
fix/update-selenium
fix/chrome-net-errors
enh/nc-bm-js
sentry
fix/unidirectional-scanner-shoudl-use-mappings
enh/interrupts
dependabot/npm_and_yarn/vue-loader-17.4.2
ci/build-ios
enh/manifest-v3
release/4.19.0
fix/codeql
fix/google-drive-ios
all-contributors/add-dmotte
fix/unidirectional-sync
fix/interrupts
all-contributors/add-pinpontitit
all-contributors/add-dsiminiuk
test/old-apis
test/interrupts-on-nextcloud-bookmarks
feature/no-hashing-in-diff
feature/improve-diff-performance
capacitor
enh/rename-nextcloud-folders
fix/complex-hierarchy-reversal-2
tests/coverage
feature/google-drive
dependabot/npm_and_yarn/eslint-plugin-vue-7.6.0
fix/crypto
dependabot/npm_and_yarn/sass-1.32.7
dependabot/npm_and_yarn/css-loader-5.0.2
dependabot/npm_and_yarn/webpack-cli-4.5.0
fix/performance-hash-caching
dependabot/npm_and_yarn/eslint-plugin-standard-5.0.0
dependabot/npm_and_yarn/sass-loader-10.1.1
dependabot/npm_and_yarn/eslint-import-resolver-webpack-0.13.0
dependabot/npm_and_yarn/webpack-merge-5.7.3
dependabot/npm_and_yarn/p-queue-6.6.2
dependabot/npm_and_yarn/throttle-debounce-3.0.1
fix/lww-move-test
fix/overwrite-strategy
fix/root-folder-sync
enh/local-hash-cash
test/ci
ui/vue
cookie-hack
fix/travis
rollup
refactor/ui
webdav
refactor/modularize
v5.9.1
v5.9.0
v5.8.6
v5.8.5
v5.8.4
v5.8.3
v5.8.2
v5.8.1
v5.8.0
v5.7.0
v5.6.0
v5.5.6
v5.5.5
v5.5.4
v5.5.3
v5.5.2
v5.5.1
v5.5.0
v5.4.5
v5.4.4
v5.4.3
v5.4.2
v5.4.2-alpha.1
v5.4.1
v5.4.0
v5.3.4
v5.3.3
v5.3.1
v5.3.0
v5.3.0-beta.1
v5.2.7
v5.2.6
v5.2.5
v5.2.4
v5.2.3
v5.2.2
v5.2.1
v5.2.0
v5.2.0-beta.3
v5.2.0-beta.2
v5.2.0-beta.1
v5.1.7
v5.1.6
v5.1.5
v5.1.4
v5.1.3
5.1.3-beta.1
v5.1.2
v5.1.1
v5.1.0
v5.0.12
v5.0.12-beta.1
v5.0.11
v5.0.10
v5.0.9
v5.0.8
v5.0.7
v5.0.6
v5.0.5
v5.0.4
v5.0.3
v5.0.2
v5.0.1
v5.0.0
v4.19.1
v4.19.0
v4.18.1
v4.18.0
v4.17.1
v4.17.0
v4.16.0
v4.15.0
v4.14.0
v4.13.1
v4.13.0
v4.12.0
v4.11.0
v4.11.0-alpha.0
v4.10.1
v4.10.0
v4.9.0
v4.8.7
v4.8.6
v4.8.4
v4.8.3
v4.8.2
v4.8.1
v4.8.0
v4.7.0
v4.6.4
v4.6.3
v4.6.2
v4.6.1
v4.6.0
v4.5.0
v4.4.10
v4.4.9
v4.4.8
v4.4.7
v4.4.6
v4.4.5
v4.4.4
v4.4.3
v4.4.2
v4.4.1
v4.4.0
v4.4.0-rc1
v4.3.0
v4.2.6
v4.2.5
v4.2.4
v4.2.3
v4.2.2
v4.2.1
v4.2.0
v4.2.0-beta.4
v4.2.0-beta.3
v4.2.0-beta.2
v4.2.0-beta.1
v4.1.0
v4.0.4
v4.0.3
v4.0.2
v4.0.1
v4.0.0
v4
v4.0.0-alpha.3
v4.0.0-alpha.2
v4.0.0-alpha.1
v3.5.3
v3.5.2
v3.5.1
v3.5.0
v3.4.2
v3.4.1
v3.4.0
v3.4.0-beta.3
v3.4.0-beta.2
v3.4.0-beta.1
v3.3.2
v3.3.1
v3.3.0
v3.3.0-beta.5
v3.3.0-beta.4
v3.3.0-beta.3
v3.3.0-beta.2
v3.3.0-beta.1
v3.2.16
v3.2.15
v3.2.14
v3.2.13
v3.2.12
v3.2.11
v3.2.10
v3.2.9
v3.2.8
v3.2.7
v3.2.6
v3.2.5
v3.2.4
v3.2.3
v3.2.2
v3.2.1
v3.2.0
v3.1.15
v3.1.14
v3.1.13
v3.1.12
v3.1.11
v3.1.10
v3.1.9
v3.1.8
v3.1.7
v3.1.6
v3.1.5
v3.1.4
v3.1.3
v3.1.2
v3.1.1
v3.1.0
v3.0.10
v3.0.9
v3.0.8
v3.0.7
v3.0.6
v3.0.5
v3.0.4
v3.0.3
v3.0.2
v3.0.1
v3.0.0
v3.0.0-beta.9
v3.0.0-beta.8
v3.0.0-beta.7
v2.2.9
v3.0.0-beta.6
v3.0.0-beta.5
v3.0.0-beta.4
v3.0.0-beta.3
v3.0.0-beta.2
v3.0.0-beta-1
v3.0.0-alpha-1
v2.2.8
v2.2.7
v2.2.6
v2.2.5
v2.2.4
v2.2.3
v2.2.2
v2.2.1
v2.2.0
v2.1.0
v2.0.6
v2.0.5
v2.0.4
v2.0.3
v2.0.2
v2.0.1
v2.0.0
v2.0.0-beta.2
v1.3.4
v2.0.0-beta.1
v1.3.3
v1.3.2
v1.3.1
v1.3.0
v1.3.0-beta.5
v1.3.0-beta.4
v1.3.0-beta.3
v1.3.0-beta.2
v1.3.0-beta1
v1.2.0
v1.1.2
v1.1.1
v1.1.0
v1.0.1
v1.0.0
Labels
Clear labels   
browser-specific

   
bug

   
correctness issues

   
enhancement

   
feature: Google Drive

   
feature: Linkwarden

   
feature: git

   
feature: nextcloud-bookmarks

   
feature: tabs

   
feature: webdav

   
help wanted

   
native-app

   
priority: high

   
priority: low

   
priority: medium

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
question

   
stale

   
upstream

   
waiting for more information

   
wontfix

   
🙁 Not following issue template
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/floccus#128
No description provided.