Please Read if you are Experiencing the PDF Export Bug in Version 2.5.6

[Hangman]

A small regression was introduced in the new 2.5.6 update, also affecting the current 2.6.0.2900 Beta across all three apps. Under certain circumstances, PDF files fail to export, instead displaying the following error message...

This impacts both Mac and Windows when exporting files containing RGB JPG and PNG files when using the following PDF Presets if Embed Profiles is unchecked, which it is by default when using PDF (digital high-quality):

• PDF (for print)
• PDF (press ready)
• PDF (digital high-quality)
• PDF (for export)

The current workaround for the bug is to check Embed Profiles in the PDF Export window, however, certain print workflows require no ICC Profile to be embedded in the exported PDF making this option unsuitable.

While waiting for this bug to be patched there are four additional workarounds for this scenario detailed below...

The Cause of the Bug
The bug appears to be caused when placing images that don't contain an embedded ICC Profile if the Placed DPI for the image is below 375 dpi but only if the Placed image is contained within the document page bounds...

Exporting to PDF with Enable Profiles Unchecked

Workaround 1
Ensure your Placed image contains an embedded ICC Profile...

Workaround 2
Swap any PNG or JPEG files for TIFF, PSD or .afphoto versions...

Workaround 3
Ensure the respective Placed DPI for any image files is a minimum of 375 dpi. This may mean adjusting the export settings for the source image (where possible) to ensure that once placed and resized the image's Placed DPI is 375 dpi or greater...

Workaround 4
Enlarge full-page images slightly so they exceed the document page bounds...

Workarounds 1, 3 and 4 when Checking Embed Profiles is Not an Option

[Latens]

Too bad that a forum member should create such a post @Patrick Connor

[Hangman]

@Return,

To be honest, it's taken a lot of testing and trial and error to figure out what on earth was causing this so I'm unsure that is fair feedback. I expect the findings above have already been determined internally by the development team and that we'll see a patch released very quickly due to the seriousness of the bug...

The post was just to try and help anyone who finds themselves in a similar quandary with an urgent deadline...

[Latens]

Grateful that you posted workarounds but this isn't about you but the lack of responsibility by Serif.

And although they may be working on a patch it is very unprofessional to say the least.

[Patrick Connor]

Thanks @Hangman despite what @Return said your post is exactly what these forums are for, the reporting of problems and some innovative ways to avoid it will be appreciated by many and likely linked to by staff helping customers till a patch appears.

I'm incredibly grateful for your comprehensive explanation of some workarounds given the regression, that I agree should not have happened and for which we are very sorry.

56 minutes ago, Return said:

Grateful that you posted workarounds but this isn't about you but the lack of responsibility by Serif.

How do you judge that Serif are not taking responsibility for this? This post is worthy of one of our FAQs, but to imply we would not make one ourselves is simply false.

[Latens]

Question remains why didn't you post a faq?

Seems the truth annoys, now doesn't it?

[duvid]

Hi! I have the same problem, but it can't be solved like this because there are no images in the document, all are curves or text. I've tried different ways to export to pdf and the only one that worked for me is rasterizing everything (ironic). I'm on the beta version because I made the fatal mistake of opening the afbook in the beta (2.6.0.2900).

I've tried embedding and not embedding and it doesn't work.

[Hangman]

Hi @duvid and welcome to the forums,

Do you have Tagged PDF selected in the Advanced section of the PDF Export Window?

If you do, does unchecking it allow you to export your file?

If it’s not checked or if unchecking it makes no difference could you zip your .afbook file and .afpub chapters along with any linked files and upload the zip file so we can take a look as it’s likely something in the file itself causing the problem not related to this specific issue…

[Patrick Connor]

1 hour ago, Return said:

Question remains why didn't you post a faq?

Because no doubt it has taken Hangman hours to get this detailed information and over the weekend he has got ahead of our processes to get one written and published.

1 hour ago, Return said:

Seems the truth annoys, now doesn't it?

No, nothing so childish 

[StuartRc]

@Hangman
Thank you so much for presenting the solutions to your investigations.....with regards to the PDF Export issue.. Much appreciated and well presented...keep it up!

[duvid]

5 minutes ago, Hangman said:

Hi @duvid and welcome to the forums,

Do you have Tagged PDF selected in the Advanced section of the PDF Export Window?

If you do, does unchecking it allow you to export your file?

If it’s not checked or if unchecking it makes no difference could you zip your .afbook file and .afpub chapters along with any linked files and upload the zip file so we can take a look as it’s likely something in the file itself causing the problem not related to this specific issue…

It works!

Thank you so much, truly. It seems some people don't know how to appreciate the time others invest in them selflessly.

[Hangman]

Hi @duvid,

That’s really good to hear, I’m glad everything is working again for you and that you can export your file successfully, many thanks for letting us know… 🙂

[Latens]

22 minutes ago, Patrick Connor said:

Because no doubt it has taken Hangman hours to get this detailed information and over the weekend he has got ahead of our processes to get one written and published.

No, nothing so childish 

Your reaction speaks loads.
You could have acknowledged the f***up and wrote a faq about the issue and made it sticky and also put it in the release notes topic, which many users are missing for every update.
Don't take it personally, it's your job as head of Q&A to provide this info and I hope this time you can get a patch out sooner as to the non-subject of thumbnails in sequoia.

[Evaluation complete.]

I did not feel any closer to being in safe hands from this thread. 

[bbrother]

Hangman great job. I can imagine how much time it took to trial and error.
Thanks for the hard work you did providing workarounds. It saved me a lot of trouble.

Your processes suck if first you don't catch bugs like this before release and then the user gets ahead of you and provides information and a workaround before you do. For God's sake, @Patrick Connor what the hell are you and your team for.

[Affinity Info Bot]

The issue "Export to PDF fails if using High Quality preset without embed ICC profile ticked" (REF: AF-5175) has been fixed by the developers in 2.5.7 Release.
If you still experience this problem once you are using that version (or later) please reply to this thread including @Affinity Info Bot to notify us.