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

[Paul Mc]

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?

[walt.farrell]

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.

[Paul Mc]

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?

[R C-R]

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.

[Paul Mc]

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 😊).

[walt.farrell]

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.

[Paul Mc]

@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.

[Lee D]

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.

[Paul Mc]

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.