henryb

Affinity Photo - Apple Photo problems not addressed in this release or did I miss something?

I’ve been generally aware of the issue with Apple Photos and Affinity on the Mac for awhile now, but I just today got curious about the status of the fix that’s obviously coming and ran across this thread.
i say that the fix is obviously coming because I also have Affinity Photo running on my iPad, and it can easily export jpegs to Apple Photos - so it seems that Serif is aware that that ability is a desirable feature.
Mostly, however, I am appalled at the entitled attitude some users are demonstrating in this forum about this issue. More than a few of you have stomped your feet and threatened to abandon Affinity altogether if this issue isn’t given top priority and addressed immediately.  You should understand that threats are only effective if they’re actually carried out. After making the same threat theee of four times and you’re still here, everyone knows you’re just blowing smoke.  MEB has FAR more patience than I would under these circumstances. Personally, I’d have revoked your license, refunded your $50, and deleted your login to this forum.
Moreover, those of you who report that you have decided to use Apple Photos as your DAM - well, I’ll just say you certainly don’t have high expectations for the functionality of your DAM. At a minimum, I would expect a DAM to permit me to define my own folder structure and my own keyword tag hierarchy. I would prefer the keyword tags be written to the individual picture’s metadata (EXIF data), but I might live with an external database. Apple Photos, for all of its pluses, meet none of those requirements.  For that matter, one can’t even generally determine either the name that the photo is stored under or where it is stored.
So in my mind what a few of you are saying is that you’ve decided to use Apple Photos as something that it’s not really designed to be and you’re upset that Affinity Photos has a temporary issue that’s preventing you from doing what you want to do - and you’re unsatisfied with the speed at which Affinity is addressing the issue -,although what you want to do seems unlikely to be satisfactory in the long run.
Nevertheless, sometime in the not too distant future, there’s going to be a new version of Affinity, and Serif has apparently committed to fixing the issue in that version. When will is arrive? When they think it’s ready. Do they no yet when that will be? No.
you can either accept that in good humor OR you can find a different product. But please, do everyone else a favor and pick one of those two options. Stop with the constant bellyaching and idle threats.
Happy new year, everyone!

I have been working in IT for 45 years and have learned that one of the most important rule for successful keeping satisfied customers is: If you have problems that cause serious customer problems, solve them as soon as possible. It's a really bad idea to keep them waiting for several months.
Why don't they release version 1.7.4 as soon as possible, which fixes the bug only? Why must everyone wait for version 1.8? Serif has a good product and a good reputation, I don't understand why they are putting it at risk.

E.X.A.C.T.L.Y.!!! It's CRAZY that we've been unable to work properly on AP since JUNE 2019 (!!!!) and all we are getting is hints on a beta release, that "should" (not "WILL"...) fix AP's bug, at an unknown future date, and we will get new features with it... Like, seriously?? Release any new features you want, when you can, in order to remain competitive in the market. That's great. But we have been SERIOUSLY put back by this bug of yours for HALF A YEAR (in 10 days it will be a new DECADE for crying out loud) and still no fix!! If you have fixed it release it NOW. Please. Please. Please. Give us the new features LATER - that's not what's URGENT....

this
is 
not
even
funny
anymore

It does seem to be taking a very long time !!

Hi MEB
It really would have been good to release a hot fix just to fix this issue. I have spent literally years deciding which photo editing program to stick with and I chose AP for editing and Photos for organising. But this issue has been around for a REALLY long time and it still hasn't been fixed. I have worked in I.T. management for over 16 years and have never been won over on a "it's fixed in the upcoming Beta". If you've fixed it, RELEASE IT! You have 6 pages of people asking for help with this bug going back 6 months you must have a schedule for production release of 1.8, can you share it as I think your loyal customers and AP evangelists deserve better?
 

I'm getting this too.
Workaround doesn't work.

I'm having the same problem as henryb. I tried your workaround but it does not work. An error box pops up saying Unable to Save Changes for "Edit in Affinity Photo"

Can affinity keep us informed as to when this problem will be fixed. I have mentioned this problem in the Affinity group on Face Book and it appears we're not alone but it also appears others are not having any problems. 
we've paid for Affinity photo but would have thought how as the magazine IMAC FORMAT plugged Affinity a lot that such a site as Affinity would try and keep up. All were asking is simple really " give us an update and possibly a time frame as to when this will be resolved.

This is the workflow I tried many times but it does not save back to Photos for me. I also tried de-selecting the Affinity extensions, closing photos then re-selecting them...still can't save. Is there a timeline for the fix?

“Dude”, I’m the one who started this thread… And yes, I have been following it throughout. And, again, all we have been getting so far are - exactly – “vague responses”. A vague response is “we are working on it“. This response, essentially, has been recycled over the last 5 months (!!) since June.
A clear response, on the other hand, would have been, for example, “Our developers have been working on it feverishly since June, and we hereby inform you that the bug in our software to be fixed by ?/?/19”. Or, another example of a clear response would be “our developers have been working on our bug since June, but regrettably, they are still unable to fix it because the problem lies in the issues x y z which have been the reason for the delay“.
A vague ”We are working on it“ says absolutely nothing with regards to the ETA of the functional release (especially when we are approaching December - and in six weeks we will be in a different decade of when the problem first occurred and has yet to be fixed). And all us customers of serif who have purchased the affinity photo app so that we can directly edit from our Mac photos app – because that’s the reason most of us purchased it since it is meant to work flawlessly with the Mac photos app - have been on hold since June. Maybe you are a casual user of this app, or maybe your photos are not stored in your Mac’s photos app, but if you did you would understand that your entire workflow has been put on hold for five months! So, no, that’s not good enough. And, no, experimenting with “workarounds“ would just not be acceptable for such an insanely long time, and you would expect something more than just “we are working on it“ by now.

I was thinking of ditching LR and using Photos with AP, guess I'll have to wait before I can ditch LR

I had to go back to Ligthroom again. This company and whatever policy and way to prioritise their work is not acceptable to me. I have to say I regret having recommended people to go Affinity.

I am also having this same problem.  It's a real bummer because I just bought AP last month and then last week I downloaded the Catalina OS update.  If I would have known about this problem I either wouldn't have bought AP or I wouldn't have downloaded Catalina.  I imagine this is more Apple's fault than AP but still, this functionality is the main selling point of their product (at least for me).  

“Dude”, I’m the one who started this thread… And yes, I have been following it throughout. And, again, all we have been getting so far are - exactly – “vague responses”. A vague response is “we are working on it“. This response, essentially, has been recycled over the last 5 months (!!) since June.
A clear response, on the other hand, would have been, for example, “Our developers have been working on it feverishly since June, and we hereby inform you that the bug in our software to be fixed by ?/?/19”. Or, another example of a clear response would be “our developers have been working on our bug since June, but regrettably, they are still unable to fix it because the problem lies in the issues x y z which have been the reason for the delay“.
A vague ”We are working on it“ says absolutely nothing with regards to the ETA of the functional release (especially when we are approaching December - and in six weeks we will be in a different decade of when the problem first occurred and has yet to be fixed). And all us customers of serif who have purchased the affinity photo app so that we can directly edit from our Mac photos app – because that’s the reason most of us purchased it since it is meant to work flawlessly with the Mac photos app - have been on hold since June. Maybe you are a casual user of this app, or maybe your photos are not stored in your Mac’s photos app, but if you did you would understand that your entire workflow has been put on hold for five months! So, no, that’s not good enough. And, no, experimenting with “workarounds“ would just not be acceptable for such an insanely long time, and you would expect something more than just “we are working on it“ by now.

I don't understand all the grief on here, it's not a showstopper, not the end of the world, I think a liitle perspective is needed here, there is a perfectly suitable work around using a free app. We get free upgrades. I for one am happy to wait, not pay Adobe's subscription. These things happen.

I would also be glad if this problem would disappear. I talk a lot of people into Affinity Photo and got a lot of complains now...
I have no clue what goes wrong but I am sure it could not be rocket science to fix the bug. It is an official API for Photos and I pretty sure you would even get some help from Apple if you can not find the cause on yourself.
So please fix it soon.

Just a suggestion, maybe this thread should be pinned? Seems like someone starts a new thread every couple of days on this same topic.

An absolutely great idea
Would be really great to get a fix

This should work without workarounds. I hope it is fixed soon.

Not with RAW files.
 
And btw, Affinity....there is developer beta's for a reason. Got some new progress on the bug? Still no idea why its not working? Apple contacted? Someone doing anything? How is it prioritised? Some dude spending 2 minutes per day on it? Your competitors have this fixed by now, they did it last week.

DEAR AFFINITY DEVELOPERS!
As this forum is meant to be your "hangout" and you read all the problems customers/users are having in order to fix them, please let us know RIGHT AWAY when you will fix this HUGE BUG that your software has had over the last MONTHS. We bought AP exactly because it claimed to work flawlessly with macs and their included apps (especially Photos). Now it SIMPLY DOES NOT WORK WITH PHOTOS AND IT IS CAUSING A MAJOR PROBLEM WITH OUR WORKFLOW (we might as well have bought any 3rd party app that wasn't Mac-related...).
So please reply ASAP regarding WHEN EXACTLY you will fix this bug in your software.
Thank you. 

Seriously, is this even being worked on? Luminar 3 have it fixed by now, and Pixelmator have no problem with it either. Im talking about editing and saving directly into Photos. I have two options, wait for your fix unless its something that might take months(?) to fix or move back to Lightroom again. Any ETA for a fix? I need this working now, preferably yesterday.
 

This problem is still outstanding - i.e. I cannot save back into the Mac Photos app (Catalina, MBP) photos which I have edited in Affinity Photo. This has become a useless app for me now so have abandoned it in favour of Pixelmator - which does exactly what I want
Photo