I'm re-posting this issue that I've seen pop up again and again on these forums going all the way back to 2014, and nobody seems to have a definitive explanation or an answer for what's causing the discrepancy between note counts across devices. Any official responses I've seen have been "known bug" claims, but this is something that hundreds of users have been mentioning for a very long time and it's still not fixed or explained. Some users have offered their takes, but none that I've seen have solved the problem.
Simply put, the total note counts don't match up across any of my devices or versions of Evernote. I'd really, really like to know why. I'd also really like to know if I can be totally confident that the notes I create on one device are successfully syncing with my Evernote account and broadcasting to all of my other devices. That's what we're told should be happening and that's what I'd ideally want from a note-syncing service for which I pay a regular subscription fee. I don't want to have to run tagging experiments to see what I'm missing from what device, because clean and accurate syncing is what the service is supposed to provide – and what it promises that it provides.
My disparate totals are as follows:
Evernote Web: 5433
Evernote Legacy Mac: 5819
Evernote 10 Mac: 5599
Evernote iOS: 5582
Evernote iPadOS: 5794
It shouldn't be an issue with shared notes or notebooks, as all shared notes should still be accessible from the account no matter the device, both incoming and outgoing shares. It's not a Trash issue, and it's not an identifiable setting like offline downloaded notebooks on different devices. I'm especially concerned about the c.300 missing notes between 10 and Legacy on the same desktop computer.
Would someone on the Evernote team please explain what this is all about? If it's still a bug or known issue, why has this not been taken care of in the seven years it's been flagged repeatedly? If there's a reason, would you please let us know? It seems to me that this should be a baseline functionality that needs to be shored up and explained before any further bells and whistles are added to the next iteration of the service.
Thanks for any information you can offer, but please offer something if you can.