Jump to content
Lojza

Failed to open an older .afdesign document

Recommended Posts

Hi, I'm trying open some older .afdesign document in the newest version for Mac and I'm getting the "File type not supported" error:

screenshot_1474.png.e3fe64ff4ed84f6a1e03649ae26ffa76.png

I can't remember in which version I've created the document, but it was certainly several years ago. Was there any backward compatibility break in the meantime? Is there a way how to recover the document?

Thanks for any advice.


UX/UI designer, IT analyst & consultant, Business Architect at Cool Ticket (www.coolticket.co).

MacBook Pro 13'' Early 2015, 3,1 GHz Intel Core i7, 16 GB 1867 MHz DDR3, Apple Thunderbolt Display 27'' (2560 x 1440).

Share this post


Link to post
Share on other sites

Are you able to upload the document to the forum?


Due to the fact that Boris Johnson is now our Prime Minister, punctuation, spelling and grammar will never be worried about ever again.  We now have far bigger problems to be worried about.

Share this post


Link to post
Share on other sites

Hi Lojza :)

Sorry to hear this!

4 hours ago, Lojza said:

Was there any backward compatibility break in the meantime?

Certainly not that we're aware of, all files should be forwards compatible (ie old files will open in the newer versions, not vice-versa)

If you don't wish to post this file publicly, could you please upload it to the following link so we can investigate further for you? Has the file been opened/saved on an external/network drive?

Thanks in advance!

https://www.dropbox.com/request/3ZpgxuJ4lDdRe7YKsC76

Share this post


Link to post
Share on other sites
2 hours ago, Dan C said:

If you don't wish to post this file publicly, could you please upload it to the following link so we can investigate further for you? Has the file been opened/saved on an external/network drive?

Hi Dan C,

Thanks for the response. I've uploaded the file to Dropbox. And yes, I moved it to Google Drive earlier this year and now moved back to my local drive.

 


UX/UI designer, IT analyst & consultant, Business Architect at Cool Ticket (www.coolticket.co).

MacBook Pro 13'' Early 2015, 3,1 GHz Intel Core i7, 16 GB 1867 MHz DDR3, Apple Thunderbolt Display 27'' (2560 x 1440).

Share this post


Link to post
Share on other sites

Thanks for your file and for confirming that, I've forwarded your file to one of our developers for investigation and to see if we can recover the file for you - I'll respond here in due course :) 

Share this post


Link to post
Share on other sites
On 8/28/2019 at 4:13 PM, Dan C said:

I'll respond here in due course :) 

Hi @Dan C, any news on that?

In the meantime, I'm struggling with another older file (created maybe in AD 1.5 and saved in AD 1.6, or maybe both in 1.6, not sure now). However, it's quite big design (140 MB) with some SVGs in it (as inserted files). When trying to open it in current Affinity Designer, the app throws tens of "Linked Resource Changed - Image ... has been modified outside of the application" warnings, then hangs the computer for some time, then hangs itself for another quite long time and finally (after a couple of minutes) opens the document, which seems OK. This file has never been uploaded to a network drive or cloud - from its creation, it stays on local disk.

Is it possible to investigate on this as well? I'm willing to upload the file for your examination, if necessary (not publicly, however).

Thank you!


UX/UI designer, IT analyst & consultant, Business Architect at Cool Ticket (www.coolticket.co).

MacBook Pro 13'' Early 2015, 3,1 GHz Intel Core i7, 16 GB 1867 MHz DDR3, Apple Thunderbolt Display 27'' (2560 x 1440).

Share this post


Link to post
Share on other sites

My sincerest apologies for the delay here, there's unfortunately been no developer update with this file as of yet, I'll bump the report again for you now.

19 hours ago, Lojza said:

When trying to open it in current Affinity Designer, the app throws tens of "Linked Resource Changed - Image ... has been modified outside of the application" warnings, then hangs the computer for some time, then hangs itself for another quite long time and finally (after a couple of minutes) opens the document, which seems OK.

This is a bug our developers are aware of and has been caused by allowing Linked not Embedded resources in Publisher, meaning a global change was required for the suite - however certain files made before 1.7 exhibit this behaviour when opening a file with Embedded content - meaning even if the documents had been updated externally, this would have no effect in your document. We hope to have this fixed ASAP!

Share this post


Link to post
Share on other sites

Many thanks for your continued patience and understanding here, unfortunately our developers have tried to recover this file, however it appears as though the data has been lost/corrupted by Google Drive.

We suspect this has happened in the process of either uploading or downloading from Google Drive. Do you still have a copy stored here? We've found previously that downloading files through the Google Drive app occasionally corrupts files, however we've seen better results when downloading them directly from the Web interface. If you still have a copy stored online, could you try this for me?

Share this post


Link to post
Share on other sites
On 10/1/2019 at 12:06 PM, Dan C said:

Many thanks for your continued patience and understanding here, unfortunately our developers have tried to recover this file, however it appears as though the data has been lost/corrupted by Google Drive.

We suspect this has happened in the process of either uploading or downloading from Google Drive. Do you still have a copy stored here? We've found previously that downloading files through the Google Drive app occasionally corrupts files, however we've seen better results when downloading them directly from the Web interface. If you still have a copy stored online, could you try this for me?

Thanks @Dan C for your assistance! Yessss! The original file downloaded from GDrive via web interface works well! Wow, you saved my day! :) (I actually use Expandrive most of the time for downloading/uploading to GDrive... So it seems the GDrive API is somehow messing with the files o.O).

We can consider this topic closed ;) Thanks again!


UX/UI designer, IT analyst & consultant, Business Architect at Cool Ticket (www.coolticket.co).

MacBook Pro 13'' Early 2015, 3,1 GHz Intel Core i7, 16 GB 1867 MHz DDR3, Apple Thunderbolt Display 27'' (2560 x 1440).

Share this post


Link to post
Share on other sites

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

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.