Access from Third Party App rejected

[JPLM]

I recently upgraded to V2 from a V1 I really appreciated. What was presented as a major step forward happens to be -in my opinion- a step backward. V1 was stable and working fine. V2 crashes and I just discovered a major and very embarrassing issue. On my desktop, Affinity Photo is the default photo editor I have to use from a third party app (Reallusion IClone 7.93).

With Affinity V1, I never had any problem. Now IClone does not find it.  I pointed to: C:\Users\myname\Appdata\Local\Microsoft\WindowsApps\AffinityPhoto2.exe    and I always get an error message (Cf attached).    What do I have to do?  I have already wasted a lot of time searching and trying to no avail. Do I have to go back to Affinity V1 ?

AMD Ryzen 9 5900x, Nvidia RTX 3070, 32 Gb RAM, Windows 11, plenty of SSD storage

Affinity error message.pdf

[JPLM]

I finally found the solution to my problem, and this is to dump V2 and reinstall V1 which was working fine. A real waste of the money. Besides, there was a Tech support with V1 and it seems to have disappeared with V2.

Very unhappy with this upgrade!

[R C-R]

A quick search of the forum reveals a number of ways to work around the limitations of the MSIX installer, plus the welcome news that they will be releasing an MSI installer which should make the workarounds unnecessary.

[JPLM]

Yep! I hope it comes quickly. I tried some of the work around solutions including aflaunc.exe but none of them worked.  I am also currently working on a huge book (>700 pages) with Publisher V2  and honestly I don't see what improvements it brings to V1.        I'm afraid Serif fell to the current temptation of releasing new upgrades which bring more problems than improvements.

 

[walt.farrell]

6 minutes ago, JPLM said:

and honestly I don't see what improvements it brings to V1.

Footnotes, for one, which many users need.

I'm curious how you are using iClone with Publisher. Off-hand from reading its description, I don't see how it would be beneficial.

[JPLM]

I'm just saying that I purchased the Affinity suite. So far I have been using Publisher V2 as I did with V1 and probably I did not explore enough to find obvious differences.

No connection with Designer and Photo that I am using together with video. For me, a full integration to IClone is crucial and after wasting a lot of time in trials and errors, I just came back to photo V1.  

[walt.farrell]

OK. And what kind of "integration" are you doing with iClone? What do you need to set up?

[JPLM]

let's say I have a prop, 3D object, text,  or character in IClone and I want to change the color somewhere or the text. Then I send it to Photo, make my change and reimport it in IClone. Done!  

[walt.farrell]

5 minutes ago, JPLM said:

Then I send it to Photo, make my change and reimport it in IClone.

You can do that in Photo 2. If iClone doesn't support Windows App Execution Aliases, just install the aflaunch.exe helper application and have iClone invoke it. 

See the second post in the FAQ: 

https://forum.affinity.serif.com/index.php?/topic/167828-accessing-affinity-v2-apps-from-other-apps/

[JPLM]

and that's exactly my problem, I pointed IClone to aflaunch.exe and nothing happened.

When I double click manually on aflaunch.exe, it launches correctly Photo 2

 

[walt.farrell]

Strange. No one else has reported something like that, that I've seen.

[JPLM]

I agree, it's strange

Have a good sunday evening!

[NathanC]

Hi @JPLM,

The legacy MSI/.EXE installers are now available for V2, so using this version should eliminate the need for any workarounds, more information below: