Publisher 2.04 crashes when I will print

[lexmark]

Affinity Publisher 2.04 crashes when I will print out of Publisher. I already deinstalled the printer Brother DCP-7055, but the same problem.  I use Windows 10 64bit.

I enclose a crash report which shows System.NullReferenceException.

My book is nearly ready and then this.

Lexmark

Crash-Report.docx

[Dan C]

Hi @lexmark,

Thanks for your report!

Unfortunately I'm going to require the full .DMP crash files in order to investigate this further - can you please follow the instructions here and attach a copy of the .DMP files directly?

In the meantime, I would recommend using File > Export and exporting your document to PDF and then printing this externally, rather than though the Affinity app.

I hope this helps

[lexmark]

Hi Da C,

enslosed I send you the dmp-file. Hope you can use it.

Thank you for your help.

 

Lexmark

cc8afd17-3e1e-4986-b612-f21b2ee6e3b7-dump.dmp

[Dan C]

Many thanks for providing that for me and my apologies for the delayed response here!

I have debugged this crash report and it shows that the Affinity app is crashing when attempting to use your Printer driver - but as I don't have the source code for said driver this is all the information I am provided from this.

I note you mention you have already reinstalled the printer through Windows, did this include installing the printer using a new copy of the latest drivers, directly from the manufactures website?

If not, I'd recommend uninstalling the printer and then reinstalling it with a new copy of these latest drivers to try and resolve this issue.

I hope this helps

[lexmark]

Hi Dan,

thank you for your reply. Yes I really deinstalled and reinstalled the printer. After deinstalling I tried to print without any printer installed but  Affinity app was crashing when I push the print button in Affinity.

Latest copy of drivers already installed from manufacturers website now. Problem is still there.

Another idea?

Thank you

Lexmark

 

 

 

[Dan C]

Thanks for trying that for me and I'm sorry to hear this - does this happen if you try printing a different document?
For example a new, blank file - or one of the Samples you can download through the New Document dialog?

[lexmark]

Hmm. I download the cookbook and I could print it. Then I tried to print my book but affinity crashes.

Affinity is running under Windows 10 on my PC. The files for my project are saved in One Cloud from Microsoft and not on my PC. Is it possible that here is the reason for my problems?

But the printing problem ist new for me. Two weeks ago I could print out of Affinity. 

[Dan C]

Many thanks for confirming that for me!

50 minutes ago, lexmark said:

The files for my project are saved in One Cloud from Microsoft and not on my PC. Is it possible that here is the reason for my problems?

It's certainly possible as we recommend loading and saving files from a local location, rather than a cloud synced folder. If you create a copy of your .afpub file in a local folder (such as your desktop) are you able to print this file as expected?

[lexmark]

Unfortunately it crashes too.

In my project I have linked a large number of photos, these photos are also in a cloud synced folder. I assume that I have to copy the .afpub file and the photos to a local folder. Furthermore I assume I have to refresh the links to the photos in the local folder?

 

[lexmark]

I saved a copy local under new name. I deleted all photos in this project. Saved under new name. Closed affinity and started again. Chose now the new file without photos. I will print and affinity crashes again. 🥵

[Dan C]

My apologies for the delayed response and thank you for trying that for me - I'm certainly sorry to hear this is still crashing.

I'd like to request a copy of your document so I can investigate this further, I shouldn't require a copy of your linked files at this time if any remain in your document, simply a copy of the .afpub file should be enough for my preliminary testing.

Can you please upload a copy of this .afpub file to the below link for me?

https://www.dropbox.com/request/tVriqufcOBPSjQtPZGNF

Once uploaded, please reply here to let me know

[lexmark]

Hi Dan,

I uploaded the .afpub-file "Silberhochzeit in Amerika"

 

[Dan C]

Many thanks for providing that for me!

I can confirm I'm able to replicate this crash here - even if I delete all but the first page in the file. Interestingly if I load this file in the latest 2.1 beta version, I'm able to open File > Print without the app crashing, however the Print Preview only shows 1 page eligible for printing.

I'm not 100% certain of the cause of this currently and therefore I will be logging the document with our team for further investigation.

In the meantime, I have recreated the document in a new file, which appears to allow me to use File > Print as expected in 2.0.4, without the app crashing.

I'll be returning this file via Dropbox now, to the email address associated with your Forum account. I'd recommend checking through this document carefully before proceeding to ensure no data has been lost.

I hope this helps

[lexmark]

Hi Dan,

I thank you very much for kind assistance.

I downloaded the file and I will check the content. I will revert as soon as possible.

Furthermore I found an additional problem. When I try to export the file in PDF. See File "export1" and when I click "inklusive Anschnittbereiche"  then "Vorgabe" will be empty. See file "export2". When I push on "export" affinity ask where will I save the file. After confirming nothing happen!

When I do the same and mention side 1 - 255 the document will be converted in PDF.

 

[Dan C]

No problem at all!

19 hours ago, lexmark said:

Furthermore I found an additional problem. When I try to export the file in PDF. See File "export1" and when I click "inklusive Anschnittbereiche"  then "Vorgabe" will be empty. See file "export2". When I push on "export" affinity ask where will I save the file. After confirming nothing happen!

When I do the same and mention side 1 - 255 the document will be converted in PDF.

Thanks for letting me know - I'm seeing the same behaviour here and I will be sure to update the development log with this information now. I suspect the same issue that is failing to print the document is also failing to export the file to PDF.

I've tested this with the repaired document however and this appears to export to PDF as expected

[lexmark]

Hi Dan,

sorry for the delay.

I checked the file and now seems all is okay. I can print without crash and export in PDF is possible now. Only after clicking "inklusive Anschnittbereiche" the field "Vorgabe" will be cleared. That is not correct, but this problem is not so important for me.

In the meantime I go further with my project, is it possible for me to change my actual working-document in the same manner as you did? Make it sense for me to use the beta-version or can you give me a work-around for my problems.

However I thank you very much for exceptional assistance.

Lexmark 

 

[Dan C]

On 4/15/2023 at 4:55 PM, lexmark said:

I checked the file and now seems all is okay. I can print without crash and export in PDF is possible now

That's wonderful news, many thanks for letting me know!

On 4/15/2023 at 4:55 PM, lexmark said:

Only after clicking "inklusive Anschnittbereiche" the field "Vorgabe" will be cleared. That is not correct, but this problem is not so important for me.

I can confirm this is expected behaviour - the 'Vorgabe' (Preset) menu allows you to select a predetermined set of export options for different formats - once you change the preset options, such as enabling 'inklusive Anschnittbereiche', the preset is no longer active and therefore is not shown in the 'Vorgabe' field.

On 4/15/2023 at 4:55 PM, lexmark said:

In the meantime I go further with my project, is it possible for me to change my actual working-document in the same manner as you did? Make it sense for me to use the beta-version or can you give me a work-around for my problems.

You shouldn't need to use the beta to recover this file, but you are welcome to do this in either 2.0.4 or 2.1, whichever you prefer.

To recover your document, I did the following:

1. Create a new, 1 Page long file in Publisher, using exactly the same document settings (page size, colour profile, margins, bleed etc) as the document you are repairing.
2. In the Pages Studio, right-click on Page 1 and select Add new pages from file in the menu shown.
3. In the dialog that opens, select the .afpub file that cannot be printed/exported
4. In the following dialog, ensure that 'All Pages' is enabled and change the 'Add Pages' option to 'Replacing' -
   
    
5. Click OK and your document will be added to the new file, at which point you can use File > Save As to save as a new document, and File > Print/Export as required.

I hope this helps  

[Dan C]

Hi @lexmark,

I wanted to update you with the findings from our developers - your document contained 1 section which had 'Include on Export' disabled, which was causing the crash in the print dialog and the reason no file was generated when exporting.

This is why recreating the document in a new file resolved the issue, as the Section was no longer set to be excluded. 

Our team are implementing a fix to stop this from causing the app to crash when opening the print dialog and are looking at adding a Preflight check to inform the user if no pages are set to export, such that this is clearer in the future.

I hope this clears things up!

[lexmark]

Hi Dan,

great job! I thank you very much for this information. You found the reason for the crashes. When I "include on export" all ist fine and I can print and export as pdf.

And when I didn't want to export the sections?

But the main problem has solved. I thank you very much for your kind assistance and prompt attention.

Best regards.

 

 

[Affinity Info Bot]

The issue "User file - Crash on File > Print" (REF: AFB-7632) has been fixed by the developers in internal build "2.1.0.1781".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.

[Duncan W]

Hi all,

I am running a trial of 2.1.1 and Publisher crashes without warning or any messages when I try to Print or Export from the Book menu. I tried the solution to "Include on Export" but it was already set.

However, I did find the solution, hence why I am adding this post.

The problem was that I didn't have a Style Source Chapter set. I set one of my chapters to be the Style Source Chapter and now it brings up the Book Export and Print dialogs without an issue.

This is probably something that should be fixed. It is only by chance that I figured it out. Maybe Preflight should look to see if there is a Style Source Chapter.

[Dan C]

Hi @Duncan W,

Welcome to the Affinity Forums

Many thanks for letting us know - technically it should not be possible to create a Book with no Style Source Chapter set, as when removing a Chapter that is set as the Source Style, the next Chapter in the Book will automatically adopt this setting.

However I have found that when replacing a Chapter that is set as the Style Source, this creates a Book state whereby no Chapter is set as the Style Source, which subsequently crashes the app when exporting/printing.

As you've mentioned, this certainly isn't expected behaviour and therefore I'm getting this logged as a bug with our development team now.

I hope this helps!

[Affinity Info Bot]

The issue "Replacing Style Source Chapter in Book results in Book without a Style Source Chapter - app crashes when exporting/printing file" (REF: AF-223) has been fixed by the developers in internal build "2.3.0.2083".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.