New sync system

Eik

Seems that it has something to do with grouping and agenda mode:

Also google calender selection is not persisted:

andrew

Jay When I try to open beta.legendapp.com, it gets stuck on Loading… and gives me the following toast. Never gets past it.

I logged out of Windows desktop and the same thing is happening… can’t load any documents. I know it is using Stable (confirmed by looking at inspector and it is loading app.legendapp.com).

Yet in a Chrome tab, I am able to load app.legendapp.com and all documents loaded (except one local one that was created when I imported my original document locally).

andrew

I am getting these errors when it hangs on Loading in Windows desktop app:

Jorge

So testing the beta today… I noticed than in my board of bills to pay, in which I have a pane that filters for overdue items -is:complete #pay date:overdue and shows them as a list type, there was an item missing in the beta that what I was seeing in the stable version.
I found that in the beta version the view was showing an outline type view, while the stable version was a list type view (and therefore the item I was looking for was being shown inside another item and therefore the discrepancy). When I switched the board in the stable version to be of outline type, 1 second later the board in the beta version just went blank and to the default prompt to create a new board!

webalstrom

Not a huge deal, compared to missing documents and the app not working, but when I logged into the beta (using incognito), I noticed that the Document sidebar is not showing the hierarchy below one level deep. I can see the name of of the document, click the carrots to show the first level. The carrots show next to each element on this level, clicking on them rotates them, but nothing shows. Everything displays fine in the pane.

Other than that, everything seems to be working fine for me. All my boards are there and working (although they were reordered, but rearranging them back, closing the beta and reopening seemed to keep them in the correct order). The app opened up pretty quick (about 4 seconds of the loading documents screen). Changes I make in the beta reflect in the stable and vice versa.

Just FYI: I have 5 documents. two are around 12,500 items each, one is around 1000 items, two are under 200 items each (this does not include the ones in the trash).

Jerud

andrew I got these same two issues (documents never load, and duplicate documents) when switching to beta as well. I got past it by reverting back to stable, then beta, then stable, then beta again. Not kidding; I really am just a stubborn caveman. It finally loaded : 0

I dismissed the duplicate documents errors as an artifact of switching to new backend – would have saved a little heartburn to know they would appear ahead of time but it at least was explainable and I saw no missing (or zombie) documents as others have.

Jay

Thanks a ton for your patience and detailed reports everyone! A big change like this is always going to be bumpy, but I think we’ll come out the other side in a much better place than before 🙂.

Eik andrew I think I’ve fixed the causes of those errors. If I didn’t, I set up better error reporting so it will be easier to track down the cause in the future.

andrew Jerud Is that duplicate document error happening in the stable version? That would be because the beta version caches everything to local documents instead of the internal cache (so that you can back the files up yourself, and it’s much faster). Then the stable version doesn’t understand that so it sees the files and thinks they’re local documents, and ignores them because it already has a synced version of them. If that’s happening in beta I’d need to look into it! But if it’s in stable there’s nothing to worry about 🙂.

I’ll keep looking into the other issues you’re seeing. This should (hopefully) fix all the load errors and leave only some display issues remaining. If you see that an error you already reported is still happening, please let me know so I know it wasn’t fixed. Thank you!

andrew

Jay I cleared out all Legend data on my PC and reinstalled, then got stuck on Loading, but realized it was in Beta mode, switched to Stable, then it loaded and I had duplicates of every document, plus another My First Document. Then my PC crashed while using Legend and after restarting, I started Legend again and I now have one version of each document (after trashing the My First Documents). My original main document, which had come back as the version from a year ago, is now not present again but the copy I created is still OK.

Should I stay on Stable (where it seems to work) or go back to Beta (which seems to bring on these problems)?

andrew

Actually in Windows desktop Stable, I can’t access some boards. When I click on the board, it does nothing. Other boards I can access. Can’t identify a common thread.

Also in one pane, an advanced filter got turned into a regular filter that was missing some of the advanced filter terms. Not a big deal for me, but mentioning in case it affects others.

Jay

andrew I’d suggest for now using the beta in a Private/Incognito browser window. The desktop version does some extra things (saving to files instead of in the embedded browser’s storage) that may be less stable. And if there’s any problems it will be with the local cache so you can just close the private window to clear it. I’ll keep working on testing everything reported here in the desktop app and make sure all is good. It’s been working great for me but everybody has different document data so I have to try to find the bugs that are being hit.

andrew

Jay OK I am running beta in Incognito. Observations:

Beta now shows my original main document that had been missing and it appears to be current (reflects changes up through the time I copied all items to a new document). This was not present in Stable, but then I closed and restarted Windows desktop in Stable and a document by that same name appeared as a local document with no items in it.
In Beta, a few of the boards that I can’t access in Stable (the ones that I click but nothing happens) are not present in Beta. I thought it might be because all panes refereneced the original document now present in Beta but showing as empty local in Stable, but I changed the document in all panes to refer to the new document now present in both Stable and Beta but I still can’t access in Stable. One of the other boards that uses the original doc in all panes is accessible in Stable but the panes refer to a different document.
In Beta, I also cannot expand the second level of Overview tree, only the first, as described by @webalstrom
The following Advanced filter appears correctly in Beta but in Stable shows in non-advanced mode and without the part in parentheses:
(is:star or before:tomorrow) is:task -is:complete

Jerud

Sounds like I’m in the same boat as @andrew. I thought I had moved successfully to beta but that no longer appears true. I opened Legend last night and found total swiss cheese: randomly missing boards, some boards visible but un-clickable, randomly missing panes on the boards I could see, panes pointed or defined wrongly, randomly missing docs, and randomly missing items within docs.

I fully uninstalled Legend in all locations, then reinstalled. Things look fine in stable. I tested switching to beta once and got the same Loading… delay as before, at which point I just switched back to stable, where I shall stay for now.

A few details in case they help:

@Jay you are correct the duplicates warning only happens upon entering stable and I’ve seen no negative impact.
This is all on windows desktop, which is my non-negotiable primary use
I use the same Legend account from within two different Windows “users” (work vs. personal) on the same machine. The app is installed “for all users”. My initial switch to beta was in “work” user. The problems last night happened when I signed in as “personal” user.
The “Loading…” screen that hangs up when switching to beta has an interesting glitch: the three bouncing dots are corrupted. Sometimes they don’t appear at all but usually they appear with a “broken” animation. I find this noteworthy because I assumed this to be just an animated GIF or similar, in which case glitches might cause it to pause or move slowly, but follow the same pattern. Instead, the animation is actually “wrong”. Normally they bounce up and down with a slight stagger, so they make a “wave”. But I see the 1st dot moving on its own pattern while the 2nd and 3rd dots are moving together - slightly misaligned, but perfectly in-phase. Are they three separate single-dot animations that are just started out of phase? Is there any significance to the 2nd and 3rd not getting properly phased?

andrew

andrew Jay I need to correct my post above:

When saying I changed the document for the panes in Beta on the boards that were inaccessible in Stable, I was referring to the subset of boards that were inaccessible in Stable but were present in Beta. Of course, I couldn’t change the document for the panes in the boards that were not present in Beta.

The advanced filter in Beta that was converted to a non-advanced filter in Stable was not actually just the same filter without the parentheses, rather it was set to exclude complete and include high priority, or effectively:
-is:complete pri:high

Jay

Just released an update which should fix a few miscellaneous errors with sync and load.

One of the hidden changes in the beta version is that we’ve upgraded to a new/better error reporting service, and this update fixes an issue we’ve had forever, that adblockers were blocking error reports. It now proxies error reports through our domain so that won’t be a problem anymore 👍️ . And error reports are now tagged by app/web and with your userid, so when you post an error report I can find exactly the problem that you hit. I’m pretty excited about that 🙂.

It sounds like there’s still some issues with upgrading from old beta data, and the interop between stable and beta. Those will of course go away when we fully release this to stable, but I’ll investigate and make sure they’re not real problems and try to fix them anyway.

Jorge

After trying this new beta release, I still see problems in the display. I still cannot see my Inbox branch.

The agenda view has gone berzerk. When I select a pane with my personal document and select outline view grouped by agenda at the beginning it looks normal with overview items expanded. But if I collapse the overview group the whole pane goes blank and it only shows a Today group with 0 items.

In fact, any change in the filter or collapsing, causes the pane to display the Today group with 0 items. the only way to reeestablish the contents is to change the Agenda mode.

Jay

Thanks Jorge, I’m reproducing that here. I’ll get a fix out soon.

Jay

Update: I’ve got the agenda issues fixed, with new tests to make sure that doesn’t break again. A big part of the recent board improvements (that fix sync issues) was to reduce the size of the pane element IDs, but I hadn’t gotten them in every spot so there was some mismatches in ids in the agenda view. I’ll test it some more while working on some of the other issues and aim to release an update in the morning (8pm here in Japan).

Jerud

Nice to know about improved error reporting although frankly the only time I’ve ever seen the “send a report to developers” toast was randomly, when nothing appeared to actually be wrong.

Can you add a button to manually generate an error report or application-state freezeframe, so we can submit that along with a bug report if the ‘notify’ toast isn’t part of the symptoms?

Any feedback on the erratic typing/focus loss/keyboard navigation issues I saw while I was in beta? I sure don’t want that to end up in stable, it made it hard to get wok done.

Jorge

Jerud
There is an option to manually trigger the error reporting: Options > Contact Support.
Not sure how much logs or metadata go with that report, but it would be ideal when you trigger that, that basic debugging information could be sent (with the user’s consent) to Jay for additional info on a specific problem.

Jerud

Jorge I should have known that 🤦 thanks for the reminder!

But maybe not a bad idea to just ask @Jay specifically: does the ‘contact support’ function benefit from the improved error reports functionality? Does it make it any easier to handle bugs in the absence of good repro?

« Previous Page Next Page »