Unpinning Inline Graphic After Converting to a Symbol Results in an Instant Publisher Crash

[Hangman]

Steps to reproduce

1. Create a text frame in a new Publisher document and add a few lines of text
2. Add an inline graphic to each line of text (in this instance SVG files)
3. Switch to the Designer Persona
4. Select the Text Frame and Create a Symbol, adding it to the Symbols palette
5. Immediately Delete the newly created Symbol from the Symbols palette
6. Switch to the Publisher Persona
7. Select any of the inline SVG files in the Layers panel and select Unpin from the Pinning Panel (or click the Inline in Text Icon)
8. Publisher instantly crashes
    

Screen Recording

Crash Reports

Affinity Publisher 2 Affinity Store-2024-01-02-133933.ipsAffinity Publisher 2 Affinity Store-2024-01-02-133158.ipsAffinity Publisher 2 Affinity Store-2024-01-02-132955.ips

 

Sample File

Note: The SVG Files will need to be re-linked owing to a known bug in v2.3.0 that prevents their embedded status from being honoured.

Inline Symbols.zip

 

[Dan C]

Thanks for your report @Hangman!

I can confirm I've been able to replicate this issue here, it appears to affect Windows also, and can be triggered using Pixel layers or Quick Shape objects, alongside your SVG files above.

Therefore, I'm getting this logged with the development team now - I hope this helps

[Hangman]

Hi @Dan C,

Thanks for the additional testing and for logging, much appreciated as always...

Could you confirm whether the issue with the SVG files not remaining embedded is already logged?

[Dan C]

No problem at all, you're very welcome!

9 minutes ago, Hangman said:

Could you confirm whether the issue with the SVG files not remaining embedded is already logged?

Absolutely, and if I'm not mistaken is already fixed in our internal 2.4 build:

(Ignore the 'PSD' only in the title, the issue fixed covers multiple file formats)

[Patrick Connor]

1 minute ago, Dan C said:

and if I'm not mistaken is already fixed in our internal 2.4 build:

and the fix for AF-1416 has been branched into the 2.3 codebase to be included in 2.3.1 beta that should be available tomorrow