Xcode 6.3 freezes/hangs after opening XIB file

IosXcodexcode6.3

Ios Problem Overview


After upgrading to Xcode 6.3 (release version), Xcode now freeze every time I open a XIB/Storyboard file that includes an IB_DESIGNABLE view that uses a custom font for any projects and includes a custom font (not necessarily to have reference to that font in that XIB/Storyboard). The freeze occurs after opening the .xib file and then attempting to switch to any other file. Xcode hangs and must be force quit.

I have opened a bug report with Apple. (Bug 20483867).

Right now, I have two work arounds.

  1. Download and use Xcode 6.2 from Apple.
  2. Remove the IB_DESIGNABLE tags from the custom view header files.

This is likely an Apple bug, but does anyone have a better work around or solution?

Ios Solutions


Solution 1 - Ios

I've already suggested an edit for a more accurate description.

It only happens when your project contains a custom font. It'll freeze just by visiting any Storyboard/XIB that contains an IBDesignable custom view, not even referencing to that font in your Storyboard/XIB.

My workaround is to use have an older version of Xcode also installed (Xcode 6.3 beta or Xcode 6.2) and use that to update your Interface Builder files, and never open it in 6.3. open those Storyboard/XIB in a new window in Xcode with option+shift+click the file in the project tree.

Whenever you encounter the freeze, I use this command to clear the saved state just for that project.

rm -rf YourProject.xcodeproj/project.xcworkspace/xcuserdata

Solution 2 - Ios

Xcode 6.3.1 fixes the problem with custom fonts and IB_DESIGNABLE views in a Storyboard. Update via the Mac App Store, and you should be good.

Solution 3 - Ios

Response from Apple: Link to Developer Forums on Apple

> Thank you all for your reports. We are tracking this on our end and working hard to resolve it. Unfortunately we don't have a great workaround, but here are two options to get you going:

> If Xcode is hanging on launch because a storyboard/XIB using a custom font/IBDesignable was previously open: remove the "UserInterfaceState.xcuserstate" file inside the xcodeproj of the project you are opening, it would be at a path like this: My App.xcodeproj/project.xcworkspace/xcuserdata/yourusername.xcuserdatad/UserInterfaceState.xcuserstate

> If you really need to edit the storyboard/XIB file containing the custom font with Xcode 6.3:

> 1. Make a copy of your storyboard/XIB file as a backup > 2. Open the storyboard/XIB file in a text editor > 3. Remove XML tags named "fontDescription" that reference your custom font, for example: . Removing this tag will revert the font to the standard system font. > 4. Make outlets to the objects using the custom font and at runtime set the font of those objects to your custom font, for example in an override of viewDidLoad or awakeFromNib on your view controller

> IMPORTANT NOTE: we never recommend hand editing storyboard/XIB files. However we recognize this issue is preventing many of you from editing your documents and wanted to provide a workaround with the caveat that any hand editing may result in corruption of your document.

Solution 4 - Ios

Same problem for me. Removing IB_DESIGNABLE fixes the problem.. Going back to 6.2 doesn't work for me as I'm testing apps on device with iOS 8.3 - Xcode 6.2 can't run apps on devices with iOS 8.3 :(

Solution 5 - Ios

Another workaround is to change the file extensions to all of your font files and load the changed file names from Info.plist. This way you can keep IBDesignables and still use your custom fonts, but wont be able to see them in the Font Picker in Interface Builder.

All custom fonts that were peviously set from Interface Builder will continue to work, but in order to change them or to set another custom fonts, you will have to do it either from code or to modify the Storyboard or Nib files from text editor in order to set the font name.

Solution 6 - Ios

I don't have an answer but found out that simply force-quitting and restarting will re-launch Xcode in the exact same situation. To just be able to restart Xcode, remove the folder ~/Library/Saved Application State/com.apple.dt.Xcode.savedState.

Solution 7 - Ios

This bug has been fixed in the 6.4 Xcode beta that came out today. Go to the dev center and log in to download it.

Solution 8 - Ios

Xcode 8.1 - if you have a view with Navigation (in my case it was top Bar opaque Navigation Bar), just try to set property "top Bar" to None.

Solution 9 - Ios

As a workaround,I just commented out all the @IBDesignable markup in my handful of custom components that use this. When I did that, yes I lose ability to tweak the settings in Interface Builder, but it allowed me to at least open the .xib files w/out XCode crashing.

I will simply un-comment those @IBDesignable lines when Apple comes up w/ a fix.

Solution 10 - Ios

@O. Kurnenkov's answer worked for me. It didn't have anything to do with IB_Designable nor custom fonts, Cocoapods, etc.

For some reason having an "Opaque Navigation Bar" causes the nib file (it doesn't seem to affect storyboards) to constantly change y position; this can be seen in the Size Inspector where the y position will flicker between 0 and 64. This is happening to me with Xcode 8.2 (8C38).

enter image description here

My guess here is that this causes Xcode to constantly update the layout thus draining resources and causing it to hang/freeze.

enter image description here

The solution is to use any of the "Translucent" options, Inferred, or None.

Hope this helps!

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionpiccianoView Question on Stackoverflow
Solution 1 - IosJames TangView Answer on Stackoverflow
Solution 2 - IosJosh BrownView Answer on Stackoverflow
Solution 3 - IospiccianoView Answer on Stackoverflow
Solution 4 - IosDenis KildishevView Answer on Stackoverflow
Solution 5 - IosKoCMoHaBTaView Answer on Stackoverflow
Solution 6 - IosBart van KuikView Answer on Stackoverflow
Solution 7 - IosChristian A. StrømmenView Answer on Stackoverflow
Solution 8 - IosO. KurnenkovView Answer on Stackoverflow
Solution 9 - Iosuser871177View Answer on Stackoverflow
Solution 10 - IosLuisCienView Answer on Stackoverflow