Affinity Designer for iPad V2 crashing when invoking View mode or Split View mode

[tbaucells]

I was trying Shape Builder and wanted to invoke the x-ray mode that I’ve seen on various tutorials. When I tap the Navigator icon and then tap on either Main View Mode or Split View Mode, Designer crashes instantly.

I’ve tried with both the beta and mainstream app, getting the same result. I have also tried it with other files and it seems to work a little better.

I have found that if I use the Designer module within Affinity Publisher for iPad, with the same file, there is absolutely no problem.

I am attaching the file. You’ll see that it is not particularly large or complicated particular shapes. I was trying to combine using Shake Builder were the little houses (I was trying to replicate what the original artist had made, for practice).

I realise there is probably something weird about the file, but this crash shouldn’t really happen, I think.

cardch4.afdesign

[loukash]

https://forum.affinity.serif.com/index.php?/search/&tags=afd-6141
https://forum.affinity.serif.com/index.php?/search/&tags=AFD-6205

All likely the same issue.

[DM1]

19 hours ago, tbaucells said:

but this crash shouldn’t really happen,

I tried your file in Current Beta and can’t fault it.  Tried Split View with all sorts of combinations. Have you tried a hard reset of you iPad?

[loukash]

3 hours ago, DM1 said:

I tried your file in Current Beta and can’t fault it.  Tried Split View with all sorts of combinations.

In my aforelinked reports, it always crashes when the zoom reaches 200%.

[DM1]

10 hours ago, loukash said:

In my aforelinked reports, it always crashes when the zoom reaches 200%.

I went way past 200%. Maybe it is model specific? The M1 units have had issues that don’t effect older iPads.

[Dan C]

Hi @tbaucells,

Thanks for your report and our sincerest apologies for the delayed response here. We are exceptionally busy following the release of V2 and we thank you for your continued patience and understanding here.

I can confirm that this issue has since been resolved in the latest update (2.0.4) and should hopefully no longer occur.

If you're still experiencing issues with these settings or any other bugs in the latest update, please create a new post here and our team will be happy to investigate further