windowId is undefined - Spaces is losing all data about spaces HOT 9 CLOSED

In the support section of the webstore version there is also a comment by another user who lost their work on 10th October – which I think is when I started losing my data as well.

Note that ALL saved spaces were erased, I only keep one or two open.

from spaces.

I know this doesn't help you now and is sub optimal but:
Since spaces is not yet super stable I back mine up outside it pretty regularly.
(And who knows if it will ever be, the browser companies have broke extension compatibility many times before.)

The workflow looks like this:

1. Change Chrome's download directory to a new one called 'Tabs_Backup_DATE'
2. Click through and export each space.
3. Change the download directory back.

from spaces.

from spaces.

@themightychris "Backup all spaces" exports a truncated JSON file that does not parse correctly.

Exporting each space individually with the top-right download option does work though at least, but with a lot of spaces can be difficult to do repetitively.

Have been using Spaces again more recently now and haven't had a failure for some time now but still scared to rely on it as much as I used to.

from spaces.

@Martin-Pitt The "Backup all spaces" bug should be fixed now (it no longer truncates the JSON file). Would you be able to confirm this for me?

from spaces.

@deanoemcke, yep the backup all spaces bug is fixed! Well, at least before this new issue:

A new bug is happening on Canary however, newly spaces saved across sessions seem to be now showing up as 'Unnamed window' that I can't select in the manager window. I've got three of these. I can see that the "sessionId" increments to the last numbers from the URL in the manager (57, 58, and 59).

I suspect it is because Canary has a new feature related to grouping tabs.

I've not used the grouping tabs feature except for a quick trial run. But I suspect that changes under the hood mean that Spaces might not be acting a bit funny. I'm making sure to backup things, and that functionality is working all right now at least.

from spaces.

I'm getting the following stack trace:

Looks like I have rogue tab entries stored now that are causing errors:

from spaces.

The latest version 1.1.2 has filtered out the bad undefined/spaces, preventing errors from stacking up and it breaking.

Created a new space, and restarted chrome, seems to have remembered it this time.

from spaces.

@Martin-Pitt Is this issue resolved then?

from spaces.