Publisher 2.6.0 corruption running rampant!

[TChitwood]

Create File....... Save File....... Make 2 copies [locally]........ Close File.

Open File.... er, nope
[The document file is corrupted: SSD Pgm 2025.1 - The document file appears to be corrupted and must now be closed].

Close File....... Open File..... er, nope...... Close File..... Create New File.... Import Pages [one at a time] to see if there is something in the file which is creating the corruption. But it doesn't seem to be any one element or any one font. The only consistency is saving, closing, opening, [nope], new file, import, and repeat.

And so has been the past 10 hours - I have completed one page today due to this corruption issue. I have searched the forum and read every post which asks for a solution to this problem, but, alas, no solution has been offered - only the steps leading up to the problem.

My Info:
MacBookPro16,1
MacOS Sequoia 15.3.2 (24D81)
2.3 GHz 8-Core Intel Core i9
AMD Radeon Pro 5500M 4 GB
Intel UHD Graphics 630 1536 MB
16 GB 2667 MHz DDR4

Affinity Publisher v2 2.6.0

I have attached the ONLY viable copy of my file. [SSD Pgm 2025.1.afpub]

Here are the answers to the common questions asked:

No, I am not working on a server - ALL files are locally saved on the harddrive
Yes, I save often and to multiple folders
I have never used Publisher v1 - I just downloaded v2 last week and is the first time using Affinity anything. I thought if I packaged the file, then any elements, fonts etc. would be in a central folder and I shouldn't get any more errors.... bwahahaha, nope. [see image.png]

Tried packaging again after working for a while - and was denied. [see Screenshot 2025-04-01 at 7.41.45 PM + Screenshot 2025-04-01 at 7.41.33 PM] for all the reasons Publisher doesn't want to work.]

If anyone has a fix for this problem, I would greatly appreciate the sharing of said knowledge. For now, I will download an earlier version - hoping that this is a 2.6.0 bug. It's really the only thing I can do... I have a 48-page program due by 4/15 and I can't get past the cover.

I shall report back if the corruption goes away with a previous version of Publisher [and fingers crossed that I am able to import a 2.6 file into the 2.5.7 or 2.4.1 version] Wish Me Luck!

AND I fully support the Autosave function being added to the next update... I don't carry my external BU when I'm working away from home, therefore Time Machine does not solve my problem.

SSD Pgm 2025.1.afpub

[carl123]

Cant download your .afpub file (says not available)

Probably just a forum glitch.

Can you try uploading it again?

[TChitwood]

Here is Round 1 and Round 2 - You would think that I would know better than to NOT zip the files and expect them to transfer. LOL

Thanks for taking a look.

SSD BU.zip

[TChitwood]

Here is Round 1 and Round 2 - You would think that I would know better than to NOT zip the files and expect them to transfer. LOL

Thanks for taking a look.

[TChitwood]

Oops - forgot to report on the outcome of the Affinity Publisher 2 v2.5.7 Experiment.

One word: FAIL [it was worth a shot - and yes, I had a feeling it wouldn't work]...
it would have been a success, had I been able to export to the equivalent of an .IDML file. But, alas, no.

All of that being said - I am happy with the conversion to AP2 [albeit not by choice, but a financial necessity]

[Hangman]

Hi @TChitwood,

As you point out, only one version of the file opens: SSD Pgm 2025.1.afpub. All the other versions and the .afpackage files are corrupted.

There are a couple of missing linked files. One is an unnamed cloud graphic, which I recommend you name and then replace in the Publisher file. The second is a PDF, neither of which appear in the Images folders in your upload.

The issue appears to be with pages 10 to 17. Those pages are causing the file to hang repeatedly. Removing those pages allows the file to function normally, though I've not tested it extensively...

You may need to start by deleting pages 10 to 17 and then rebuilding those pages...