I've just experienced this problem and the issue seems to stem from using kCGImageDestinationLossyCompressionQuality (or maybe options in general). Using nil instead resolved the issue for me, but that's less than ideal.