Publisher Crashes Attempting to Change the Image Policy When Placing Affinity Designer Files [1971]

[Hangman]

When placing an Affinity Designer file into Publisher 2.2.0 (1971) agreeing to a change of Image Policy instantly crashes Publisher. This happens reliably when placing multiple Designer files from both the 2.1.1 retail version and the 2.2.0 (1971) beta version into Publisher 2.2.0 (1971).

Steps to Reproduce

1. Create a New Publisher Document
2. Set the Image Placement Policy to Prefer Embedded
3. Place an Affinity Designer file, sufficient in size to invoke Publisher's Image Policy dialog
4. Click 'Yes' to change the Image Placement Policy from Emdedded to Linked
5. Publisher crashes

A crash report is attached below...

Affinity Publisher 2 Beta-2023-08-26-140956.ips

Placing the same v2.1.1 Affinity Designer File into Publisher 2.1.1 and 2.2.0 (1971)

[MikeTO]

I just experienced this crash with 1971. I'm getting it with TIFF images so it's probably for any type of resource. Here's a crash report.

Affinity Publisher 2 Beta-2023-08-26-220256.ips

[Hangman]

Hi @MikeTO,

Thanks for testing and confirming…

[Gabe]

Thanks. We are aware of this issue. 

[Hangman]

Hi @Gabe,

Just to clarify, this is different to the known issue, which interestingly I can't replicate...

Quote

Known Issues: Crash on replacing embedded or linked images [AFB-8244] has been introduced in this build, but will be fixed in the next beta

Are both issues logged or are they considered part of the same bug, despite this one technically having nothing to do with physically replacing missing images via Resource Manager?

[Gabe]

It's part of the same bug. It still calls the same backend to "replace" that resource with the linked equivalent. 

[Hangman]

Hi @Gabe, Perfect, thanks for clarifying...

[Affinity Info Bot]

An issue raised in this thread ("Publisher Crashes Attempting to Change the Image Policy When Placing Affinity Designer Files [1971]") has now been reported to the developers by the testing team (Ref: AFB-8255). Thank you very much for reporting this issue to us.