TOC crash when turning off Include As PDF Bookmarks with multiple TOCs

[MikeTO]

I've attached a 2.1.1 test document that crashes in 2.2 beta 1986 when I click into either of the two TOCs at the top of the page and turn off Include as PDF Bookmark. Doing the same thing doesn't crash in 2.1.1.

toc test 3.afpub

Affinity Publisher 2 Beta-2023-09-06-135010.ips

 

If I deselect Heading 1 in the TOC panel's style list for TOC 2 before clicking Include as PDF Bookmark it won't crash. It does in my real document and I'm still trying to figure out why it only crashes in that one.

The reason I want to turn off Include as PDF Bookmark for the secondary TOCs is that if TOC 2 has Heading 1 turned off, then Heading 2's PDF bookmark won't be nested under Heading 1. So any book with multiple TOCs needs to turn this off or it will break the PDF bookmark hierarchy.

Edited September 6, 2023 by MikeTO
Attached the wrong crash report the first time

[MikeTO]

There is a workaround for those who encounter the same bug but it will require work if you've used your TOC anchors as cross-reference targets.

1. Delete the main TOC.
2. Deselect Include as PDF bookmarks for all of your secondary TOCs.
3. Insert the main TOC again.
4. It will be badly formatted but your TOC style isn't gone so you just have to choose the TOC style again.
5. Now re-target every cross-reference that had targeted the TOC's anchors. This may take a while because you can't search for anchors or type the first letter to jump to them in the edit cross-reference dialog.

[MikeTO]

Also please see this other bug I reported - they might be symptoms of the same problem.

 

[Affinity Info Bot]

An issue raised in this thread ("TOC crash when turning off Include As PDF Bookmarks with multiple TOCs") has now been reported to the developers by the testing team (Ref: AFB-8308). Thank you very much for reporting this issue to us.

[Affinity Info Bot]

The issue "Crash after unchecking Include As PDF Bookmarks on a document with multiple headings in Table of Contents" (REF: AFB-8308) has been fixed by the developers in internal build "2.2.0.1999".
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.

[MikeTO]

Thanks! This works perfectly now.