CoreSVG is a private framework

[lapfelix]

The switch from SVGKit to CoreSVG seems to be a little dangerous.

Specifically, all of these functions and method declarations are private and since the framework is private, Apple could change their method/function signature in an upcoming iOS/macOS update without any warning. It could also lead to apps being refused from the App Store since using private APIs isn't allowed.

[dreampiggy]

Until we have another choice. Actually.

In next release, I'll encrypt all the private API call without the stringify symbol, which can avoid potential issue. I'll do this in hours.

For exist SVGKit integration, you can always using SDWebImageSVGKitPlugin. It's here and does not disappear.

The reason is simple:

SVGKit is not a Stable Framework and Maintainer is not able to drive that forward development. So, we as a downstream dependency, can not rely on that framework. That's the question.