Jump to content

Switching from AP to AD causes error and work appears to be lost


Recommended Posts

I started work on a photo in AP (v2.0.3) and then needed to work on a vector overlay so selected Edit in Designer... which launched Designer and then displayed this error message. Any idea how to interpret it? Neither application shows any of the file I was working on so is my previous work now lost?

image.png.2482052f4eb6165d009e90f4c4c8f9c6.png

Link to comment
Share on other sites

What OS are you using?

What release of Designer do you have?

But it is probably lost. Using File > Save before the transfer is safest.

-- Walt

Desktop:  Windows 11 Home, version 22H2 (22621.1413) 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 
Laptop:  Windows 10 Home, version 21H2 (19044.2728) 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
        Affinity Photo 1.10.6 (.1665) and 2.1.0 and 2.1.0. beta/ Affinity Designer 1.10.6 (.1665)  and 2.1.0  and 2.1.0 beta / Affinity Publisher 1.10.6 (.1665)  and 2.1.0  and 2.1.0beta
iPad Pro M1, 12.9", iPadOS 16.4.1 (a), Apple Pencil 2, Magic Keyboard

      Affinity Photo 1.10.7 and 2.1.0 and 2.1.0 beta/ Affinity Designer 1.10.7 and 2.1.0 and 2.1.0 beta/ Affinity Publisher 2.1.0 and 2.1.0 beta

Link to comment
Share on other sites

Sorry,  I should have mentioned that this is on Windows 10. The release is the recent v2.03 update.

I've done this step many times (100s) without any issue as it is part of a recurrent workflow I use. This error is new. Yes, Saving is clearly the missing step here 😂 I've now redone the work by saving the AP file and then opening it in AD i.e. not using the Edit in... method. This is not an issue for now as I will not use that feature in the short-term. I am wondering if anyone from Serif can comment on the error message. Is this something peculiar to my setup or a known issue?

Link to comment
Share on other sites

For what very little it is worth but as a Mac user I have never seen a file anywhere with the filetype *.afmigrate.

So while it may be totally irrelevant here, I have to ask if the file was ever saved with any name prior to trying to changing apps, or if any Windows user has ever noticed a file with this filetype on their PC.

All 3 1.10.6, & all 3 V2.03 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
Affinity Photo 
1.10.6; Affinity Designer 1.10.6; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Link to comment
Share on other sites

Hi @R C-R I didn't save the file before trying to switch applications. This might be the issue. I think that given the pathname quoted in the error message there is likely to be a permissions issue with that location. My guess is that AP wrote a file to that location - but failed, and the error wasn't trapped and handled and no file was saved to disk. Then AD is launched and expected the file to be there but it wasn't and so produces the above error but that's downstream of the original error (IMHO 😊).

Link to comment
Share on other sites

3 minutes ago, Paul Mc said:

Then AD is launched and expected the file to be there but it wasn't and so produces the above error but that's downstream of the original error

Or, you could be correct about a permissions error, but perhaps Photo was able to write, but Designer was not able to read.

-- Walt

Desktop:  Windows 11 Home, version 22H2 (22621.1413) 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 
Laptop:  Windows 10 Home, version 21H2 (19044.2728) 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
        Affinity Photo 1.10.6 (.1665) and 2.1.0 and 2.1.0. beta/ Affinity Designer 1.10.6 (.1665)  and 2.1.0  and 2.1.0 beta / Affinity Publisher 1.10.6 (.1665)  and 2.1.0  and 2.1.0beta
iPad Pro M1, 12.9", iPadOS 16.4.1 (a), Apple Pencil 2, Magic Keyboard

      Affinity Photo 1.10.7 and 2.1.0 and 2.1.0 beta/ Affinity Designer 1.10.7 and 2.1.0 and 2.1.0 beta/ Affinity Publisher 2.1.0 and 2.1.0 beta

Link to comment
Share on other sites

@walt.farrell maybe, but then we start the speculative guessing game. It needs insight from someone familiar with the inner workings of the code. Sadly, because there is no saved file (that I'm aware of) then there is probably no evidence of what exactly happened. I checked the folder referenced in the error message and it exists but is empty - hence my interpretation.

Link to comment
Share on other sites

  • 2 months later...
  • Staff

There isn't really a way to know why the process failed. The basic process is that the file is moved from the 1st app into the Migrate folder for the 2nd app to then open for editing. It could be sandboxed related depending on how the app was installed.

Link to comment
Share on other sites

Thanks @Lee D this happened a while ago and hasn't happened since. I am now in the habit of saving the file in the first app before switching to the second one. Out of curiosity, is the folder named in the error message the Migration folder you mentioned? If not, where would that folder be? Both apps were MSIX installs.

Link to comment
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...
 Share

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