file corrupted

[filippoguidarelli]

Hi, a huge file of a book looks corrupted and does not open. I used resources on my mac (mac mini), not cloud or other external drives. It seems like it's impossible to recover it. This is not the first time it happens: usually I made copies of the file once or twice a day (even if it's not a professional way to work) but this time I had not. What's the issue? It must be solved, because it's not acceptable for a professional to experience such an issue. 

[carl123]

Can you upload the document to the forum?

[filippoguidarelli]

here's the file

Rafanelli-2024_012.afpub

[carl123]

The file is a total mess for me but maybe the Affinity team can do a better recovery with the tools they have at their disposal

I attach what I can recover but all images appear corrupt

I would not trust the document enough to keep working in it but maybe you can copy the text etc as you appear to indicate you have no backup

 

 

 

bestIcanDo.afpub

[filippoguidarelli]

2 minutes ago, carl123 said:

The file is a total mess for me but maybe the Affinity team can do a better recovery with the tools they have at their disposal

I attach what I can recover but all images appear corrupt

I would not trust the document enough to keep working in it but maybe you can copy the text etc as you appear to indicate you have no backup

 

 

 

bestIcanDo.afpub 340.62 MB · 1 download

Hi, thanx for trying. The only effective workaround was creating a new file and adding pages from the corrupted one. I made this proceeding for sections and finally got to the corrupted part: it looks like there's a single image which provokes the issue, an afphoto image btw. The strange thing is that I put the image into the file last week but it only started to create issues today (please note I didn't touch this image)

[NathanC]

Hi @filippoguidarelli,

We'll get your file logged with the developers for further investigation into what's caused it. So we've got as much information to hand as possible, we would be grateful if you could also answer the below:

1. Which Affinity app and version did the file last get saved in?
2. Which Operating System are you using?
3. Are you saving the document to an Internal drive, External drive or Network location?
4. Is the folder you’re saving to syncing to Google drive, OneDrive, iCloud, Dropbox etc...?
5. Do you have any Anti-virus and/or Anti-malware software running on your machine. If so, which one(s)?
6. Was this file a new document or are you trying to save to an existing document?
7. Are you able to save a new document to the same location?
8. Can you remember what you were working on within the affected document before trying to save?
9. Any other information you think would help us try to find the problem

 

Thanks

[filippoguidarelli]

12 minutes ago, NathanC said:

Hi @filippoguidarelli,

We'll get your file logged with the developers for further investigation into what's caused it. So we've got as much information to hand as possible, we would be grateful if you could also answer the below:

1. Which Affinity app and version did the file last get saved in?
2. Which Operating System are you using?
3. Are you saving the document to an Internal drive, External drive or Network location?
4. Is the folder you’re saving to syncing to Google drive, OneDrive, iCloud, Dropbox etc...?
5. Do you have any Anti-virus and/or Anti-malware software running on your machine. If so, which one(s)?
6. Was this file a new document or are you trying to save to an existing document?
7. Are you able to save a new document to the same location?
8. Can you remember what you were working on within the affected document before trying to save?
9. Any other information you think would help us try to find the problem

 

Thanks

1. Affinity publisher 2.5.2
2. Mac mini M1 - Sonoma 14.4.1
3. Internal drive
4. No
5. No
6. Save an existing document
7. Yes
8. I think substitutions or regulations (brightness etc) of linked images
9. The issue seems somehow linked to some images: once removed it started to work again; plus, yesterday ate the end of the day I got the same problem, but this morning the file was normally openable.