eric99

While I still don't have a collaborative editor, I'm already noticing performance improvements with the new 10.50.3 release. And more importantly, the hangup I reported last week seems to be resolved so far. I have the impression that they are regaining control of their software 👍

Does editing also stay fast with large text notes?

This is the technology underneath: https://yjs.dev/#features The offline support is fascinating as well:" No waiting for slow connections. The shared data can be stored in a local database (e.g. indexeddb) and will be available right away. Render the information you have and sync later. " Has anyone with the new sync tested that already? edit: this is what I hoped for, they use a mature library instead of trying to program it themselves...

Yeah, electron/react apps force people to buy a new phone every 3 years, creating a dramatic amount of e-waste. Very bad for the planet

Good to hear that the new sync is still compatible with legacy, and that it works flawlessly on mid-range Android phones as well. What phone type do you use?

my question is whether edited or newly created notes in your latest V10 can still be edited in legacy later on. Or in other words, is the database and note format still downwards compatible?

And another pressing question: can you still view and edit the newly created notes in the legacy versions?

is your android version 10.50.2 ?

no glitches anymore? what kind of phone are you using?

So, not so much different from Evernote then, they don't have a working android app either 😏

Where can I find the Android client?

The ticket is directly followed up now by the Director of Technical Support. Hopefully, after two years, this kind of issues gets more attention now...

Yeah, and this is still relatively fast since I just reinstalled everything. After a week, it"s already much slower. But have you noticed the actual problem that when back in the note list, I clicked several notes attempting to open them, but the client was unresponsive from then on, for hours, until I restart the client (although everything is synced, I checked that in my other clients)

FYI: This is the screen recording when the race condition bug occurs: https://drive.google.com/file/d/18Jwuo4XvnM5PiIg_oMtFMK6Xe2S1Be71/view?usp=sharing I've raised a ticket

So the beta has been finished successfully then?

It happens at slower speeds as well, but there is a higher probability when acting faster than your phone or the EN server can handle. Your high end S22 phone is much faster than you, therefore the race condition bug will occur less frequently. https://en.wikipedia.org/wiki/Race_condition#In_software High quality software should use proper software mechanisms to protect itself against all potential race conditions.

I think this name was invented by the EN developers, but the more interesting part is the schizophrenic state the system is in: part of the system thinks that the editor is still busy although it has been closed, fully synced and we are already back in the note list for hours...

I've sent the activity log to support with the proper timestamp "ERROR: neutron: Note editor not saved, because editor is not ready:" it stays in this deadlock until the app is restarted This is a typical race condition: I can reproduce this easier by very fast note creation/closing (a small title and a single word in the body and closing immediately, all this in a few seconds). I doubt that this will arrive at the developers' desk, considering my previous unresolved tickets concerning performance and sync problems...

Sorry, I was replying to @spersephone post

Unfortunately, the problem is there again, probably caused by an unhandled race condition. I'll investigate it further tomorrow...

thanks for the tip but it didn't help. In the mean time, after complete uninstall/reinstall, I can't reproduce the problem anymore (so far) Maybe, the timing is different after the fresh install which makes race conditions less likely or there is a version incompatibility (my app was reinstalled just before 10.50 arrived, so a corrupted database or something like that was probably not the root cause)

Yes, I already tried to uninstall etc but no avail. It can easily be reproduced by creating a new note on the android client. After closing, the note list is displayed again and it looks completely normal. The new note is synced on my desktop as well. But my android client refuses to open or create any other note from now on, it just stays in the note list, clicking does nothing anymore. When I stop the app (no logout, just stopping) and restart, everything is fine again until the next new note.

Did the update as well, and there seems to be a dramatic regression unfortunately. After editing a single note and closing it, the android client gets unresponsive until I stop the android app and start it again. This is 100% reproducible. It seems to me that developers have lost control of the Android client and don't really know which screws to turn. It goes from bad to worse 😕 I've seen this behaviour in the 10.49 as well, but then I reinstalled from the app store and got 10.48 which doesn't have that problem

What device are you having these issues on?

Thanks for the tip, I didn't realize that the striketrough can be turned off. But in that case, @PuddinHead's shopping list problem has been solved I think ?