ChartViewBase.saveToCameraRoll() accesses the photo library (obviously.) While a nice feature, Itunes Connect now* insists that an NSPhotoLibraryUsageDescription key should be added to Info.plist. And adding it and not actually having functionality that accesses photo library may cause problems with review.
Most people probably don't need this functionality, so maybe it should be conditionally-compiled and off by default.
*note sure how recent this is, I just grabbed this branch for the Swift 3.0 update, but it is a real problem.
7macaw
All 10 comments
hmm.. where it says it will be a review problem if you had functionality but not using it?
liuxuan30
on 18 Sep 2016
Agreed, my app was just rejected after updating to the Swift 3 version of the library and submitting with Xcode 8. Took me a while to figure out which library was causing the issue.
_This app attempts to access privacy-sensitive data without a usage description. The app's Info.plist must contain an NSPhotoLibraryUsageDescription key with a string value explaining to the user how the app uses this data._
Given I (and potentially many other users of the library) don't use this feature it would be nice to not have to add this key to my info.plist.
AshRobinson
on 18 Sep 2016
Well it's a feature, and Apple probably detects it's existence in the code.
It's not easy to allow you to choose whether to contain this piece of code or not - we could maybe enable/disable it based on macros.
If there are other suggestions - please put it in here. We'll vote!
danielgindi
on 18 Sep 2016
Yes I'm not actually sure the best way around it, I guess it's not too much hassle to add the key to the info.plist. It might just be worth adding a note in the readme as it took me a while to realize it was Charts causing the issue.
AshRobinson
on 18 Sep 2016
I didn't say it _will_ cause problems in review, but that it may. Apple is finicky about these things at times. And it is already annoying - we either have to go into the library code and take out the feature, or set a dummy NSPhotoLibraryUsageDescription string.
I think not enabling it unless a macro is defined should be a could solution.
7macaw
on 18 Sep 2016
If i can suggest a more drastic but (imho) cleaner approach, i would simply remove the feature.
After all, it's only a simple wrapper around calling UIImageWriteToSavedPhotosAlbum, we already have an UIImage object by calling getChartImage and it's the client app's responsibility to deal with it in whatever way best suits its needs.
ezamagni
on 18 Sep 2016
@ezamagni I tend to support your view
danielgindi
on 21 Sep 2016
I agree too. Saving to camera roll is a very platform dependent thing which dosen't make much sense in a cross platform library. Outputting an NS/UIImage is fine I think.
pmairoldi
on 22 Sep 2016
Turns out Apple (automated) Review fails for NSPhotoLibraryUsageDescription even if it's in InfoPlist.strings, something going on there with this specific key. Other apps, no relation to Charts, fail to upload to Apple.
I'm removing this method anyway.
danielgindi
on 23 Sep 2016
Well then, as you decided to remove this method how do we find the path to the camera roll?
Thank you!
(For now, I am using the same method as before, using UIImageWriteToSavedPhotosAlbum after getChartImage, but it doesn't work setting transparency to true at getChartImage)
1397v
on 10 Oct 2017
Related issues
anhltse03448
路
3Comments
newbiebie
路
3Comments
coop44483
路
3Comments
Shunshine07
路
3Comments
guanyanlin
路
3Comments
Most helpful comment
If i can suggest a more drastic but (imho) cleaner approach, i would simply remove the feature.
After all, it's only a simple wrapper around calling
UIImageWriteToSavedPhotosAlbum, we already have an UIImage object by callinggetChartImageand it's the client app's responsibility to deal with it in whatever way best suits its needs.