RonC

I didn't hear back from Evernote support, so I solved the problem myself. Here is the comment section of the python script I wrote: # This script helps corrects inconsistent date formats between Evernote 10 and .enex files exported from Evernote Legacy. # For a given .enex file, the script finds every occurrence of the form: # "<created>2023-09-15T17:49:22.631Z</created>" # and replaces it with # "<created>20230915T174922Z</created>" # which is the format that Evernote 10's import function assumes. # Similarly, the script finds every occurence of the form: # "<updated>2023-09-15T17:49:47.631Z</updated>" # and replaces it with # "<updated>20230915T174947Z</updated>" # On completeion, the script reports how many replacements of each type were made. # This script defines a function modify_dates_in_file which takes the path to the file as an argument. It uses regular expressions to # find and replace the patterns for 'created' and 'updated' dates, and then writes the modified content back to the file. Finally, it # prints the count of replacements made for each type. # Remember to replace 'your_Legacy_export_file.enex' with the actual path of your file. If you are an Evernote user, and would like the code, contact me. Please do not redistribute without my permission. If you are an Evernote developer, and would like the code so you can fix this problem for your users (it will be of use even after Legacy is decommissioned, as long as the .enex files were exported before then), please get in touch and I'm sure we can work something out.

Ticket submitted. Thanks.

Yes, it does, it by "automatically" you mean on first run, the existence of a local Notebook is flagged, a dialog is displayed, allowing the user to click to export the Notebook to .enex. That is the end of the guidance. I had to "manually" import the .enex file that was created.

Just downloaded Joplin and imported the same .enex file. Joplin's imported notes all have the correct creation date, so it's just a buggy import script on Evernote's part. I'm new here -- do Evernote PMs/developers read this and create tickets, or do I have to do a separate bug report somewhere? Or am I dreaming, and should find my own solution? Thanks for any help.

Finally upgrading to 10 because of the imminent demise of Legacy. I had one local Notebook, so exported it to .enex., then updated the app. For good measure, I also exported the Notebook when prompted during the first run of 10. I then imported the .enex file, and as has been reported by others, the "updated" date is unhelpfully set to the time of import. But worse, the creation date of all except for a few of the 279 notes is given as 1970. The few that are not 1970 are listed as having been created at time of import. I had a look at the .enex file and the correct "created" date info is in there (as is the "updated" info), so it just looks like an import error in 10. For example: </span></div><p></p></en-note>]]></content><created>2023-09-15T17:49:22.347Z</created><updated>2023-09-15T17:49:47.631Z</updated></note> I repeated the process and got the same result, except there were no 1970 creation dates; all were from today. Any advice for how to get my created dates back to what they should be?

Evernot 10.0 🙂

@bhermansI had the same problem as you. I updated my ipados to 14.3, and it finally synched.

I'm still in Mojave, but am also no longer getting thumbnails, just the default gray generic document icon.