-
-
Notifications
You must be signed in to change notification settings - Fork 6k
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
Crash: function signature specialization <Arg[0] = Owned To Guaranteed> of Charts.BarLineChartViewBase.calcModulus (Charts.BarLineChartViewBase)() -> (), line 444 #471
Comments
Are you crashing at Because this is the line 444 code of |
It works for most of the users. Just noticed this crash happened to one user 3 times... Maybe the user has some very specific set of data, not sure... |
then why xAxis has problem... |
Any ideas what |
Are they using the library from objective-c? This might be why https://forums.developer.apple.com/thread/6078 |
I see some crash on my side with |
Are those projects objective-c projects? |
I'm not sure who are you referencing to. I'm talking about one project I'm working on. We use both Swift and Objective-C. We use ios-charts library mainly from Objective-C. Also just to clarify: I'm talking about the crash reports I see in HockeyApp. It didn't crash to me with a debugger attached. And it happened just a few times. Unfortunately I don't have repro steps... My guess is that meybe the user has some specific data set... Posted it here in case anybody else gets the same crash, can find this thread to put more details in. |
The thread from the Apple dev forum I posted above seems to be talking about the same issue. Seems to be because of the swift/obj-c interoperability. I've never seen this issue but I use swift only. |
@petester42 thanks :) I've read that thread, still not sure what's the reason of the problem... Maybe in our case somehow that user gets some weird set of data... Will wait until we get more crashes and/or info about this. |
I would add some log for _xAxis.isEnabled and other suspect object to check if they are nil and you will have more knowledge what caused the crash |
I've started to seeing this kind of crash reports. Wondering if anyone else is getting this and/or have any thoughts why is it happening.
We were at 2.1.2 version of the library.
Thanks in advance!
The text was updated successfully, but these errors were encountered: