mz123

@Ralph77 I'm not certain it would help. You can somewhat disregard that message. About 2 weeks ago, I accidentally upgraded myself to 8.12.2. I haven't seen the issue described here, so perhaps whatever is triggering the problem isn't applying to me. Nonetheless, my circumstances don't present any strong evidence that 8.9.1 avoids the problem. Perhaps it does, but perhaps something else is at fault. It could also be a server-side issue that applies to certain people. I hate this circus. I miss the days when I could upgrade Evernote without fear that the upgrade would include debilitating bugs. There have been too many lately. I really hope Evernote identifies the root cause and fixes it before I run into it, as downgrading, adjusting settings, and re-syncing offline notebooks is not how I want to be spending my time.

Which version is it that's hanging? Is it version 6.20? Thanks.

Anything unusual about the notes? Something in common that might lead to a workaround idea?

Has anyone figured out the conditions that trigger this bug? I feel as if there aren't enough posts here to indicate that all users have it, but that might not be true. Perhaps all do, but only notes with certain content do.

Thanks for the update. After being burned badly twice this year with really bad bugs introduced in updates, I am holding off on updating due to this issue. For what it's worth, I haven't seen this issue on v. 8.9.1 I hope the reliability of Evernote updates improves enough so that I don't feel the need to scour forums for bug reports before installing an update. For me, it's not always as simple as install / uninstall. I have large offline notebooks that need to be re-downloaded over many hours (and apparently many failures). This is not required when updating, but downgrading always requires an uninstall, which causes this headache. I'll be watching this, so any updates are appreciated.

Your experience mirrors mine (on a manually installed APK), but I did get notified of updates on the Play Store eventually. I received the June 26 update a day or two after release, for example. I believe that publishers on Google Play can roll out in stages or with delays, and some people get the update later than others. That said, I'm surprised you don't see anything after June 5, as there were a couple of releases since then. Perhaps try clearing your Play Store cache and restart your phone. I've had glitches in the past where many updates showed up after performing those steps.

The current beta is 8.11_beta1. It doesn't fix the issue, at least not on my device.

Hmmm. My steps describe performing the same action twice. It freezes on the second time. Is that what you did? Or did you have to try to start a new note 3 or 4 times before the freeze? I'd be surprised if someone doesn't have this issue.

Just FYI for some that speculated this may be a server issue: it's not. I can recreate the exact same behavior from airplane mode.

For those of you who think you have an intermittent issues or no issue at all, please try the steps I posted to recreate the issue - for me it happens every time. See my post in a separate thread on this problem here: This is the same issue described here. I later clarified that the app does eventually unfreeze, but for me it takes well over a minute. I am on a modern flagship phone, have no other performance issues, and a fantastic internet connection.

Gazumped, Are you still not having issues? Have you tried my steps above? They are a sure-fire way to recreate the problem for me. Just don't wait between them... do them right after another. You are the only person I have seen chime in and indicate that your phone is immune to the issue, so that's curious.

Ok, mine eventually unfroze too, but it took almost 2 minutes. That's as good as never.

How long did it freeze for?

I'm running the newest stable channel Android Pie with the June patch. It certainly possible that the new Evernote has a problem only with newer Android versions, as I've noticed that those reporting no problems are on older versions of Android? I can recreate a crash every time by doing this Create a new note. Delete, don't save. Try to create a 2nd note. You'll find you cant type in the content area, save, or delete the note. App essentially frozen. Force-stop Evernote to "recover" to a state that will let you do step 1 again or potentially open a note without error.

The latest version release, released on the Play store yesterday and marked as 8.10, is quite horrible. Opening notes, saving notes, adding photos, all cause freezes / crashes. Not every single time, but quite often. Why does Evernote keep releasing such buggy updates? It feels as if even basic testing is not being done.

A similar issue, where an entire screenshot is blurry / low-resolution, has been occurring in the Windows Chrome Web Clipper for over 2 years now.

You're welcome. I can see from my experience and others' that eventually something in Evernote's approach changed from "no old APKs" to "here you go, an old APK". I didn't expect a gracious reply and thank you - appreciate it. Note that I agree that a quick bugfix may be a big ask. I was advocating merely that Evernote make the old APK available immediately, via an update where the old APK is re-packaged with new version number. I don't think that's a big ask at all. Here's to better software coding, either way!

Some counterpoints to your response: I suspect you were slower to ask for help. I asked for help, and over a week went by before I received a reply like you did. I suffered with the bug for 2 weeks in disbelief that it was taking so long for Evernote to act, then waited another week after contacting support before this solution was offered. The path to get to this workaround was painful. I was first offered no solution ("we're working on a fix"). After repeatedly asking for a previous version's APK or a refund, I was eventually offered links to a third-party APK download site by an Evernote employee! I understand software development too. Reverting to a previously released version immediately was (and still is!) the best solution. After all, support is offering exactly that to users. Within hours of discovering this bug and understanding its impact, Evernote could have simply re-released the previous APK as the next update. They still can, and should. They can then work on implementing a bug fix into the next release version at their leisure. I understand that new release development requires testing, etc. However, a re-release is not the same. Reverting code to a previous version is technically simple, and requires no additional development or testing. It's simply like an undo-change. Put another way, it's like simply delaying a release further, or pulling an unauthorized release. It doesn't require business analysis, QA, or dev ops, in more than a trivial way. There is no excuse for Evernote eliminating a mission-critical feature from what is arguably their most important platform, for an entire month (and counting). I don't care how much they innovate their software, or how much that innovation will be delayed by doing what I described above. If one can't search, the app is nearly useless to a large portion of users. New features and rapid development are nice, but they are not so nice as to allow the software to become useless to users for a month. So, I quite disagree with your post.

With a bug this serious, Evernote should have rolled back code in its entirety to the previous version 1 hour after discovering the bug, in my opinion. If one uses Evernote as it was intended, designed, and marketed, it's simply unusable without a functioning search. One can't use a second brain if one has no idea how to find anything in it.

Most will tell you not to install apps from third party sites, as they may contain malware. Evernote should make a downgrade (or an upgrade with the old code) available. There really is not excuse for this. Evernote made a video where they talked about customer focus. Letting this issue continue for so long without any resolution is very anti-customer.

How can Evernote not fix this hours after it's discovered? This sort of problem is so fundamental, they should do a code rollback to the previous version. In the meantime they're releasing dark mode improvements?! Evernote: why?!

OK, I wasn't aware of the nuance here, and in sum it's really odd. For starters, typing evernote:///view/... does not create a link that's clickable, whereas www.evernote.com/shard/ does. Android, and its apps, don't know what to do with a classic EN link in general. But.... I found that your approach works for me too, in the way you described. However, it's not going to work in most apps, and never works unless I first "prep" the link in Evernote. For example: If I copy the link out of an Evernote note in Android, it works as you described, but only in some apps. I can't paste that link into Google Keep for example, or a Google Doc. It works in my calendar app though. If I instead simply grab the URL directly from Evernote Windows "evernote:///view/...", without first pasting it into a different Evernote note, and share it somehow (in Google Keep, in Remember the Milk as text, or in a calendar event), it isn't even recognized as a link in Android, and it's not clickable. If I paste that text into Chrome Android, it simply searches for it in Google. Interestingly, if I paste the text of the URL into Remember the Milk Android, but in the URL field, it somehow now recognizes it as clickable and sends it to the Evernote App. My most common use case is actually #3. I never realized that a link might work out of the URL field, but not out of a note field. All other links are clickable out of a note field just fine. It seems the Android OS doesn't make evernote:/// links clickable, but Remember the Milk figures it out. I strongly suspect that's due to their behind-the-scenes integration with Evernote, which I actually did not use or even enable. I suspect many, if not all apps don't recognize links of the form evernote:/// - perhaps #1 works in some apps, such as our calendar apps, because some apps simply paste links without bothering to somehow validating them first. In other words, Keep, Docs, and other apps look at the clipboard and say "here's a link that's not actually a link, so I'll just paste the text part". Our calendar apps simply paste what's there, and it turns out the links are valid for the Evernote app. It would be great if you could validate the above to ensure things aren't different between our phones. Bottom-line: on my phone (and I suspect on yours too), Android and most apps don't know how to deal with evernote:/// and do not treat those as valid links. Some apps are the exception. On the other hand, www.evernote.com/shard is obviously a web link, and will be handled that way and intercepted by the installed Evernote app, providing a more consistent experience. So, standard links always work on Android, wherever you put them. Classic links only work if you first copy them out of the Evernote app within the phone (or within Remember the Milk's URL field, likely due to those companies' integration partnership).

One note here... before I found the workarounds, I saw the button. However, to get the button requires me to be logged in with the browser. I'm almost never logged in there.

Several problems (see higher in this thread for details): It doesn't in all cases. It used to never do so with the Windows app installed. It shouldn't today, with the Windows app installed.

Now sure what you mean by #2 and #3. I mean links created when I select "Copy Internal Link", which look like this: https://www.evernote.com/shard/s3/nl/... By the way DTLow, I'm rehashing stuff here. Everything is spelled out in great detail in this thread: the problem, various workarounds, and disadvantages of the workarounds.