IB Designables: Failed to render and update auto layout status

怎甘沉沦 提交于 2019-11-28 18:42:38

I add this script at the end of my Podfile and performed pod install again. So I could build normally my project.

post_install do |installer|
    installer.pods_project.build_configurations.each do |config|
        config.build_settings.delete('CODE_SIGNING_ALLOWED')
        config.build_settings.delete('CODE_SIGNING_REQUIRED')
    end
end

I just had the exact same issue, and the only thing that worked for me was instead of using the main Bundle I had to get the Bundle for the Nib I wanted. Essentially changing:

Bundle.main.loadNibNamed("UserView", owner: self, options: nil)

To:

let bundle = Bundle(for: UserView.self)
bundle.loadNibNamed("UserView", owner: self, options: nil)

Which is bizarre, as in my case when comparing the two Bundles at runtime in LLDB they were identical (class name is different but the rest of my setup was identical to the OP)

Xcode 9.3, CocoaPods 1.5.3 It may be due to recent update on CocoaPods version. See issue here.

I had this error IB Designables: Failed to render and update auto layout status in the storyboard, the class STPPaymentCardTextField in Stripe SDK related to Cocoapods.

Solution is to downgrade your CocoaPods to 1.4.0.

sudo gem list cocoapods

sudo gem uninstall cocoapods

sudo gem install cocoapods -v 1.4.0

pod update

This question is related to this answer. Check both.
Failed to render instance of ClassName: The agent threw an exception loading nib in bundle

Bottom Line

Make sure that your xib file does not have any orphaned outlets. Check each view/element of the nib for an outlet and remove and re-add.

For me, they were orphaned outlets. It seems the nibs and IB are very finicky and the debugger doesn't give many details... if you can't get this to work, you might start with a fresh nib/xib file.


Walkthrough of my working code

This issue took me several days to resolve. For the benefit of others I am giving a verbose answer and showing all of my relevant code and connections.

A working commit where I implemented the fix action (above) is here: https://github.com/jfosterdavis/ZMAppFoundation/commit/6855f0d5b9cd1bc320395e57e2b271653ef7acd1

Xcode version 9.2

My file structure

Here is my file structure (note: I am creating a pod with cocoapods named ZMAppFoundation. Also, ZMPieTimerView.swift is not relevant to the solution.):

I want my nib to be viewable (IBDesignable) in the Main.storyboard file. Here is the File's Owner and Custom Class of my xib, ZMGauge.xib:

Code, implementations

Here is my ZMXibView class:

//  Adapted from https://medium.com/zenchef-tech-and-product/how-to-visualize-reusable-xibs-in-storyboards-using-ibdesignable-c0488c7f525d

import UIKit

@IBDesignable
open class ZMXibView: UIView {


    var contentView:UIView?
    @IBInspectable var nibName:String?

    override open func awakeFromNib() {
        super.awakeFromNib()
        xibSetup()
    }

    func xibSetup() {
        guard let view = loadViewFromNib() else { return }
        view.frame = bounds
        view.autoresizingMask =
            [.flexibleWidth, .flexibleHeight]
        addSubview(view)
        contentView = view
    }

    func loadViewFromNib() -> UIView? {
        guard let nibName = nibName else { return nil }
        let bundle = Bundle(for: type(of: self))
        let nib = UINib(nibName: nibName, bundle: bundle)
        return nib.instantiate(
            withOwner: self,
            options: nil).first as? UIView
    }

    override open func prepareForInterfaceBuilder() {
        super.prepareForInterfaceBuilder()
        xibSetup()
        contentView?.prepareForInterfaceBuilder()
    }
}

In storyboard, my xib is designated in the Custom Class. I am using cocoapods to develop a pod. I have explicitly selected the Module. (Note that in my XibView class, I have to define the nibName property.):

Don't Forget!

Then you may need to clean, close Xcode, rebuild, or simply wait a while for the IB to render it again. It is still a mystery to me exactly when Xcode will decide to try to render the IBDesignables, and I don't know of a way to force.

Success

Based on my code and the actions I took, my nib is now IBDesignable viewable in my Main.storyboard.

In case you missed it

In case you missed it, my solution is at the very top of this post. I got mine to clear the error cited by the OP by removing some orphaned IBOutlets.

(xCode 9.2, Swift 4) The following may not help your exact problem but may help others with a very similar problem. This was my error:

error: IB Designables: Failed to render and update auto layout status for CustomExampleView (XXXXX): the agent crashed

I was able to remove the error when deleting the CustomExampleView.xib and CustomExampleView.swift. To replicate, I then re-created the files, went to the .xib and set the top level view's custom class to CustomExampleView.

My mistake was setting the custom class to the top-level view on the .xib instead of setting the custom class on the File's Owner. After setting the proper custom class, my problem was solved.

For me, the fix came down to getting Interface Builder to redraw the object. I had this in two places and both were fixed by no changes to code but the symptoms of the agent error and the views being blank in storyboard was eventually fixed.

One was fixed by dragging a UIView to a different order under the View and rebuilding. A second in a TableView with Prototype cell was fixed by selecting the TableView, changing the count of Prototype cells to two, wait a sec, then change it back to one. The TableView, which had been a white blank, then drew all the elements correctly and the agent error was gone.

It feels like it's a bug with IB and from other searches, many solutions exist for the similar error. Hope this helps someone.

    post_install do |installer|
    installer.pods_project.build_configurations.each do |config|
        config.build_settings.delete('CODE_SIGNING_ALLOWED')
        config.build_settings.delete('CODE_SIGNING_REQUIRED')
    end
end

Entering the above-mentioned code in the Podfile solves the issues. This code just does away with the requirement of code signing for the installed framework via Cocoapods. But this seems to be a bug in IBDesignable too as using Xcode 10 bets 4 I don't get this bug due to new build system incorporated in Xcode 10.

I'm cringing at how dumb this is that doing what I'm about to tell you makes a difference, but you can try removing the breaking code out of

override func prepareForInterfaceBuilder() {

and only use it in

override func awakeFromNib() {

. I'm cringing, even more, when I report that its possible that your changes could still reflect in storyboard as desired when doing this.

You can identify the breaking code by commenting out all the lines and using a process of elimination to identify the breaking line.

Shaheryar Malik

It is the problem with some cocoa pods versions like 1.5.0. If you are using this one then it cause to rendering failed to move from current version to other run this commands in terminal

sudo gem uninstall cocoapods

You can install any specific version by mentioning like this

sudo gem install cocoapods -v 1.4.0

Hope it will works for you.

For me this problem solved by,

  1. Updating pods.
  2. Changing build setting to '$(inherited)' for swift libraries embedded option.
  3. Building, cleaning, building.
  4. Closing project.
  5. Quitting Xcode.
  6. Running again.

hahaha old hack :) Thanks!

Unfortunately, you can't use IBOutlets within a IBDesignable. Better answer for you here:

Live Render IBOutlet Connected Subviews Via IBInspectable Properties

Perhaps you wanted to have your UserView extend UIButton, rather than UIView?

I don't really know much about the cause of this, but I've seen this a couple of times and every time it's fixed by just restarting xcode. I think that's where everyone should start and if that doesn't work then you can try the other suggested answers.

I disabled the 'User trait Variations' and my problem was solved.

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!