Launching iconify 2.0.2 immediately crashes Sketch 70.1 running on M1 mac about iconify-sketch

[cyberalien]

@digiklug Try 2.0.3, I think it might fix that bug.

[cyberalien]

Unfortunately I can't replicate that. There is nothing in plug-in that could crash Sketch. All it does at start is it retrieves saved configuration (if it exists) and opens a web view.

Safari could crash Sketch. It currently does crash Sketch when Safari is set to automatically close when closing plug-in, so there is something fishy going on in Sketch communication with Safari.

Can you check if attached plug-in crashes on your computer? It is a basic plug-in created from Sketch template, which uses same web view version (3.4.4) that is used by Iconify plug-in.

my-plugin-name.sketchplugin.zip

[jink3]

Hey, thanks for that. Yes, your plugin also crashed Sketch in the exact same way. I'm not really sure what the relationship with Safari is though, I don't use Safari at all on my laptop. Anyhow, hoping my confirmation of the crash helps in some way.

[cyberalien]

Sketch uses Safari to display user interface for plug-ins.

Thank you very much for testing, it helps a lot. It confirms that issue is with web view, not with Iconify plug-in. That plug-in is created with Sketch template using skpm create my-plugin --template=skpm/with-webview with sketch-module-web-view updated to version 3.4.4.

Can you post a Sketch crash log in skpm/with-webview#25 and any details you can think of? I think it might help developers figure out what's causing crashes.

[jink3]

Just posted there, thanks.

[digiklug]

this is the issue i see on big sur and version 70 in case it might help you

[cyberalien]

Thanks for report, it is a bug in plug-in, but it is different from this issue. I suspect its a bug that I've fixed in Icon Finder earlier today, but haven't pushed to Sketch plug-in yet.

I'll publish update soon.

[digiklug]

unfortunately not and now there is another issue

[cyberalien]

Thanks for reporting! Can't replicate it, but will try to figure it out. I've copied your post to #17 because this is a different issue from issue reported by @u-i-1.