Jump to content

Recommended Posts

Posted

I have a file that I created in Affinity Publisher 2 and have been working on for the last couple of months. It's an AFPUB file. I haven't worked on it for 3 weeks and today when I tried to open it, it says "the file type is not supported". I created it on the same computer, on Affinity Publisher 2. There has been a small update to Affinity Publisher 2 since then, which I accepted, but other than that, nothing has changed. Any ideas for how I can fix this and open the file?

 

image.thumb.png.3df311f5bc454b259ac3706abd7f1340.png

Posted

Seems to be another problem with this shit OneDrive. You have linked your documents folder to the MS OneDrive Cloud and this causes many problems in many other apps too, not only Affinity.

Always work on a local file which is not synced to any cloudstorage. Use the cloud (if at all) only to backup or share files.

Hopefully you have a local backup of your file. Also youn try to download the file to a folder which is not synced to the cloud.

Regards,
Otto

Affinity Suite v2.6.x - Windows 11 Pro

Posted

Thanks. I've been using OneDrive for five years and never had this happen. I didn't realise it was an issue. It's tough because I have to change between two computers when working so I guess I'll have to figure out a way around it. Thanks for your help!

Posted

As said, do not work directly on synced files. Work locally and then upload it to the cloud and download it locally to your other PC.

Regards,
Otto

Affinity Suite v2.6.x - Windows 11 Pro

Posted

You might try moving the file to a directory) disk that is not managed by OneDrive. Or marking the file to be available offline so OneDrive restores the complete file to your local drive.

-- 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:  Windows 11 Pro 23H2, 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 18.5, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.5

Posted

Hi @Country Cow Designs,

Thanks for your report & we're certainly sorry to hear this file is no longer opening for you.

As we've confirmed via Facebook DMs, unfortunately our Support team were unable to recover this file using our usual methods, and therefore it has been logged with our development team using the information you've already provided.

As the file was stored using OneDrive, you may be able to recover a previous version of the file in working condition using the method outlined below -

OneDrive Version History

I hope this clears things up!

Posted
3 hours ago, Dan C said:

this file is no longer opening

Just curious, isn't the message "File type not supported" wrong? According to the message, it's a file that isn't corrupted (checks confirm it's correct), but Affinity doesn't support its format (the fact that it has a *.afpub extension may not be relevant, as the file may have been renamed).
Or is it a "damaged" file that Affinita misinterprets as "unsupported format"? Do Affinity files even have any checking mechanisms to detect their corruption?

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.5.7.2948 (Retail)
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605.
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.

Posted
27 minutes ago, Pšenda said:

Just curious, isn't the message "File type not supported" wrong?

Technically the message is unexpected, as it appears to have been a legitimate .afpub file previously - but the reason for it is likely the one you've already mentioned;

27 minutes ago, Pšenda said:

is it a "damaged" file that Affinita misinterprets as "unsupported format"

If certain file header information is missing, the Affinity app will not read the file as a supported format, regardless of the file extension itself.

29 minutes ago, Pšenda said:

Do Affinity files even have any checking mechanisms to detect their corruption?

The Affinity apps do have checks for corruption, which happen when loading the file - this is the reason you may occasionally see "the file has been opened, but has errors" warning, as this corruption detection can sometimes find issues with a file that can otherwise be loaded and appear normal.

Unfortunately the actual mechanisms for corruption detection are a little outside my remit of knowledge, so I can't really explain the functionality much further - but I hope this clears things up!

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • 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.