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

xcode10.2,swift5,chart version 3.3.0 #3948

Closed
Mosaics opened this issue Apr 17, 2019 · 3 comments
Closed

xcode10.2,swift5,chart version 3.3.0 #3948

Mosaics opened this issue Apr 17, 2019 · 3 comments

Comments

@Mosaics
Copy link

Mosaics commented Apr 17, 2019

archive error:

Undefined symbols for architecture armv7:
"method descriptor for Charts.ChartViewBase.initialize() -> ()", referenced from:
nominal type descriptor for aa.xxxView in xxxView.o
ld: symbol(s) not found for architecture armv7
clang: error: linker command failed with exit code 1 (use -v to see invocation)

@Mosaics Mosaics changed the title xcode10.2,swift5 xcode10.2,swift5,chart version 3.3.0 Apr 17, 2019
@liuxuan30
Copy link
Member

liuxuan30 commented Apr 24, 2019

I can archive ChartsDemo-iOS with generic iOS device without issue:
image

so you better check your build settings.

@DTown
Copy link

DTown commented Sep 2, 2019

@Mosaics
Did you solve this by editing the settings?
I get the exact same message with xCode10.3 and after switching to 3.3.0 & Swift5.
I cleared everything, also reinstalled my pods completely new but still have this message on archiving.
I do not have very special build settings, that should cause this.

Undefined symbols for architecture armv7:
"method descriptor for Charts.ChartViewBase.initialize() -> ()", referenced from:
nominal type descriptor for XXX.XXXXXXXView in XXXXXXXView.o
ld: symbol(s) not found for architecture armv7

@DTown
Copy link

DTown commented Sep 4, 2019

OK, what finally helped was the hint here in this ticket:
#3976 (comment)

For now I have changed "internal" to "open" in all this initialize functions, that are based on "ChartViewBase" class. If this is really releated to an swift bug, maybe Swift 5.1 might get rid of this. Tested 5.0.1 and 5.0.2 and this did not help.

My setup:

  • xCode10.3
  • Charts version 3.3.0
  • Swift5
  • CocoaPods package manager

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