For Evernote users who use TaskClone (seeing duplication of tasks and how to prevent it)

[DrFrankBuck 254]

This information is from TaskClone:

Duplicate Tasks in Evernote

Without notice, Evernote recently released an update called "Real-Time Editing" that apparently blocks notes from being updated by their API while the note is open in the app or browser.  This change means TaskClone is unable to update notes with Skip Codes or remove the Trigger Tag.  This will ultimately cause tasks to be duplicated when the note is edited again.  For now, please make sure that you close the note in your browser or app as soon as you add the Trigger tag.  Please allow 2 minutes before opening the note again so the process can complete. 

We will update here when we have a more durable fix.

 

Source: https://support.taskclone.com/article/358-duplicate-tasks-in-evernote

[gazumped 9,812]

Hmmnn.  I'm not a TaskClone user,  but I'm into Filterize in a fairly big way... wonder if anything similar applies there...

[agsteele 1,838]

It actually applies to all apps that run through the API. 

Similarly described in another thread

 

 

[DrFrankBuck 254]

I was also seeing an issue with IFTTT applets where the action is appending to an Evernote note.

The solution was to be sure the destination note in Evernote is closed. 

[realistdreamer 7]

We all know Evernote's API is outdated. What many don't know is they haven't updated the documentation in years so it doesn't reflect the currently reality of the product. 

Every single app that uses the API is a Legacy app and at risk of breaking since version 10 was released. 

Ian said "the backend needs some love" but that love has never been documented or accessible to developers. Early on, Evernote's detailed API made it the note app with the most integrations. That is already changing and if this isn't addressed, it will accelerate that change while breaking the existing integrations that haven't given up. This technical debt is assuredly a headache for the company too. 

[Ray Sidney-Smith 120]

2 hours ago, realistdreamer said:

it will accelerate that change while breaking the existing integrations

I want this issue resolved too. It's frustrating that I cannot connect to my productivity apps the way I expect them to, and that's one of the driving values of my Evernote usage.

Something to note, this will only get worse before it gets better. While Evernote/Bending Spoons, I'm sure, still intends to update the API it would be at this point a whole new API might make sense to eliminate much technical debt. (Of course, they may intend to stay with Thrift.) They will need to wrestle with which API protocol to choose (again), which would likely break all the existing integrations that don't update to the new API protocol, and specs.

Realistically, the existing dev.evernote.com isn't going to be touched until they decide to do something with the API. It hadn't been updated in years, why start now? Lol.

I'm saying all this to temper everyone's expectations around this (as an outsider looking in) because it's a heavy lift that doesn't seem to be top-of-mind for Bending Spoons at this time, and when it does hit the roadmap it's going to be like the transition from Legacy to v10+! 

[realistdreamer 7]

11 hours ago, Ray Sidney-Smith said:

Realistically, the existing dev.evernote.com isn't going to be touched until they decide to do something with the API. It hadn't been updated in years, why start now? Lol.

Before the acquisition, I understand they were "planning" what to do with the API so they could incorporate things like Tasks.  Building a new API with something different than Thrift is a well worn path.  However, transitioning all the apps that depend on that transition being successful will be a herculean effort.  Having both APIs partially operational at the same time also seems like a huge headache (although they are using ENML and another format simultaneously now).  My larger fear is that being a mobile-first company, BS may de-prioritize integrations altogether.  To your point, EN had not touched the dev site for years and has a app marketplace that exists in a similar state.  Why start now?