eric99

This is not my experience: sometimes support seems to be completely ignorant of an issue that has already been submitted multiple times by other affected users. I can't find the issue status at https://help.evernote.com/hc/en-us/requests . The only status I get is that it's solved which isn't the case. For some tickets I'm still waiting for 2 years to be solved.

The major problem with tickets is that related issues/info from different users get scattered over several 'independent' tickets. And the worst problem is that it is extremely difficult to get the ticket to the developers, it is always shielded by various impenetrable levels of support and the status of the issue is kept secret for the end-user once it has been fed into the pipeline. I believe much more in the agile interactive way of bug reporting/solving on the forum, like Federico already did successfully for some urgent problems.

Here's a list of the regression issues I'm experiencing in 10.59.5. Have you already tested this yourself? https://discussion.evernote.com/forums/topic/146555-👉-input-needed-– what-issues-did-you-experience-in-the-last-couple-of-days/?do=findComment&comment=692061

To prevent this kind of chatGPT reactions from support, I always added a forum link to my tickets to provide more context. Apart from that, this "notebook access denied" problem has been introduced in the latest release, they just have to check the changes they made in the latest release to find the problem...

Yeah, since we are on @Federico Simionato 's thread, I hope to get some response too on the v10.59.5 regression list: https://discussion.evernote.com/forums/topic/146555-👉-input-needed-– what-issues-did-you-experience-in-the-last-couple-of-days/?do=findComment&comment=692061

"...Those inline images are CDATA encoded base64 strings. They don’t include a hash, but I figured out that decoding the base64 string and then running it through MD5 generates the hash that is used in the corresponding <en-media> tag..." https://simonwillison.net/2020/Oct/16/building-evernote-sqlite-exporter/ So, as I read this, it's a MD5 calculation on the raw image data.

I found out that the global search oscillation is caused by the sort order of the result list which was default set to 'relevant' . Apparently it's trying endlessly to find the most relevant order and gets never satisfied, probably because I write only highly relevant notes 😉. When I set the sort order to 'update time', the global search seems to work normally. The other problems I mentioned before are still there. edit: even with the 'update time' sort order set, there is another problem: when scrolling to the bottom of a result list with length > 128 ( 2^7 ), it always jumps back automatically to the top of the list. So the notes at the end of the list are unreachable.

That's the advantage of a unified code base 😉

There is an obsidian search plugin that handles OCR and PDF

EN data is just encrypted at rest, it can still be accessed by Evernote employees. Obsidian or joplin employees can not access your data due to full E2EE with your own private password.

Yes, very frustrating. I'll further check Obsidian and Joplin in more detail. Both have full E2EE AES 256 encryption, a big plus.

Yes, I have several search problems too:

Yes, race conditions bugs are hard to pinpoint because these are very difficult to reproduce. Actually, race conditions should have been handled in the early design and not as an afterthought. That's the only way to get rid of it.

Yeah, but this might be the result of taking over a monolitic code base: you turn one ***** to fix a specific problem, and suddenly an unexpected side effect occurs in a completely different piece of the code base. Therefore, before changing anything, much more (unit) tests should be written to verify that the behavior hasn't been changed after refactoring.

V10.59.5 should be roll backed or fixed urgently as this version is useless without proper search and with unpredictable behavior / crashes

Hmm, I wouldn't advice that, v10.59 is very unstable:

Yes, I'm also going back to 10.58.8. I don't trust 10.59.5 anymore, very unpredictable! SQA should test more thoroughly, especially now that they completely took over the software...

I logged out (cleared all data), reinstalled and still the same problem. It looks like the GUI gets in some endless (recursive?) loop after a search, refreshing every 2 seconds for a while. This confirms the React error 185 "Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate. React limits the number of nested updates to prevent infinite loops." edit: sometimes a global search does return a result list, but then after just waiting 10 seconds, it spontaneously starts repeating the search at regular intervals of 4 seconds forever.

@Federico Simionato The most recent windows client 10.59.5 (5236) seems to have serious regression now: searching in a notebook is denied with the pop-up message: "Permissions lost, you can no longer access notebook XYZ" sometimes global search in all notes returns the full note list instead of the filtered one. deleting a note by pressing the delete button doesn't always respond the note menu is sometimes completely grayed-out for some notes when scrolling to the bottom of a result list with length > 128 ( 2^7 ), it always jumps back automatically to the top of the list. So the notes at the end of the list are unreachable sometimes a global search does return a result list, but then after just waiting 10 seconds, it spontaneously starts repeating the search at regular intervals of 4 seconds forever. Edit: I found out that the global search oscillation is caused by the sort order of the result list which was default set to 'relevant' . Apparently it's trying endlessly to find the most relevant order. When I set the sort order to 'update time', the global search seems to work normally. The other problems I mentioned before are still there. Edit: here a complete crash by just clicking the notes button in the left side bar after the search oscillation (probably related)! Error: Minified React error #185; visit https://reactjs.org/docs/error-decoder.html?invariant=185 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at hi (app://evernote/4448.js:2:92504) at Lo (app://evernote/4448.js:2:64442) at app://evernote/6034.js:1314:10409 at Ui (app://evernote/4448.js:2:104192) at n.unstable_runWithPriority (app://evernote/4448.js:2:121861) at $l (app://evernote/4448.js:2:44842) at Fi (app://evernote/4448.js:2:103655) at bi (app://evernote/4448.js:2:95183) at app://evernote/4448.js:2:45065 at n.unstable_runWithPriority (app://evernote/4448.js:2:121861) at $l (app://evernote/4448.js:2:44842) at Yl (app://evernote/4448.js:2:45010) at Kl (app://evernote/4448.js:2:44945) at Ui (app://evernote/4448.js:2:104378) at n.unstable_runWithPriority (app://evernote/4448.js:2:121861) at $l (app://evernote/4448.js:2:44842) at Fi (app://evernote/4448.js:2:103655) at app://evernote/4448.js:2:103566 at I (app://evernote/4448.js:2:120921) at w.port1.onmessage (app://evernote/4448.js:2:119644)

I hope not, they've had over 2 years to get V10 right...

Yes, but they want to get rid of V6 without fixing these issues first. So this forces people to leave evernote before legacy stops 😕

weird, in my windows client it also occurs with a simple word search (but only when I select the notebook in the left sidebar) Have you already created a ticket or are they reading it in this thread?

Unfortunately attachment links in V10 HTML are broken. I reported this bug more than 2 years ago, EN can fix it by just adding a single line of HTML to the attachment icon: <a href="my files/john doe.pdf" style="text-decoration: none;"> They promised me several times that they would fix it, but for some reason they refuse to do it. Today's data loss issues make a working HTML archive more urgent than ever. I'm willing to keep paying for Evernote, but they have to deliver what they promise in their feature list.

yep, exactly like that, on windows client, same version as well... edit: no problem if I select a notebook via filters

Is this a known regression? When I select a notebook, searching within it is denied with the pop-up message: "Permissions lost, you can no longer access notebook XYZ" (my translation...) It's only a search problem because I can still visit all the notes in the selected notebook without any problem. Also, a global search will still return all expected notes