Jump to content
You must now use your email address to sign in [click for more info] ×

Affinity Designer file is corrupted suddenly


Recommended Posts

7 hours ago, ic90 said:

Thanks for checking this out @LibreTraining. I created other text frames as a work around to get around the issue. I'm not sure about the versions you have. I got the fonts from Google Fonts. Bitter and Work Sans. Both should be free.

You have a few other fonts in there - one is in the logo, but the other two I am not sure where they are used.

The odd characters may have come from the original source of the text, if you did not type it directly. How was the text entered?

Link to comment
Share on other sites

13 hours ago, cxazet said:

Hi it's me again, @carl123

One of my project, it says "corrupted" can you fix it?

I am using Windows 10, Affinity Photo (1.9.2)

https://drive.google.com/file/d/1OcgwyjhHKuDJH6fyIyQtQwFXWNvPGC77/view?usp=sharing

also please reupload or send back the fixed file at my PM like last time.

I have PM'd you the recovered file

Backup frequently, not all corrupt files are recoverable

To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.

Link to comment
Share on other sites

I appear to have been struck by the gremlin as well. After hours of work on an Affinity Designer project (attached), when I went back to make a small but important change, the file appears to be corrupted. The work was all done on the internal drive on this computer, but does include a link to an Affinity Photo file.

The original file is corrupted, as are all my backups, so I feel that it was probably corrupted when I originally quit and saved.

This is on a Mac running Catalina and v1.7.1 of Affinity Designer.

If you fine folks could work your magic and make my file usable again I'd hugely appreciate it.

Many thanks – Nic

CorruptedFile.afdesign

Link to comment
Share on other sites

  • 2 weeks later...
On 8/10/2021 at 2:16 PM, RB DESIGN said:

I too have a "The file appears to be corrupted" message appearing. File was saving and encountered a lack of disk space issue on my local drive. I removed the necessary space on my drive to save the file and upon opening again encountered the Error. Working on OS 10.14.6 and am currently on Affinity Publisher 1.10.0 but the file was created/saved in the pervious Publisher version but had automatic updates enabled and the app updated the following day to current version. Are you still able to assist in the recovery of files like this or provide instructions on how I can attempt myself? Have DEV background but wanted to reach out before mucking around in the file and making things worse. Thank You for all your assistance. 

Any help with determining if this file can be recovered would be greatly appreciated. Thank you for all your efforts.

1402882391_BrownBook3.1.afpub.zip

Link to comment
Share on other sites

On 8/14/2021 at 10:22 PM, Nic McPhee said:

I appear to have been struck by the gremlin as well. After hours of work on an Affinity Designer project (attached), when I went back to make a small but important change, the file appears to be corrupted. The work was all done on the internal drive on this computer, but does include a link to an Affinity Photo file.

The original file is corrupted, as are all my backups, so I feel that it was probably corrupted when I originally quit and saved.

This is on a Mac running Catalina and v1.7.1 of Affinity Designer.

If you fine folks could work your magic and make my file usable again I'd hugely appreciate it.

Many thanks – Nic

CorruptedFile.afdesign 4.32 MB · 8 downloads

I haven't heard back and folks deadlines are looming. Looks like I'll have to redo the project, which isn't super exciting.

Link to comment
Share on other sites

  • 3 weeks later...

File now opens, looks OK but can't vouch for its integrity

Do backups not all files are recoverable

And someone get that guy an ashtray

 

stanzetta2-recovered.afphoto

To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.

Link to comment
Share on other sites

@carl123

Any chance my file (a few posts up) can be fixed?

I appreciate the need for backups. Unfortunately in my case it appeared to have been corrupted when first saved, as all my backup copies are also corrupted and won't open.

Is there some "simple" magic folks are doing to try to fix these corrupt file issues? I'm happy to try to open the file up in some editor and hack around if there's a little guidance.

Thanks – Nic

Link to comment
Share on other sites

@Nic McPhee

Sorry, no help on that one. Try contacting support directly to see if they can help, if the file is important

To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.

Link to comment
Share on other sites

Good Day,

I too seem to have suffered the 'File Corrupted' bug today as this file I was working on up til this morning without issue suddenly won't open and is saying it's corrupted (see screenshot attached below).

The previous version I have of this file is fine, though this is the 99% complete version of the document and I am due to submit a draft to the client today. Is there any way this file can be recovered? Here are my system details -

OS: Windows 10

Affinity Publisher Version: 1.100.1127

HD: Western Digital 'My Passport' external HD

Font Manager: Fontbase

 

Let me know if you need any further info or have any issues with the files....many thanks.

Affinity Publisher_FileCorrupted_Grab_Sep17.jpg

CPDC_ProgrammeReport_2021_Sep17_Corrupted.afpub

Link to comment
Share on other sites

  • 1 month later...

Hope you don't mind me tagging onto this thread but I've got a problem with corrupt AD files too - on a laptop.   In the summer I had so many corrupt files and, eventually, my hard drive broke so I assumed that was the issue.


My hard drive was replaced with a new one and laptop/software rebuilt (Windows 10).  I've been working on it fine since then and have deleted old corrupt files as and when I find them.  I make lots of scrapbook and greetings card designs and whenever I make an Affinity file (I've used Photo, Publisher and Designer) I also create a JPG file for printing.  The corrupted files were always Affinity files - no JPGs, PDFs, Documents or Photos on my laptop were corrupted.

Over the last few days I've found newly created artboard files in AD to be corrupt.  Fortunately I'm backing up to external drive and (now) a USB too as I lost so much work when the hard drive crashed, so I don't need your help to recover a file but just thought I'd report this issue and find out if anything is obvious to you that's not obvious to me. 

I'm using AD v 1.0
Windows 10 (up-to-date)
NVIDIA Gameforce drivers have been updated 2 days ago (I saw mention of them on another post when I searched for the corrupt file issue)

I've added the latest corrupt file herewith in case you would like to examine it.

1961812939_MyFloralAssetscont(2).afdesign

Link to comment
Share on other sites

15 hours ago, Canterslowly said:

I'm using AD v 1.0

I recommend updating - the current version of ADesigner is 1.10.4.

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.3.1.2217
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.2506.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.2506.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Link to comment
Share on other sites

Hi. PLEASE HELP. I have a very important file that just went corrupted.

How can I recover the last edits I made?  I also don't know why it is 2GB in size, all my media is linked.

here is my file I HOPE you can help me else i would have to redo a lot of work. :(

https://we.tl/t-ZzbRoUN8iU

 

worked on M1 macbook air 8gb ram

affinity 1.10.4

was trying to save then affinity crashed. now file is corrupted.

Link to comment
Share on other sites

Hello,

same experience here. I finished all the work with my book, copying last two pictures and then it crashed. It says my file is corrupted. I can´t open it to make backup. What should I do? Working with Affinity Publisher on HP AMD Ryzen 5, 8 GB RAM, 2 GB graphics.

632288062_Havarrskkobkytypografiehyphenationodsazen.afpub

Edited by machetasmo
Link to comment
Share on other sites

Hi I'm have the same issue with files corrupting and I'm not able to open them. Can you please have the Devs take a look and let me know what's happening ASAP please.

File upload doesn't seem to be working, I've uploaded the files in question to Google Drive

https://drive.google.com/drive/folders/1JeTKNdaYez6oTnCMv-58vLRvg8pWcQD3?usp=sharing

Edited by KeithP
Link to comment
Share on other sites

2 minutes ago, Canterslowly said:

@carl123  Hello - would you know if this thread is being monitored still?  I'm just wondering if the reason for these file corruptions is understood by the Affinity team.  Thank you. 

Most file corruptions occur when the file being worked on is not on a local/internal drive (i.e. a drive inside your computer) due to the connection to the (external) drive being dropped, even temporarily

The Affinity team is aware of the problem but have not as yet solved it and as such their recommendation is to always work on the file locally and then copy/move it to another external drive if that is where you ultimately want to store it.

Further recommendations, by others, is to do regular backups and to do a File > Save as... to a new file name every so often when working on a file, so you can always go back to a previous version should your main document crash and be unrecoverable

PS If you have a corrupt document, you can upload it to the forum to see if someone here can recover it for you or if it is private then request a dropbox link from the support staff and upload it privately to them.

 

To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.

Link to comment
Share on other sites

@carl123 Thank you for your answer.  I always save direct to my hard drive and do regular "save as" updates.  I also back up to a USB drive once I've finished working on the item.  I'm a hobbyist so it's unlikely I'd have anything important enough to bother the team with 😀😀 (I hope).  It's good to know that the forum threads are being monitored.  I can imagine it's a massive task!  👍

Link to comment
Share on other sites

1 hour ago, carl123 said:

Further recommendations, by others, is to do regular backups and to do a File > Save as... to a new file name every so often when working on a file, so you can always go back to a previous version should your main document crash and be unrecoverable

I suggested Serif's automatic indexing of the previous/backup file name. Maybe they implement it sometimes.

Although I don't hope for it much after a year, even though it's a matter of a few minutes - I use it myself in my applications.

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.3.1.2217
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.2506.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.2506.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Link to comment
Share on other sites

  • 4 weeks later...
Guest
This topic is now closed to further replies.
×
×
  • 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.