Jump to content
THESE FORUMS ARE READ-ONLY: Please Read Me ×

Recommended Posts

Posted

I encountered a repeatable crash when trying to open two Books with the same filename but stored in different directories. They were versions of the same Book but it's easy to repeat this with a blank Book. This isn't really that obscure of bug, I often open older versions of my documents to compare them and that's what I tried to do with this Book.

  1. Create a Book and choose Save Book from the panel menu, there's no need to add chapters for this test
  2. Choose Save Book As and save it somewhere else under the same filename
  3. Choose Open Book and open the first one you saved. It will result in this repeatable crash.

Affinity Publisher 2 Beta-2023-09-01-202312.ips

Posted

Just a comment: If you did have chapters in the book, that could be a dangerous operation as changes to either book would affect the same chapter files, and you might end up with a real mess.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop 1:  Windows 11 Pro 24H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 26.0, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.6.1

Posted
1 hour ago, walt.farrell said:

Just a comment: If you did have chapters in the book, that could be a dangerous operation as changes to either book would affect the same chapter files, and you might end up with a real mess.

That would be dangerous but each book had its own chapters. I had the book in a folder and to make backups I duplicated the entire folder.

Posted
14 minutes ago, MikeTO said:

That would be dangerous but each book had its own chapters. I had the book in a folder and to make backups I duplicated the entire folder.

But, can you be sure that the duplicated Book file wasn't still using the original chapter files?

I would hope that if the .afbook and .afpub files were in the same directory then relative paths, not absolute, would be used. But I have not (yet) verified that.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop 1:  Windows 11 Pro 24H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 26.0, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.6.1

Posted
51 minutes ago, walt.farrell said:

But, can you be sure that the duplicated Book file wasn't still using the original chapter files?

I would hope that if the .afbook and .afpub files were in the same directory then relative paths, not absolute, would be used. But I have not (yet) verified that.

Fair point

  • 1 month later...
  • Staff
Posted

The issue "[macOS] Opening two .afbook files stored in different directories but with the same file name causes an app crash" (REF: AF-44) has been fixed by the developers in internal build "2.3.0.2083".
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.

×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.