-
Notifications
You must be signed in to change notification settings - Fork 1
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
Latest Xcode crashes after successful build with BarBack enabled #1
Comments
I can't reproduce this with the latest Xcode downloaded from developer.apple.com. Can you please provide more details?
|
iOS app |
Are you running on the device or in the simulator? Do you mind trying in the direct-download version of Xcode, in case I can't repro it in the MAS version? |
I don't recall but I believe simulator. |
OK, I've reproed this and I think I've got it mostly figured out: if the tab bar has never been made visible while the current document has been open, Xcode will crash when trying to run the project. Here's the backtrace, in case your link goes away: UNCAUGHT EXCEPTION (NSInternalInconsistencyException): Cannot remove an observer <NSKeyValueObservance 0x7fd23f0c5ba0> for the key path "currentLaunchSession.currentDebugSession.coalescedState" from <IDEExecutionEnvironment 0x7fd23e9224f0>, most likely because the value for the key "currentLaunchSession" has changed without an appropriate KVO notification being sent. Check the KVO-compliance of the IDEExecutionEnvironment class. |
…he window. If the titlebar is visible, NSThemeFrame winds up moving toolbar buttons to a new view within the same window. IDERunPauseContinueToolbarButton seems to have a bug when it gets -viewWillMoveToWindow: with the same window as it's already inside of. This method calls down to a helper that unregisters existing KVO notifications and then registers new ones; I can't see why this pattern is failing, but it's a scenario that titlebar-less Xcode doesn't hit, so I'm just going to squelch the -viewWillMoveToWindow: notification. Addresses issue #1.
Crash logs here.
The text was updated successfully, but these errors were encountered: