"This file type is not supported" / WTF, Serif?

[mangauniversity]

So, today got the dreaded "This file type is not supported" error when trying to open a Publisher 2 file that I had already done significant work on. I don't want to start over again. I want the file that I created, worked on, and saved, to open again as it is supposed to open.

Serif, stop making lame excuses for this error. If you can't help me open the file, then give me the money back that I spent on your flawed software.

[Dan C]

Hi @mangauniversity,

We’re sorry to hear that your Affinity document is no longer opening for you. Please upload the file to us using the below link and we’ll take a further look at the file to see if we can recover any of its contents.

https://www.dropbox.com/request/6As88PsJrFK1aSL9EyNd

We would obviously also like some additional information to see if we can work out the cause of the problem and stop it happening in future. To assist this process, as well as uploading your file, please can you also tell us the following:

1. Which Operating System are you using?
2. Which version of Affinity did the file last get saved in?
3. What drive type was the file last saved to?
Local disk
USB disk/Flash disk
Google Drive folder
OneDrive folder
iCloud folder
Dropbox folder
Network location
Other (please specify)

4. Any other information you think would help us try to find the problem?

We suggest that you check to see if you have any backups of the document available in case we’re unable to recover the file. The investigation process can take some time, but we’ll be back in contact with our findings.

3 hours ago, mangauniversity said:

Serif, stop making lame excuses for this error

I'm unsure if you're aware, but we've made large changes in this area in our latest beta version in order to reduce the chances of this occurring. Although we don't recommend using the beta version for production work, you can find out more about these fixes here -

On 7/14/2023 at 12:07 PM, Ash said:

Important: This build also includes some changes to how we load and save files, in particular to be more robust when files are saved on removable storage / network drives and in scenarios when connection to those drives maybe lost. We believe these changes to be safe, but there could be more risk than normal with this beta that you could encounter file save problems / lose work. For that reason wanted to remind you again that we recommend you do not use the betas for production work and create a backup of any important files you want to load into the beta.

[mangauniversity]

Frankly, I am not comfortable uploading the file to Affinity's Dropbox. Why not just explain here what steps can be taken to determine if any of the contents can be recovered? 

 

[Bryan Rieger]

As Serifs Affinity file format (Photo, Designer, and Publisher all use the same file format) is proprietary they likely have specialized in-house tools they created themselves to help inspect, diagnose and debug their file format, similar to the way PSPDFKIT created PDF Inspector to help them do the same with the wide range of PDF files in circulation.

I've always hoped that Serif might one day open up their file format (at least a little) which would enable others to build tools, workflows, and interoperability with other applications. While they would be giving away some of their work and IP in doing so, they could also foster a much richer ecosystem built around the Affinity Suite and file formats, while ensuring they remain at the centre of it all.

Anyway, so long as the Affinity file format is a black box there is very little we as users can do to fix problems when they arise. While it's lovely that Serif always tries to help in these circumstances, it's not always possible to share the files with Serif due to privacy and IP concerns.

[Dan C]

I'm sorry to hear this, though I certainly understand.

We at Affinity have access to tools/builds of the app that can be used to attempt to recover these documents that are not available to the public - alongside a breadth of knowledge in regards to repairing or identifying the underlying cause of such corruptions that unfortunately cannot be simply summed up within a post here on the forums as much of this is related to the aforementioned internal tools.

However, you may wish to try the following - as this is one of the most basic tools in our arsenal for repairing documents:

1. Create a new document in Publisher, matching the Page/Spread size, colour space/ICC profile and DPI of the corrupted document, where possible.
2. Navigate to Document > Add Pages From File... and select the .afpub file in the dialog that opens.
3. In the Add Pages dialog that now shows, change the Add Pages: option to Replacing, then set the Pages: option to 1, if not already.
4. Select OK and the app will attempt to add the corrupted document pages to this new file, potentially allowing for content to be recovered.

I hope this helps!

[mangauniversity]

 

8 hours ago, Dan C said:

I'm sorry to hear this, though I certainly understand.

We at Affinity have access to tools/builds of the app that can be used to attempt to recover these documents that are not available to the public - alongside a breadth of knowledge in regards to repairing or identifying the underlying cause of such corruptions that unfortunately cannot be simply summed up within a post here on the forums as much of this is related to the aforementioned internal tools.

However, you may wish to try the following - as this is one of the most basic tools in our arsenal for repairing documents:

1. Create a new document in Publisher, matching the Page/Spread size, colour space/ICC profile and DPI of the corrupted document, where possible.
2. Navigate to Document > Add Pages From File... and select the .afpub file in the dialog that opens.
3. In the Add Pages dialog that now shows, change the Add Pages: option to Replacing, then set the Pages: option to 1, if not already.
4. Select OK and the app will attempt to add the corrupted document pages to this new file, potentially allowing for content to be recovered.

I hope this helps!

Can't even get past the "Add Pages From File" dialog, as attempting to open the older file results in the "File type not supported" error.

As for uploading the file to a Dropbox account to which who knows knows how many people have access? No thanks! The file contains unpublished, copyrighted material, and I can only imagine in whose hands it might end up.

[walt.farrell]

6 minutes ago, mangauniversity said:

As for uploading the file to a Dropbox account to which who knows knows how many people have access? No thanks!

Serif have said that only their staff can read from the Dropbox links that are provided. I know that we forum users can't.

And Serif commit to deleting the information when they're done analyzing it.

But if you don't trust them, that's your choice, of course.

[mangauniversity]

19 minutes ago, walt.farrell said:

Serif have said that only their staff can read from the Dropbox links that are provided. I know that we forum users can't.

And Serif commit to deleting the information when they're done analyzing it.

But if you don't trust them, that's your choice, of course.

Serif's forums were hacked through an Admin account a few months ago. Who knows whether the hackers also have access to Serif's Dropbox account. So yeah, I've chosen not to trust them.

All of this makes me really sad. Not because I lost my file. (That makes me mad.) It's the loss of my belief in Serif's products that makes me sad. I used to tell everyone I knew that they should ditch Adobe and hop aboard the Affinity train. Can't make that recommendation any longer, though.

[mangauniversity]

And now I can't even save newly created files.

MacOS Monterey 12.6

Affinity Publisher 2.1.1

Attempting to save to a local disk.

[mangauniversity]

I opened the recovery file, made one text change, tried to save and got this error.

 

[walt.farrell]

6 hours ago, mangauniversity said:

And now I can't even save newly created files.

Where are you trying to save them?

6 hours ago, mangauniversity said:

I opened the recovery file, made one text change, tried to save and got this error.

That sounds like your original (that the recovery file is based on) was marked Read-Only in the file system permissions.

[Bad_Wolf]

Sometimes, when things go wrong, I also have to forward files, which I worked on for a long time, to the software vendor. If we cannot trust Serif or those who create our software, then moving on to another vendor is better. I never had any negative experiences when sending a file to Serif or any other software creator when asked.

I am sure Serif will not illegally use your publication because when they do, they are finished! If that comes out, they lose their trust and customers.

If you want your publication recovered, you have to trust Serif. Your other option is starting all over again or using another tool.

[Dan C]

16 hours ago, mangauniversity said:

Can't even get past the "Add Pages From File" dialog, as attempting to open the older file results in the "File type not supported" error.

I'm sorry to hear this, it would usually indicate that the file is missing data and likely unrecoverable, our sincerest apologies - though of course I can only guess without a copy of the file.

16 hours ago, mangauniversity said:

All of this makes me really sad. Not because I lost my file. (That makes me mad.) It's the loss of my belief in Serif's products that makes me sad. I used to tell everyone I knew that they should ditch Adobe and hop aboard the Affinity train. Can't make that recommendation any longer, though.

As mentioned in my initial post, our team are actively working on this issue and are implementing changes in our upcoming 2.2 update to address these and attempt to reduce the chance of this happening.

As with any computer software, unfortunately file corruption can occur, though I certainly understand your hesitation following this.