Scott T.

@JMichaelTX As of this moment, Evernote has its fair share of experienced engineers along with more junior engineers. For the multiple re-architecture initiatives that are currently in process, we have experienced engineers actively leading and contributing to these projects. We also have a team of the more senior/experienced engineers in the company that meet to review and discuss any new architecture projects. This has really helped to work through potential problems with designs or technologies earlier in the process.

@mvdweer Yes. Somebody reached out to me about the tweet which is why I came here to comment and provide the additional details regarding the recent contact. I tried to work on this myself, as I originally believed it was our integration. When I found it was their integration, I provided them details including how to reproduce the problem. I'll post a follow-up if I hear back from them.

IFTTT previously looked into the issue and believed they addressed the bug. A few days ago, we reached out to IFTTT again to let them know users are still encountering problems with the integration. They opened a new ticket and are investigating. Unfortunately, Evernote doesn't control this integration. It was built entirely by the IFTTT team. Our business contacts are in touch, though, should there need to be any communication between the dev teams.

@Rxx, I would suggest reaching out to our support team. They should be able to help track down what is going on and make sure you have 2FA setup correctly. It will also be helpful for our security team to have the additional information to understand if this is a different attack beyond the one we have been tracking for several months.

Regarding local notebooks, I previously posted this: I know it isn't a 100% guarantee, but I'm pretty confident in the response from the lead. We understand the importance of local notebooks to a subset of our users.

I believe the tone of the release notes is intended to make Evernote personable. This is definitely not unique to Evernote, and we've received a number of positive responses to them as well. Given that past sentiment on the board was that Evernote was not taking any interest in users and not communicating, I think any attempts by the company to have a more personal conversation is a good thing. I personally enjoy the tone. The notes still convey what was changed, just with a little extra fun.

@Visionline The last status I heard was that we had a potential fix ready to go out. We didn't have a release last week due to some special events internally. It should be going out this week. But, it's worth mentioning that we aren't actually able to reproduce the issue internally (we've definitely been trying), so the fix is based on a best guess of the issue by the development team.

@Jeshi, just wanted to let you know the developers are actively looking into the issue. I'm sorry I can't provide more context than that, but wanted to make sure you knew that we weren't ignoring it.

Thanks @Jeshi. I will make sure to pass this on to the dev team. When it reloaded, I assume the pasted content was gone?

@Jeshi It definitely sounds like you're hitting the issue that our devs are looking into with regards to large notes and often with pasting in of large images. One of our support staff commented about this in the other thread. @Ashley Gittins I'm glad you aren't running into the issue too much. We'll hopefully fix it soon. With regards to the bulleted list issue, I noted in another thread that the issue comes up with using the older client that we won't be fixing since we're focused on the new client and editor. I think you'll really like the new editor when it's ready. We're using it internally. It shows a lot of promise for addressing many feature requests (and bug requests) with the existing editor. Also, I'm happy to be more engaged with the community. It's not actually my main job, but since part of my job is around product quality, I think it's important I understand the issues the customers are encountering. It's already helped identify numerous bugs and usability issues that I've reported to our development teams.

@Jeshi Sorry for not responding at all. I was OOO all last week. We've got developers looking into the issue in this thread, which I think may be similar to what you're seeing? Just the error is slightly different because of being a different client. Like I the other thread, can you provide any details on attributes of the notes that exhibit this behavior? Are they larger notes? Do they include attachments? Are you pasting in a large amount of data at once? We're trying to reproduce internally, but haven't found an exact set of steps that causes the issue. It may be something specific to certain types of notes.

@Tidal1234 As I noted, we have numerous rate limiters in place (which will present a captcha or even just block) and we added another one just last week based on the behavior we're seeing. But, we can't go too far with counter-measures without the potential for blocking legitimate users. So it's a balance.

@jessicaevernote Are you using any Google Chrome plugins that might be interfering with the Evernote web application? This might be an ad blocker or some other plugin that interacts with and/or modifies the content on the page.

@Jeshi Can you also please let me know if you are running any Chrome plugins that might be interfering with the Evernote web application, such as an ad blocker?

@Jeshi I'm able to reproduce this issue, but only in the scenario where I have two editor windows open and I'm going back-and-forth editing in the different tabs. In that case, the message is accurate (though not really friendly). We're letting you know that the sync failed because there is newer content on the server and the window needs to be refreshed to display the latest content changes which occurred outside the editor. Is it possible you are editing the same content anywhere else? I assume this probably is not the case, but helpful to at least rule out the scenario.

One of the devs believes the Unchecked runtime.lastError comes from a Chrome plugin as well (see https://developer.chrome.com/apps/runtime#property-lastError). A suggestion was to try opening the Evernote website in a Chrome incognito window, since that should disable all plugins (unless you've explicitly allowed the plugin in incognito mode). That would help us determine if there is a plugin issue or not.

Hi all. I'm following up to confirm that we pushed a fix out for this issue on 03/27. Please let me know if you continue to encounter any issues with revoking a device.

Hi all. I'm following up to confirm that we pushed a fix out for this on 03/27. Please let me know if you continue to encounter any issues with revoking a device. @EdH I agree wholeheartedly. However, we have complications with how we do deployments that getting out hot fixes is not easy and also disruptive itself. So it's a balancing act when deciding whether to disrupt our users for a brief period of time to make the fix. As part of our rearchitecture efforts, we will be making changes which should allow us to deploy individual changes faster and independent of other changes.

Hi all. I'm following up to confirm that we pushed a fix out for this on 03/27. Please let me know if you continue to encounter any issues with revoking a device.

Thanks @GTKZ. The only interesting thing in the screenshots is the last error in the first one. Other errors are ad blocker and I think the first is an expected warning. I'll double-check this with the dev team and get back to you when I have an answer.

Hi @GTKZ. Thanks for the additional info. I'll follow-up with the team tomorrow when I'm back in the office. If you are able to, can you open the network tab of the dev tools and make sure the web client has fully loaded (network activity stopped). Then clear the network tab out and try editing the note. Then send a screenshot of that. It will help to see if one of the calls is maybe timing out. We'll be looking for something like "utility" or "notestore". Those will be the updates/syncs. If you do the same thing on the old client, the calls should also be "notestore". Hoping this will help us figure out what is going on. Also, let me know if you are running any specific Chrome extensions. We sometimes see issues with them interfering with our calls. I think we're generally OK with most of the popular ad blockers since I know some devs use them. But, would be good to know just in case. Though, you indicated you saw something similar on Edge, which would lead me to look elsewhere, like network issues or firewalls. LMK if you have anything like that.

@GTKZ, can you provide details on the exact error you are receiving? Please provide the exact text, if possible. Also, if you are familiar with Chrome dev tools, you could open up the Javascript console and see if there are any errors there. Also, you might consider trying the latest web client again. That's the version that we are actively supporting. If you encounter issues in the older web client, we will be less likely to address the issue if not urgent. Though, if there's an issue saving notes, that would definitely be fixed.

I believe the preferred client is controlled by a preference setting. It shouldn't exist if you have never visited the newer client. The second link in my post above included a parameter that might have set that. I included it on purpose to force the old client to load. Depending on which you visited, that may have set the pref. Regardless, you can switch between the two clients by opening the profile menu. That's the menu that opens when you click on your profile picture. There's an option to switch to the newer or older client. That should set the preference setting accordingly. As I noted to @CalS, I think we're aware of the confusion between the versions. We're trying to fix that.

My understanding is that stacks is coming very soon to the latest client. For shortcuts, I'm pretty sure I've filed a ticket for the missing functionality and some of it was intended. Can you provide details on what specific shortcuts are missing so that I can make sure to raise those as an issue? Total transparency: I'm not convinced we (at least in the past) had a clear versioning strategy. This is something we're working to fix now. In fact, I got an update on my inquiry about calling the latest client "beta", and they actually want to leave that until we've met feature parity with existing clients.

@CalS Just to follow-up and clarify. This is the latest client and the one we are actively developing on. It is not a "beta" client, though it seems we still reference that in at least one place (PersonalSettings.action). I filed a ticket to address this and hopefully we'll remove all references to beta: This is the previous web client that has existed for quite some time. New development has ceased. We're fixing major bugs if we get a report, but efforts are all focused on the client above. There are features in this client that don't yet exist in the latest client, but we intend to support those soon or clearly indicate they're deprecated (hopefully in favor of other features which replace the functionality): As noted, the classic client is REALLY old and only those accounts that are old enough to have actually used it are able to access it via a setting that grandfathered them into having a link to it.