HRef

Thanks! I'd love to know what is causing it so I can stop doing it. For me it has been consistent when trying to add single page into my facing spread document. Probably likely that it is something else in the document that then corrupts due to being shifted only one page... but what that is I have no idea. As a workaround I have resorted to adding 2 pages (full spread) and then manually shifting content as needed, which isn't exactly ideal... but it doesn't cause crashing.

This file was created using the latest Affinity Publisher on MacOS 10.14.6, so this would not fall under previous versions errors.

I will add this however, I again had another perfectly working file opened in Affinity Publisher as I opened the broken file I uploaded. When I tested to save the broken file, as expected publisher crashed. However, the other functional file I had opened has now also started to behave strangely. Now this file as well appears to generate random publisher crashes, even though it can be saved. So whatever is happening when save crashes, basically ruins all open files in publisher not just the one that is broken. This behavior is making me extremely nervous as to the stability of this product.

Done. Though the file just seem completely broken now. I went back to a previous version and started redoing my work, but without adding single pages and that has been working since.

I am encountering an issue where the saving crashes publisher, and then any further attempts at opening the file and saving will always result in a crash. Something invisible has been added that corrupts the file and prevents saving. I'm positive it is related to adding single pages in the middle of a facing spread document. It doesn't always crash right way, I have been able to work and save the project for some hours, then suddenly save crashes and the document can no longer be saved at all. Reopening and saving causes crash. The particular change when the crash happens has no pattern. Going back to a previous copy of the file, where saving was possible, and just opening that document and saving suddenly causes a crash as well - indicating the issue was present for quite some time but then randomly and suddenly causes the save crash. If I go back to a previous version of the document file where single pages have not been inserted, saving works again. I can work in the document, add 2 page spreads, etc. No isssues, no crashes. I can even do the change the previously was done right before the crash happened with no issues, with the only difference that I have not added any single pages. Then again I try to add a single page, it doesn't crash right away and does allow for saving.. but a couple of hours later, crash. And there is no rhyme or reason as it crashes with sometimes no change at all, sometimes changing pararaph style on page 10, or typing a word on page 100. The only thing consistent is adding that single page into the facing spread document at some point. This seems to cause instability in the file/program and it is only a matter of time before crashing will occur on save. I have a file where the behavior is 100% reproducible. I can open the file and do a Save As and it works. But any change to the document and saving beyond that causes a crash (Literally any type of change it doesn't matter what is done to it). I can share the file with a developer, but due to the IP/copyrighted unpublished material not attach it publicly this post. Attaching the apple crash report. I started to experiment to try and understand what I did that caused the crash, and it keeps coming back to the same thing. Start from the functional document, make a bunch of changes. No crash. Start from the functional document, add a single page in the middle, start making the same changes as above, eventually save crashes. Start from the functional document, make a bunch of changes. No crash. Add single page in the middle, make some more changes, eventually but certainly a crash happens. Start from the functional document, make a bunch of changes. No crash. Do not add the single page. Replicate the same changes as previously. No crashing happens at all. applecrashreport.rtf

Thanks, yeah I'll post over there.

I now have it 100% reproducible from my file as well. From the state the file is in, I can open the file and save as without changing anything, and it will work. But change anything, anything at all, and then do a save and it crashes and then the file is in a non-working state again. It doesn't matter if I change a paragraph style on page 10 or add a text character on page 100, it still triggers the crash. If I change nothing, the document saves. edit: it is absolutely related to adding 1 single page into a facing spread document. It may not crash right away, but that seems to be a ticking clock just waiting to trigger crashes down the road. I went back through my backup files, and even though I had taken a backup of a file when and where save was previously possible, suddenly it started crashing as well without changing anything. I went further back in the backup files until I got before I added the 1 single page, and suddenly it works fine. I added a couple of 2 page spreads, and no problem. Continued to work in that document, and no crashes down the line. Adding single pages in the middle of facing spread documents seems to cause complete instability in the file and software.

I'm experiencing the same issue as the initial poster, the exact same behavior and so I suspect there is some hidden corrupt elements in my afpub file as well. I have also noticed another alarming issue when the save fails, it also corrupts all other files you have open in Affinity Publisher. I had another perfectly fine file open as well when the crash happened, and now that file as well can't be saved and exhibits the same behavior. It seems to be related to add 1 page in a facing spreads document, that's at least when my woes started (and I do have pinned objects here and there). Is there anyone from development that can help me to look at my afpub file? Since it is som IP/copyrighted as yet unpublished material I'd rather not share the file openly on the forum. I did attach my apple crash report though. applecrashreport.rtf