big smile

@Pauls Please advise if you need me to supply any more info or material. Thanks! 🙂

@Pauls It seems hit and miss. Some pages will render fine. Others will not. I've made a video here. In the video, it's left on the same page for 20 seconds, but it doesn't render. At the end of the video, I include a clip of how the page should look. Prior to Affinity 1.10 this was never problem. You could have multiple Affinity Publisher documents imported into each other and they would all render perfectly.

@LeeThrope This seems to still be an issue in 2.0.3.1674 (macOS). The files no longer bloat in size. But Publisher hangs and has to be force quit. If you can provide an updated drop box link, I can send the crash reports that are generated (The old Dropbox link you had has expired). Thanks!

@Pauls @Dan C Just so you know, this is still an issue in Affinity Publisher 2 Customer Beta 2.0.3.1674 (macOS).

Thanks, do you know if there any workarounds. I would like to be able to work with the file, so I can see if the beta has resolved any of my other issues?

Hi I have uploaded the file to drop box, together with the crash report. The file does actually open, but if you go to resource manager, then Affinity Publisher 2 (Beta 2.0.3.1674 (macOS)) crashes.

@Gabe This is still an issue in Affinity Publisher 2 Customer Beta 2.0.3.1674 (macOS). It also seems to happen with older files that were opened in Affinity Publisher 2 (non-beta) and saved as a Affinity Publisher 2 file., Do I need to raise a separate post in the beta forum? Also, is there a way, I can send a crash report to help with debugging. Thanks in advance for any help.

I 100% respect this and will not challenge it any way. However, negative feedback does stand out more. So I hope when reviewing the feedback, Serif will take into account those customers that are happy with pricing. I'd hate for Serif to make changes to appease those that are unhappy, and in the process alienate those who were happy with how the pricing was handled.

I think people are looking at pricing the wrong way. The 40% discount is super generous, more generous than a lot of upgrade pricing from other companies. They didn’t have a way to make it available to only V1 customers, so they made it available to everyone. So what's the problem? Everybody wins! And for those who recently purchased V1. Yes, that does sting. But it takes 5 seconds of searching to see that Serif always give their best prices in their November event. They have done this for the last 5 years. And 5 seconds of searching shows that there hasn't been any new beta for over a year, which is a good sign that a new version was coming. So if getting a good price was important, then it doesn't seem wise to buy until November, which is when V2 became available.

About sharing crash reports on MacOs: If you go to system preferences to enable it, then do you have to select any options in Publisher? Just double-checking, to make sure I have done it right. As I get a lot of crashing, and I am not even using an M1 Mac! (My crashing also sometimes corrupts files!)

I do sympathise with such customers. Because like I said have been caught out in the past, and it's not a pleasant experience. So I feel the pain. But at the same time, I don’t think Serif can be expected to address it, especially when the upgraded pricing is so good. They give a refund for purchases made in 30 days. A cut off has to be drawn somewhere. Could Serif have sign posted things better by saying development on V1 was over back in Jan? Sure. But that could have opened a can of worms with people either panicking the product is dead or feeling entitled to have a firm date for a new release. Plus, it's always a good idea for people to do research before buying. The last time a beta came out was a long time ago (I think November 2021). That was a pretty big sign that V1 wasn't going to be updated any more. Also, Serif always do their best prices during their November specials. This is consistent: It's been like that every year since 2018. So again, customers wanting the best prices should have waited for November. They also do price events at other times. The last one was May 2022. So customers who bought during then would have got 6 months of V1 use at a discounted price. So yeah, I do have an incredible amount of sympathy for people in this position. But I think it's just a case of "that's life" (especially because waiting for the yearly November event which happens like clockwork could have avoided the situation) I think the generous upgrade pricing makes up for it. If the upgrade pricing wasn't so generous, then the case would be stronger.

Just saw the post by Ash on Affinity V2, updates, pricing and no subscription. And I think this topic is probably to best to comment on it. I think Serif have handled upgrade pricing perfectly. The universal license is an insanely good deal as are the other pricing options. I can't see why people are complaining. A lot of companies (e.g. SkyTV, insurance, etc) only give their best prices to new customers. Serif are treating both old and new the same. No one loses out. I do feel for people who recently purchased V1. Things like this have happened to me in the past with other companies, and I still feel the sting of it. But, it's life. It happens. It is not a problem Serif needs to fix, especially, as the upgrade pricing for V2 is more than reasonable. In my view, there really is no need to give bonus content as a thank you to V1 customers. And zero need to support the V1 software with updates when MacOS breaks it. Both of these are only taking away precious development time from V2. It's wholly unnecessary and I would have preferred they hadn't done this and just put all their efforts on V2. Are Serif perfect? No. I think they should have done a public beta for V2, as it's got too many bugs. I am sure these problems will be fixed. But it's annoying for launch software to be this buggy, especially as there is no way to downgrade a file from V2 to V1. But on pricing, I think they've been more than fair. Software development is not free. They have offered a cracking deal for the upgrade. They should not be expected to do anything more. I just felt I needed to share my views on this, as I'd hate for Serif to feel the need to please everyone, fail at it and then feel there is no choice but to switch to subscription. Like I said, I am sympathetic to people who feel differently about the upgrade pricing, but again, software development is not free. It needs to be paid for. Serif have been more than fair in this respect. They should be celebrated with their approach.

@LeeThorpe Thanks! I had another occurance. A file went from 6.5MB to 356.5MB!! As before no changes were made. It was simply opened in Publisher 2 and that caused it to swell in size. The new file is virtually unusable as it causes the application to hang. I have uploaded it together with the crash reports. The original 6.5MB file is called "00fun-arithmetic-INSIDE-text--v1". The new V2 356.5MB file is called "00fun-arithmetic-INSIDE-text--v2". I hope it's okay to keep on uploading these. If you've got too many let me know and I will stop. Thank you also for taking the time to look at this. I appreciate it. Thanks again!

@LeeThorpe I've got another instance of this. I opened a file that was only 3.3 MB. But then Publisher crashed. And the file went from 3.3MB to 81.3 MB! And again, this new bigger file seems to be corrupt, as although it will open it will keep on crashing publisher ever time I try to export it to PDF or make other edits. In the dropbox link, I've again uploaded the original file (It is titled "00fun-LongMath-INSIDE-text--V1") and the new corrupt version ("00fun-LongMath-INSIDE-text--V2), plus all the crash logs that occurred during the crash. If you need any other details, please ask. Thanks!

Here is nomi02118's original post incase the admins are looking for it:

@LeeThorpe It occurred again. Publisher crashed. And then the file that was open went from 11MB to over 50MB! The file also seems to be corrupt, as although it will open it will keep on crashing publisher ever time I try to export it to PDF or make other edits. To the dropbox link, I've uploaded the original file and the new corrupt version, plus all the crash logs that occurred during the crash (they are in Apple MacOS format, I am not sure if you need them in a different format). Please advise if you need anything else. Thanks!

Hi @Pauls I have uploaded the file. If you open the "child file" you can see the "parent file" (that is placed into the "child file") doesn't display properly: Many of the placed pages are either blank or incomplete. I have included a PDF which shows how the "child file" should look. As noted, there isn't any consistency to when placed files are displayed as blank pages. So if it opens fine, maybe try it again later on and see if it is still the case.

Hi when I click the link you have given, it says "This file request has been closed or deleted." I have tried on different browsers.

@Pauls @Dan C This is still an issue in Affinity Publisher V2. I have created a new thread for it here: https://forum.affinity.serif.com/index.php?/topic/172281-linked-publisher-documents-get-displayed-as-blank-pages/

I frequently import one Publisher Document into another. It's super handy when you have content reused between several Publisher documents. Since the release of Affinity Publisher 1.10, these linked documents sometimes get displayed as blank pages. There doesn't seem to be any consistency to when this happens. This issue was reported for Publisher 1.10 and was tagged with the codeafb-4980 It still seems to be an issue in Publisher 2.0. Even documents wholly created in Publisher 2.0 have the problem. In Publisher 2.0, if you click the blank page, then 80% of the time, it will appear. But obviously this isn't ideal. The problem did not occur in any version of Publisher prior to 2.0. If you still need an example document, please provide the dropbox link for this issue.

Hi Some of the file are too big, but I've uploaded all the resources for one the submited Afpub files. Thanks for your help.

I have added the files. For those files, the workaround doesn't work either.

Thanks, in the end from how I read Lee's post, I thought purchasing from the App Store would be the safest, so that's what I went with.

@LeeThorpe Hi I tried the safe settings, but same problem. Falling behind on work, I went for the nuclear option: I reinstalled MacOS and then Publisher. As before it worked fine, but then after a few hours it started crashing again. This time, I used AppCleaner to delete all the Publisher files in the MacOS library. That seems to work but then again after a few hours the crashing returns. I notice that when it crashes, it sometimes corrupts files. On the dropbox link, I have put a 34.5 MB Publisher file (titled Fun-Arithmetic-COVERS). It was originally a 7.8 MB file in Publisher V1, but every time I open it in V2 it balloons it up to 30MB+, even when I don’t make any changes. The version I have uploaded is a corrupt V2 version as it will no longer open. To this post, I have attached all the crash reports that are generated by MacOS each time Publisher crashes. I would be grateful if you could look into the matter. I was really excited to get Publisher 2. But now it feels a bit like playing a game of chance where you don’t know if it will crash and your work will be corrupted! Thanks for all your help so far, and thanks in advance that this problem can be fixed. Affinity Publisher 2-2022-11-12-161104.ips Affinity Publisher 2-2022-11-12-161128.ips Affinity Publisher 2-2022-11-12-184936.ips Affinity Publisher 2-2022-11-13-161314.ips Affinity Publisher 2-2022-11-13-163444.ips Affinity Publisher 2-2022-11-13-164231.ips Affinity Publisher 2-2022-11-13-164450.ips Affinity Publisher 2-2022-11-13-164616.ips Affinity Publisher 2-2022-11-13-164730.ips Affinity Publisher 2-2022-11-13-182354.ips

I don’t think linked files are the issue, as I created a brand new file in V2 that had no linked images. I shall try experimenting with the hardware acceleration first. Do you know which are the safest settings to start with? Maybe I can start with the safest settings first and then expand to isolate the issue.