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

Crashing on CLLayer position contains NaN #105

Open
nnhubbard opened this issue Jul 11, 2016 · 7 comments
Open

Crashing on CLLayer position contains NaN #105

nnhubbard opened this issue Jul 11, 2016 · 7 comments

Comments

@nnhubbard
Copy link

nnhubbard commented Jul 11, 2016

I have been getting some crash reports that show the following:

Fatal Exception: CALayerInvalidGeometry
CALayer position contains NaN: [nan -48.5]

Is there a reason it would be returning NaN? And is there a way I can detect this?

@nnhubbard
Copy link
Author

nnhubbard commented Jul 11, 2016

I actually added the following check, but I still get the error:

// now set the *actual* anchor point for our layer so that our "popup" animation starts from this point.
if (isnan(anchorX) || isnan(anchorY)) {
        return;
}
CGPoint anchorPoint = [layer convertPoint:CGPointMake(anchorX, anchorY) toLayer:self.layer];

@nfarina
Copy link
Owner

nfarina commented Jul 13, 2016

Hm that's weird - can you reproduce this issue in the sample project?

@nnhubbard
Copy link
Author

No I can't. I just get crash logs through Crashlytics about it. I have been getting them since we launched our app in December.

@zapsleep
Copy link

zapsleep commented Feb 7, 2017

Hi! I get these crashes as well.
@nnhubbard Have you found what's causing it?

@nnhubbard
Copy link
Author

@grusha No, have never figured it out. I still get the reports on Crashlytics but cannot reproduce.

@a8695363
Copy link

@grusha No, have never figured it out. I still get the reports on Crashlytics but cannot reproduce.

No I can't. I just get crash logs through Crashlytics about it. I have been getting them since we launched our app in December.

@grusha No, have never figured it out. I still get the reports on Crashlytics but cannot reproduce.

@nnhubbard HI,Have you found what's causing it now?

@nnhubbard
Copy link
Author

No, still never found the cause.

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

4 participants