-
Notifications
You must be signed in to change notification settings - Fork 53
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 when using Pod, working fine if copied to project. #8
Comments
Obviously, the error is that 'view' is called on e.g. an NSLock. The question I cannot answer is why. |
I'm having the same problem (thanks rasmuslp BTW, I'd never think of that :D). Works fine when copying, but not with Cocoapods. Any idea why? |
No, unfortunately not. I just begun on my Obj-C adventure, and hence doesn't have much experience yet. For now I just copied the files to the project, although I do expect to get it solved some day and use Cocoa Pods instead. |
Are you using version 0.0.2? |
Yes, this was with 0.0.2. |
Just wanted to chime in and say I am seeing the same thing. I haven't had time to diagnose yet since I am working against a deadline, but hope to look into the issue later. |
Yup, same thing here using latest HEAD |
Hmm... I had crashing too when using the pod... I moved the following code into the main initWithViewController: method and it works fine.
here's a diff, not sure if that helps
my guess is that _viewController is being released or reassigned before it's ever used (??) |
Fair warning: I'm new to Obj-C and all that it entails.
I have made a minimum example here using CocoaPods: https://github.com/rasmuslp/AXStatusItemPopupCrash
Just download zip, open workspace, build/run, and press on cloud in menubar.
For me, this stalls on line 161:
With the message
Sometimes, instead of NSLock, I get the error on the runloop queue:
If I remove the Pod of AXStatusItemPopup, and add the two files to the root group of the project, then it works like expected. Hence, it seems to be related to the podspec or a consequence thereof.
Any idea whats going on here ?
The text was updated successfully, but these errors were encountered: