Affinity Publisher 2.1.0.1714 on Windows crashes instantly when opening a book

[grabi678]

A book created with Publisher 2.0.4 worked fine with 2.1.0.1709. All the issues with 2.0.4 have disappeared. But opening the same book with 2.1.0.1714 is not possible. The application closes within a few seconds with no further information.

[MikeTO]

Hi @grabi678 and welcome to the forums.

Are you able to open this book with 2.0.4? Although that version has more bugs with editing books, it should be able to open a 2.1 beta book.

Also, try this:

1. Temporarily move the chapter files to another folder
2. Open the book - Publisher will ask you if you want to relink the chapters - decline this
3. Does the book open correctly now?
4. If so, close the book and open each chapter one by one - do they all open okay?

[walt.farrell]

16 minutes ago, MikeTO said:

it should be able to open a 2.1 beta book.

2.1 beta files are not compatible with 2.0, from what I've seen Mike. And I expect that to be true of 2.1 retail, too. 

2.1 -> 2.0 is like 1.9 -> 1.8 or 1.8 -> 1.7, etc. Doesn't work.

[MikeTO]

11 minutes ago, walt.farrell said:

2.1 beta files are not compatible with 2.0, from what I've seen Mike. And I expect that to be true of 2.1 retail, too. 

2.1 -> 2.0 is like 1.9 -> 1.8 or 1.8 -> 1.7, etc. Doesn't work.

You're right, my mistake

[grabi678]

I tried to figure this out. I created a new book with 1714 and added the chapters of my previous book one by one. Two of the 13 chapters could not be added to the book. By doing this the app crashed instantly. Although the afpub files of these chapters could be opened with 1714 without any problem. Then I tried to add these chapters whilst the afpub files were opened in 1714. This was at first sight successful but the app crashed when I tried to open a chapter within the book after saving. These two chapters don't seem to be compatible with the book function of 1714 (they are with 2.0.4 and the previous beta version!) but there is no hint what could be wrong.

[MikeTO]

9 hours ago, grabi678 said:

I tried to figure this out. I created a new book with 1714 and added the chapters of my previous book one by one. Two of the 13 chapters could not be added to the book. By doing this the app crashed instantly. Although the afpub files of these chapters could be opened with 1714 without any problem. Then I tried to add these chapters whilst the afpub files were opened in 1714. This was at first sight successful but the app crashed when I tried to open a chapter within the book after saving. These two chapters don't seem to be compatible with the book function of 1714 (they are with 2.0.4 and the previous beta version!) but there is no hint what could be wrong.

Try opening those two chapters on their own and using Save As to new files. Then add the new files to the book. I don't know if this will work but it's worth a try.

[Sean P]

Hi grabi678

Would you be able to zip up and attach the offending AFPub and AFbook files please?

[grabi678]

On 3/9/2023 at 12:07 PM, Sean P said:

Hi grabi678

Would you be able to zip up and attach the offending AFPub and AFbook files please?

Here are the files.

Test.zip

[Sean P]

Thank you very much for the files. 

I can replicate the crash here and will get it logged. 

[grabi678]

On 3/13/2023 at 1:17 PM, Sean P said:

Thank you very much for the files. 

I can replicate the crash here and will get it logged. 

This isn't fixed with beta 1730, is it?

[Patrick Connor]

18 minutes ago, grabi678 said:

This isn't fixed with beta 1730, is it?

No but we are internally testing a fix for this in an internal beta build 2.1.0.1732. That new beta should be released as a patch/update tomorrow. 

[grabi678]

With 1732 the two faulty chapters could be added to the book.

But working with books and chapters is still (or again?) very buggy. A chapter can be opened but it is not possible to select any text. Sometimes the book can be saved but mostly not. So the application can't be closed. I'm still not able to test cross references within the book.

[Affinity Info Bot]

The issue "Attached documents cause app to crash when added as a Book Chapter" (REF: AFB-7490) has been fixed by the developers in internal build "2.1.0.1732".
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.

[grabi678]

On 3/24/2023 at 2:07 PM, Serif Info Bot said:

The issue "Attached documents cause app to crash when added as a Book Chapter" (REF: AFB-7490) has been fixed by the developers in internal build "2.1.0.1732".
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.

Although most issues with the book feature seems to be solved with Beta 1742 I have to report that the same issue as described in AFB-7490 occurred again. Publisher crashes instantly when adding the same two chapters to the same book. I think the already uploaded files can be used for testing.

[Sean P]

On 4/8/2023 at 4:10 PM, grabi678 said:

Although most issues with the book feature seems to be solved with Beta 1742 I have to report that the same issue as described in AFB-7490 occurred again. Publisher crashes instantly when adding the same two chapters to the same book. I think the already uploaded files can be used for testing.

Hi grabi678,

I can indeed make this crash again! Thanks for letting us know. I've reopened that issue!

[Affinity Info Bot]

The issue "Attached documents cause app to crash when added as a Book Chapter" (REF: AFB-7490) has been fixed by the developers in internal build "2.1.0.1769".
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.