Crash when dragging part of symbol out of two instances of the samesymbol

[bedalton]

1. Are you using the latest release version?
   Yes.
2. Can you reproduce it?
   Yes.
3. Does it happen for a new document? If not do you have a document you can share that shows the problem?
   Yes
4.  What is your operating system and version (Windows 10, OSX Mojave, iOS 12 etc)?
   High Sierra 10.13.6
5. What happened for you (and what you expected to happen)
   The program crashes (closes without saving), and a little while later a typical macOS crash dialog pops up.
   I expected a copy of a part of symbol to be pulled out of each instance of the symbol
6. Provide a recipe for creating the problem (step-by-step what you did).
   1. Create a symbol with at least one item in it.
   2. Create two instances of the symbol in the document
   3. Expand both instances of a symbol
   4. Select the same item in each symbol using CMD+Left Click
   5. Drag the items out of the symbol and release mouse button
7. Screenshots (very handy) or a screen capture/video.
   Attached, but probably not useful
8. Any unusual hardware (like tablets or external monitors or drives that may affect things) or relevant other applications like font managers or display managers.
   None
9. Did this same thing used to work and if so have you changed anything recently? (software or hardware)
   This has never worked, but sometimes I forget when I have taken a symbol and mirrored it, and want to have the mirrored copies of the same item in each. It crashes with or without it mirrored.

[Sean P]

Hi @bedalton,

Thanks for letting us know and for the steps! I've reproduced that here and will get it passed on over to development.

[Affinity Info Bot]

The issue "Crash when dragging the contents of duplicate symbols outside of a symbol." (REF: AFD-5143) has been fixed by the developers in internal build "2.2.0.1925".
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.