Sync issue: Firefox -> Other (Chrome, Android, iOS)

Bug ReportsApr 26, 2024

I'm using memex on multiple platforms and browsers. Sync seems to work pretty well between Chrome (Desktop), Android and iOS.

The only issue is Firefox (Desktop). It did some comprehensive testing...

Firefox receives updates from all other platforms (Android, iOS) and even Chrome.
But everything I add in Firefox is neither pushed to Chrome (running on the same Computer) nor to Android/iOS.

Now I have an inconsistent view/database between Firefox (my main browser) and the others.

I believe, it worked pretty good ~1month ago but stopped working with the latest updates. Hopefully, it can be fixed quickly.

Posted by [Deleted User] · Apr 26, 2024

🔧 Fixed 24

Oliver Sauter

Team•

May 3, 2024

We found the issue!
In the process of fixing it and likely you'll have it all working by today again still.

Oliver Sauter

Team•

Apr 26, 2024

Thanks for reporting!

After an (unwanted) upgrade we had to make for Memex to be compliant with the new Manifest V3 that Chrome mandates, we're experiencing sync issues.

The problem is that the entire sync infrastructure had to change and so we are hell bend to get those all fixed as soon as they come up.

A few questions:

What happens after you restart the firefox extension?
What browser version are you on?
What extension version on Firefox are you on?

Anonymous User
•
Apr 26, 2024
Hi Olivers,

thanks for the quick response. I also assumed that the root cause for the sync issues might be the manifest v3 changes.

1. restarting the extension does not change anything. The updates are not pushed to other devices/browsers.
2. Firefox 125.0.2
3. Firefox Memex Extension 3.19.0
- [Deleted User]
  •
  Apr 26, 2024
  Ups, that was me. Forgot to sign in :-)
- Oliver Sauter
  Team•
  Apr 29, 2024
  Ok thanks for the info, we'll look into it immediately!
  [Deleted User]
  •
  May 2, 2024
  I've just noticed that under my sync button on the dashboard, there is a number of pending uploads.
  I'm pretty sure that number wasn't there when I opened this issue. I remember that there was something like "last sync X minutes ago".
  Maybe this has changed with some update.
  However, this number is not decreasing in my Firefox. It only goes up once I add new content to Memex.
  Oliver Sauter
  Team•
  May 2, 2024
  No that number should have been always there.
  
  A few troubleshooting questions:
  - Are you logged in?
  - Does it basically always say "Syncing changes..."?
  - Which version of the extension are you on?
  
  Can you go to: about:debugging#/runtime/this-firefox
  then on "inspect" on memex
  then on "console"
  then make a screen recording scrolling through that console.
  then I can look into it today still!
  
  Thanks a lot.
  [Deleted User]
  •
  May 2, 2024
  Hi,
  
  1) Yes, I am logged in. I can see my internal user ID in the account tab and I can also see that my pro features are enabled.
  2) Yes. "Syncing changes... pending uploads 595". I'm really convinced that this wasn't there 3.19.0 that I used my former post.
  3) 3.19.8 (Firefox)
  
  Thanks for pointing me to the extension console. There are three errors (RED):
  
  1)
  
  downloadable font: failed to start download (font-family: "Satoshi" style:normal weight:400 stretch:100 src index:0): status=2152857618 source: moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/fonts/Satoshi/Satoshi-Regular.woff2
  
  This error occurs for different font weights (300, 400, 500) but it has obviously nothing to do with the sync error.
  
  2)
  Three succeeding error messages related to "personalCloud".
  
  Remote event emitter "personalCloud" failed to emit event "downloadStarted": Error message: "Promised response from onMessage listener went out of scope" background.js:2:743140
  Remote event emitter "personalCloud" failed to emit event "downloadStopped": Error message: "Promised response from onMessage listener went out of scope" background.js:2:743140
  Remote event emitter "personalCloud" failed to emit event "cloudStatsUpdated": Error message: "Promised response from onMessage listener went out of scope"background.js:2:743140
  
  3)
  I saw another issue but I could only see these one time. The other issues above can be easily reproduced, e.g. by opening the Dashboard.
  
  However, I once saw this issue.
  
  Error while executing action (retry scheduled):
  Object { id: 4075, type: "push-object", updates: (1) […] }
  Error: Data cannot be encoded in JSON: NaN
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      o moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      o moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      o moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      y moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      g moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      g moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      callFirebaseFunction moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      u moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      u moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      callFirebaseFunction moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      m moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      get moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      pushUpdates moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      o moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      promise callback*c moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      u moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      u moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      pushUpdates moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      processPersonalCloudAction moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      o moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      promise callback*c moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      u moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      u moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      processPersonalCloudAction moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      executeAction moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      executePendingActions moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      o moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      promise callback*c moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      o moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      promise callback*c moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      o moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      promise callback*c moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      o moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      promise callback*c moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      o moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      promise callback*c moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      u moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      u moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      executePendingActions moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      _scheduledRetry moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      u moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      u moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      _scheduledRetry moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      attemptOneOffJob moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      o moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      promise callback*c moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      u moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      u moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      attemptOneOffJob moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      handleAlarm moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      u moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      u moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      handleAlarm moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
  
  Anonymous User
  •
  May 2, 2024
  Regarding 3) Error: Data cannot be encoded in JSON: NaN
  
  The problem seems to be the "order"-key in the "push-object".
  
  {
  "type": "overwrite",
  "schemaVersion": "2024-03-05T00:00:00.000Z",
  "deviceId": "XXXXXXX",
  "collection": "templates",
  "object": {
  "id": 1712074433975,
  "title": "Markdown: Note Only",
  "code": "{{#HasNotes}}\n{{#Notes}}\n{{#NoteHighlight}}\n{{{NoteHighlight}}}\n{{/NoteHighlight}}\n{{#NoteText}}\n{{{NoteText}}}\n{{/NoteText}}\n{{/Notes}}\n{{/HasNotes}}",
  "order": null,
  "isFavourite": false,
  "outputFormat": "rich-text"
  }
  }
  
  Perhaps this error prevents the sync from continuing?
  
  Some time ago, I created my very first citation template. Maybe I entered some unexpected content which led to this error?
  I delted my custom template, but the error still persists.
  
  I've just tested with a clean new Firefox Profile. I logged in, and sync works as expected (cross devices). The only issue is that many items are missing, since my main Browser did not sync for a longer period of time. So it seems, that the error occured because my profile did something unexpected....
  Oliver Sauter
  Team•
  May 2, 2024
  Ah I see the problem already! We have just discovered that bug in the error reports and glad I have someone to talk to directly about this. We're not yet 100% sure where it comes from but highest priority to investigate.
  [Deleted User]
  •
  May 3, 2024
  Great! Looking forward to a solution.
  Tell me if I can do anything else.
  Oliver Sauter
  Team•
  May 3, 2024
  We added some more detailed error logs just now, can you upgrade the extension to 3.19.11 and just let it run then we'll get a bit more data to investigate.
  Anonymous User
  •
  May 3, 2024
  Perfect. I'm now on 3.19.11.
  
  You can find my updated logs below. Not sure, if it helps...
  
  ***
  
  My personal thougts (if you are interested):
  
  The first message about RPC function and the DEPRECATED messages are yellow (warning). All remaining log entries are red (error).
  
  The first three Remote event emitter "auth" seem to be new to me (?). But in the debugger, I can see, that they belong together. The functio pushUpdates calls a function callFirebaseFunction which in turn parses all key/value pairs of the push-object. This finally results intThe error Error while executing action (retry scheduled): Object.
  The push-object itself looks identitcal to the one before: the "order" is set to null in the push-object. Thus the following function throws the exception:
  
  function a(e) {
  if (null == e) return null;
  if (
  e instanceof Number &&
  (e = e.valueOf()),
  'number' == typeof e &&
  isFinite(e)
  ) return e;
  if (!0 === e || !1 === e) return e;
  if ('[object String]' === Object.prototype.toString.call(e)) return e;
  if (e instanceof Date) return e.toISOString();
  if (Array.isArray(e)) return e.map((e => a(e)));
  if ('function' == typeof e || 'object' == typeof e) return o(e, (e => a(e)));
  throw new Error('Data cannot be encoded in JSON: ' + e)
  }
  I don't know if this "analysis" helps you. I don't have any real experieces in this. However, here are the logs.
  
  ***
  
  RPC function with name trackBqEvent has already been registered background.js:2:743424
  Remote event emitter "personalCloud" failed to emit event "cloudStatsUpdated": Error message: "Could not establish connection. Receiving end does not exist." background.js:2:743424
      t moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      emit moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
  Remote event emitter "auth" failed to emit event "onLoadingUser": Error message: "Could not establish connection. Receiving end does not exist." 2 background.js:2:743424
      t moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      emit moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
  Remote event emitter "auth" failed to emit event "onAuthStateChanged": Error message: "Could not establish connection. Receiving end does not exist." background.js:2:743424
      t moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      emit moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
  Error while executing action (retry scheduled):
  Object { id: 4075, type: "push-object", updates: (1) […] }
  Error: Data cannot be encoded in JSON: NaN
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      o moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      o moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      o moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      y moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      g moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      g moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      callFirebaseFunction moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      u moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      u moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      callFirebaseFunction moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      m moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      get moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      pushUpdates moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      o moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
  background.js:2:743424
      t moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      executePendingActions moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
  Error: Data cannot be encoded in JSON: NaN
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      o moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      o moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      o moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      y moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      g moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      g moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      callFirebaseFunction moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      u moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      u moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      callFirebaseFunction moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      m moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      get moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      pushUpdates moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      o moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
  background.js:2:743424
      t moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      t moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
  Error while executing action (retry scheduled):
  Object { id: 4075, type: "push-object", updates: (1) […] }
  Error: Data cannot be encoded in JSON: NaN
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      o moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      o moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      o moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      y moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      g moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      g moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      callFirebaseFunction moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      u moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      u moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      callFirebaseFunction moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      m moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      get moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      pushUpdates moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      o moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
  background.js:2:743424
  Uncaught (in promise) Error: Data cannot be encoded in JSON: NaN
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      o moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      o moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      o moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      a moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      y moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      g moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      g moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      callFirebaseFunction moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      u moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      u moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      callFirebaseFunction moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      m moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      get moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      pushUpdates moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
      o moz-extension://105076ae-470c-4887-a3cf-4f7cd59c92b0/background.js:2
  background.js:2:1296050
  TypeError: e is undefined 4 background.js:2:460225
  DEPRECIATED this.annotationStorage.getAllAnnotationsByUrl...
  Object { url: "https://memex.featurebase.app/", limit: 1000, skip: 0 }
  background.js:2:743424
  TypeError: e is undefined 12 background.js:2:460225

bogdan.stefan@outlook.com

•

May 2, 2024

Just wanted to let you know that on Vivaldi (Chromium) v6.6.x I experienced this issue too. The extension seemingly ran OK before the recent Manifest V3 changes.

Had about 3000+ Pending changes showing up. My Console errors said that Firebase kept rejecting the uploaded changes because my "lease had expired.
(this all due to a fallout given previous issue I had with high count of Spaces not showing up, leading to hundreds of duplicates).

Unfortunately, I lost all of these when I reinstalled the Extension, and now it made me rollback to about a lost week of effort put into Spaces Management. Will report back any further findings once my Pages and Spaces get sync'ed back, and I am done with reviewing my Spaces.

Oliver Sauter
Team•
May 2, 2024
Argh :( Sorry that you lost some important work.

Generally speaking be aware that the extension is local first so all data is stored local by default and then uploaded. If you wipe the extension and things have not been uploaded they are indeed gone.

Oliver Sauter

Team•

May 3, 2024

@blue @bogste Update to version to 3.19.12 (Firefox now, Chrome in a few hours) and the fix is live.

[Deleted User]
•
May 3, 2024
Hi Oliver,

thank your for the update. Unfortunetly, it does not seem to solve my problem.
I mean, maybe I have to wait a bit longer since Memex needs to push 600+ pendings updates (the number does not go down after a couple minutes), but according to my error log, nothing has changed.

I still see those two errors:

1)

Error while executing action (retry scheduled): background.js:formatted:47927:39
Object { id: 4075, type: "push-object", updates: (1) […] }
Error: Data cannot be encoded in JSON: NaN

2)

TypeError: e is undefined background.js:formatted:29257:17
- Oliver Sauter
  Team•
  May 3, 2024
  I just double checked again and for me the sync is continuing, and I also don't see any errors in the logs from version 3.19.12 yet, assuming you may have not updated yet?
  
  Are you sure you are on the right version?
  [Deleted User]
  •
  May 3, 2024
  Yes, I updated to 3.19.12 and restarted Firefox afterwards.
  Oliver Sauter
  Team•
  May 3, 2024
  For that error message you're seeing, can you unfold the "updates" section here?
  Object { id: 4075, type: "push-object", updates: (1) […] }
  
  I need to see the object it tries to push with the data inside bc it is a data issue related to the update, you can also email it to me if you feel its sensitive information.
  oli@memex.garden
  [Deleted User]
  •
  May 3, 2024
  Sure. I just stripped out my deviceId.
  The issue is still in the push-object -> order . I set a breakpoint to the Throw exception point in the source code (see my other post above) and could verify that this causes the exception.
  
  {
  "id": 4075,
  "type": "push-object",
  "updates": [
  {
  "type": "overwrite",
  "schemaVersion": "2024-03-05T00:00:00.000Z",
  "deviceId": "XXXXXXXXX",
  "collection": "templates",
  "object": {
  "id": 1712074433975,
  "title": "Markdown: Note Only",
  "code": "{{#HasNotes}}\n{{#Notes}}\n{{#NoteHighlight}}\n{{{NoteHighlight}}}\n{{/NoteHighlight}}\n{{#NoteText}}\n{{{NoteText}}}\n{{/NoteText}}\n{{/Notes}}\n{{/HasNotes}}",
  "order": null,
  "isFavourite": false,
  "outputFormat": "rich-text"
  }
  }
  ]
  }
  
  I'm note sure, where to find the source code on github, but if it is this commiit, there was only a check for releaseDate but not for order.
  Oliver Sauter
  Team•
  May 3, 2024
  All right, so to be very honest we have tried a lot of things and for the life of us we could not figure out how that ended up in the NaN state. It was a different bug from the NaN issue the other person here had.
  We even reproduced the sync entry for us like you have it with all the same data and it would sync fine.
  
  So we are unsure about the root cause and would appreciate feedback if it appears again so we get more data about that.
  
  However for now what you can do is remove that sync item to be able to at least continue syncing.
  For that you need to go to:
  1. About:addons
  2. Settings icon
  3. Debug Extensions
  4. "Inspect" on Memex
  5. Console
  6. Type in:
  
  await storageMan.backend.operation('deleteObject', 'personalCloudAction', { id: 4075 })
  await storageMan.backend.operation('deleteObject', 'templates', { id: 1712074433975 })
  
  This will delete the template and the sync entry and from then on it should technically work again.
  Make sure to just create a new template again with your old template data to to trigger a new sync and let all of the stacked up items process.
  
  Sorry about the troubles and thanks for helping with the investigation so much.
  [Deleted User]
  •
  May 3, 2024
  First, I want to say thank you for all the time that you and your team spent on this (and ofc on Memex in general)! This is simply awesome.
  
  Second, your work-around fixed my issue. The number of "pending updates" goes slowly down... finally.
  
  Also, I learned a lot about Memex's internals, which is very interesting.
  
  Thank you!
bogdan.stefan@outlook.com
•
May 4, 2024
Confirming that I am seeing fair improvements in Desktop-to-Desktop synchronization starting with v3.19.13+ on Vivaldi Browser (Chromium).

Sync issue: Firefox -> Other (Chrome, Android, iOS)

Comments24