Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Charts in App Extension #2590

Closed
jack-blackson opened this issue Jul 9, 2017 · 4 comments
Closed

Use Charts in App Extension #2590

jack-blackson opened this issue Jul 9, 2017 · 4 comments

Comments

@jack-blackson
Copy link

Hey!

First of all, thanks for this great project and your work on it!

I am using your chart in my iOS app, and wanted to add them now too to a custom view of an app extension. Unfortunately, this leads to a warning at the moment:
"warning: linking against dylib not safe for use in application extensions"

As far as I found out, the reason for that is, that Apple seems to see Charts as one of the "Unavailable for App Extensions APIs" (see https://developer.apple.com/library/content/documentation/General/Conceptual/ExtensibilityPG/ExtensionOverview.html#//apple_ref/doc/uid/TP40014214-CH2-SW6)

Do you think there is a way to adjust the API, that it conforms with their requirements? Or is there any way to do this myself? This would be really great. If this warning appears, Apps will be rejected for App Store Review.

Thanks,
Jack

@liuxuan30
Copy link
Member

liuxuan30 commented Jul 17, 2017

double check your app as Charts does not link to any dylib, it must be your app's.
Can you do some research on what is marked as NS_EXTENSION_UNAVAILABLE but used in Charts?

I don't see Charts use anything else that is unavailable, except for that it does have one API to save chart images into cam roll. If this is the case, you can either delete or configure it in info.plist

@jack-blackson
Copy link
Author

This is quite strange - this is the error message I receive in xcode.
problem charts

@jack-blackson
Copy link
Author

Hey! It seems I fixed it..it was somewhere connected incorrectly in the app.

@pmairoldi
Copy link
Collaborator

seems resolved. closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants