Corrupted export of vector objects in 1.8

[Genefreak]

I've encountered a significant bug in the Affinity for Windows 1.8 upgrade. It was not present in the prior 1.7 version. This was confirmed by multiple users on multiple computers. It's very simple. If you make a vector object that doubles back on itself (for example, a line in the shape of a capital I using polygon mode), and then export it to .PDF or .EPS, the part of the line that overlaps itself is missing from the exported object. For example: this object in Designer:

 

Looks like this when you export it to .eps and then open the .eps in Designer. Same problem with .pdf export. It exports to .png, .jpg, etc. just fine.

Actual files attached.
To be clear, this problem caused a MAJOR issue for me. I was editing a manuscript that was accepted for publication at the journal Science. A very big deal for me and my lab. I was given 24 hours to make final edits before the figures would be sent to the printer. I (foolishly in retrospect) upgraded Affinity at the start of that period, and only discovered this error when I exported the finalized documents to .eps for publication and upload (they only accept .eps and .pdf at Science). For those who are familiar with research papers, you may notice that the shape above is the same as used for error bars in graphs. There were HUNDREDS of these in my figures. Upon realizing this was a software glitch (and confirming on another computer), I removed version 1.8, reinstalled 1.7, and attempted to open the figure files again. Only to learn that version 1.8 had altered the files in a manner that was not back compatible.

Which brings me to my next point. AFFINITY, WHAT WERE YOU THINKING when you made the upgrade convert and replace files with a new format, rather than saving a new copy in the new format?!?!?!? Why make it non-back-compatible at all? Why not notify the user of the change and ask permission before irreversibly modifying my files?
    I was lucky. I was saved by Dropbox's "versions" feature. I recovered the prior version in 1.7, then REDID all of the edits, and submitted only a few hours over the deadline (the Editor was understanding in this case. But it could have been a true disaster. 
   Look. In general, I LOVE Affinity and it's products. I've been preaching the gospel of Affinity to my lab, to other scientists, and online. But this was a true screwup. Not only was there a glitch in a truly basic feature that was introduced at upgrade, but there was a breech of trust in that the upgrade made irreversible changes to my files without notifying me ahead of time. The former is easier to forgive than the latter.

Original I.afdesign Exported I eps.eps

[Sean P]

Hi Genefreak,

Sorry you've encountered this issue. Unfortunately for technical reasons it isn't always possible to make files backwards compatible.

With regards to your issue, this has now been resolved in the 1.8.2 release and those objects will now export correctly.

Thanks for letting us know.

[Genefreak]

I appreciate that this glitch was fixed rapidly. And I DO understand that it is not always possible to make versions back-compatible. But there is absolutely not reason that you couldn't have done one of the following two things: 1) have the upgraded version of Designer automatically make a new copies of the file instead of overwriting; and/or 2) provide the user with a notification that the upgrade is not back compatible. Either of these very small steps would have prevented a great deal of difficulty for your customers.

I still love Affinity Designer, even with this experience. I'm giving a lecture to a dozen scientists tomorrow on how to use Affinity to make scientific figures. Hopefully the suggestions here will be considered for future upgrades.