LiteralStringKeyPath is triggered for Core Animation Key-Value Coding Extensions (no easy solution here)

[Ben Asher]

There aren't any selectors available for these keys/key paths, so we can't fix this rule by doing the usual NSStringFromSelector(@selector(keyPath)).

Core Animation Key-Value Coding Extensions

Example case that would trigger this warning:

[CABasicAnimation animationWithKeyPath:@"transform.translation.x"];

I think a good solution for this rule would be to ignore key paths that contain keys from the Core Animation Key-Value Coding Extensions.

[Ben Asher]

This is also triggered in similar cases for uses of UIMotionEffect and its subclasses

[Ali Rantakari]

Thanks for reporting this. A fix will be included in the next release.

[Ben Asher]

Awesome. Thanks!

[Ali Rantakari]

Fixed in v1.3