AnnieBro Posted December 14, 2023 Posted December 14, 2023 (edited) EDIT: I was about to record the problem and this time it didn’t happen? I had the issue two days ago and now I tried with File/Place… and by dragging from my Files into the program, but it wasn’t crashing, it was working fine and I could edit the SVG and everything. I’ll update in case it happens again. Hello! I am using iPad Pro 12.9" 2018 and I imported an SVG into a file I was working on (a branded T-shirt) in Affinity Designer, the most recent update. I had no trouble when I added the SVG, until I decided to edit the SVG itself (double tap, you know, like a smart object). When I wanted to go back to the original file, it just crashes the program, causing it to close. I try opening it in Photo - again crash. It’s like it got corrupted. I open it through Files - again, crash. After trying to understand what got it "corrupted", it was importing the SVG into the file. If I separately open the SVG and copy the vector layers into another file, there is no problem, but if I import it as an SVG like a smart object into the file, it crashes it once I exit the file and try to reopen it. I’ll edit this forum post shortly so I can add a video example of what happens for further elaboration. I would love a fix to this issue as it sabotages my workflow and corrupts perfectly fine files. I have no issue opening those same files on the laptop, but I’ve been having some minor technical difficulties with my laptop which kind of force me to use the iPad. Edited December 14, 2023 by AnnieBro Quote
Staff NathanC Posted December 14, 2023 Staff Posted December 14, 2023 Welcome to the forums @AnnieBro, This is a known iPad 2.3 bug currently logged with the developers as a priority and will hopefully be fixed soon, I'll bump the existing issue with your report. Quote
Staff Affinity Info Bot Posted January 3, 2024 Staff Posted January 3, 2024 The issue "[iOS] Files containing SVGs crash on open" (REF: AF-1413) has been fixed by the developers in internal build "2.3.1.2212". This fix should soon be available as a customer beta and is planned for inclusion in the next customer release. Customer beta builds are announced here and you can participate by following these instructions. If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.