DanG

Hi @v_kyr, Thanks for reporting this. It looks to be an issue with the German translations and I've passed it on to our development team. Thanks again

Hi @Cobra Pilot, I'm glad you were able to resolve this, but I'd like to try and reproduce the issue myself so we can see what happened. I'm currently having difficulty doing so though, so would you mind confirming a few things for me please? In which order did you register the two applications? I.e. Did you do iOS or macOS first? What operating system versions do you have running on each of the two platforms? Had you installed any of the available free content on either of the platforms? What content do you now have available to you when you look at your account? Thanks in advance

Hi @ygoe, Thanks for reporting this. I can reproduce that here and have reported it to our development team. I've also raised the issue regarding keepass autotype. Thanks again

Hi @Nativo, I've not got a definite timeframe I'm afraid, although we're hoping for a release of 1.9.1 some time next week if testing goes to plan. That release should fix this issue, although you may find that the app will still crash the first time you try it, but then use a fallback code path on subsequent registrations. You might also want to try the latest beta to see if that resolves your issue. More information can be found here: https://forum.affinity.serif.com/index.php?/topic/134424-known-issues-common-issues-found-in-the-affinity-190-update/ Thanks a lot

Hi @rocsal50, Unfortunately this is a known issue affecting a few of our customers. We are currently working on a fix for version 1.9.1 which we hope to release some time next week if testing goes to plan. That release should fix this issue, although you may find that the app will still crash the first time you try it, but then use a fallback code path on subsequent registrations. You might also want to try the latest beta to see if that resolves your issue. More information can be found here: https://forum.affinity.serif.com/index.php?/topic/134424-known-issues-common-issues-found-in-the-affinity-190-update/ Thanks a lot

Hi @Nativo, Thanks for reporting this. Unfortunately a few customers on Windows have been experiencing this issue. We're aware of the problem and our development team are currently working on a fix. Thanks again

Hi @alexplus_de, Thanks for reporting this. Our development team have tracked down the issue and are working on a fix now. Thanks again

Hi @SimxX555, Thanks for reporting this. Unfortunately this is a known issue, however our development team are currently working on it. Thanks again

Hi @Bob Ohnstad, Thanks for reporting this. This is a known issue which our development team are currently working on. Thanks again

Hi @Alfred, Thanks for reporting this. It's actually a known issue and is already logged in our system. Thanks again

@edge261 & @MartyQ Welcome to the Serif Affinity forums Thanks a lot for reporting this. This is a known issue and our development team is currently working on it.

@MaartenTummers, Yours is actually a different issue to the one reported in this thread. Your issue is currently being investigated by our development team, and any updates will be relayed to you in this thread. Thanks a lot

Hi @e snissaert, Welcome to the Serif Affinity forums Thanks for reporting this. 2 quick questions: Does it affect all assets? If not, which asset were you downloading when it crashed? Do you have a crash report in %AppData%\Roaming\Affinity\Photo\1.0\CrashReports\reports? If so, would you mind uploading it here please? Thanks in advance

Hi @TonyX, Do you have an crash reports (in %AppData%\Roaming\Affinity\Photo\1.0\CrashReports\reports) you could share with us? If possible that would be very helpful. Thanks in advance

Hi @Subetoshi, Thanks for reporting this. This is actually a known issue which we are currently actively looking into. Thanks again