Open a File in af.photo on the iPad Photos

[Nadar]

Hi 😉

How to open an "af.photo" file on the iPad Photos application ?

Thanks

[Callum]

Hi Nadar,

The following Spotlight article should explain everything you need if you have any questions let me know

https://affinityspotlight.com/article/how-to-switch-seamlessly-between-affinity-on-desktop-and-ipad/

Thanks
C

[walt.farrell]

43 minutes ago, Nadar said:

How to open an "af.photo" file on the iPad Photos application ?

Are you asking how to open a .afphoto file in Affinity Photo on the iPad, or in the Apple Photos app?

You can't open them in Photos.

[Nadar]

Thank you Callum 😉

I translate all this and I come back to you in case of problem.

Walt :

Quote

you can't open them in Photos

Thank you. Maybe the Callum answer will help. 

[Nadar]

I found a solution 😉

Just open a multi-window with the iPad Photos app to put Affinity photos and the iPad Photos app side by side.

Then open the page with the photo settings (black page) in Affinity photo and press the JPEG button (if it is in JPEG) at the top and drag and drop it on to the iPad Photos app.

The blur effect has been well displayed…

[Paul Mudditt]

@Nadar The easier way is EXPORT -> SHARE -> SAVE IMAGE which saves to Apple Photo albums.

[Nadar]

Thanks Paul 😉

Youre are right but as I explained it on another post this way can't work if you use a tool effect.

There is a kind of bug as explained in this other post. 

 

[Paul Mudditt]

On 9/6/2022 at 3:11 PM, Nadar said:

Thanks Paul 😉

Youre are right but as I explained it on another post this way can't work if you use a tool effect.

There is a kind of bug as explained in this other post. 

 

Ah ok, just to let you know that APPLE have fixed the failed export bug in iPadOS16.1 beta that I initially reported in January. Looks like it was never a Serif bug which is why they could not fix it.

[DM1]

On 9/8/2022 at 5:24 PM, Paul Mudditt said:

Looks like it was never a Serif bug which is why they could not fix it.

G’day Paul, It’s a shame Serif fail to communicate these sorts of outcomes to posters here who have constantly complained. It would have saved them a lot of ill feeling, and accusations of failing to fix reported faults. I’m wondering if the loss of parts of images is also related to iOS rather than Serif. It seemed to start being reported after iOS memory management in iOS 15 was changed by Apple. Again, lots of reports/complaints and no fix from Serif (just silence).🙂

[Paul Mudditt]

On 9/11/2022 at 6:52 AM, DM1 said:

G’day Paul, It’s a shame Serif fail to communicate these sorts of outcomes to posters here who have constantly complained. It would have saved them a lot of ill feeling, and accusations of failing to fix reported faults. I’m wondering if the loss of parts of images is also related to iOS rather than Serif. It seemed to start being reported after iOS memory management in iOS 15 was changed by Apple. Again, lots of reports/complaints and no fix from Serif (just silence).🙂

I discovered and reported the initial export problem  because I used iPadOS15 beta, so no surprise that I also spotted that the problem was fixed because I was using iPadOS16 beta.

The developers will be using primarily the released versions of each OS to avoid chasing bugs in the OS betas, so likely were unaware of the initial problem or that it was fixed.

I do not know if Apple have admitted there were problems introduced when they made major changes in how RAM and virtual memory is managed, starting in iPadOS15 and continuing into iPadOS16 but the Serif developers were on a hiding to none. Very difficult to debug your own code without having to debug major bugs Apple engineers introduced.

I’m sure the Serif guys have been tearing the hair out when base code for file handling which has been working 100% well since the very first released versions of the Apps suddenly starts misbehaving. Normally when a bug is introduced, the guys just have to wind the clock back in their configuration management system to find where the bug first occurred and compare the code to see what has changed. In this case my bet is that since no code had changes then they wouldn’t have clue how to fix it.

In a nutshell, I BLAME APPLE not SERIF for the majority of these long standing issues.

[DM1]

On 9/11/2022 at 7:07 PM, Paul Mudditt said:

In a nutshell, I BLAME APPLE not SERIF for the majority of these long standing issues.

Yes, I agree with you there. The apps were generally stable prior to Apples latest updates. It’s a shame Serif cops the flack for it. Stoic ‘silence’ from Serif doesn’t help.