Home/ Questions/Ways to resolve the error - this class is not key value coding compliant for the key
Next
In Process
Mohamed Morin
  • 15
Asked: 2022-05-17T13:08:11+00:00 In:

Ways to resolve the error – this class is not key value coding compliant for the key

  • 15

. Advertisement .

..3..

. Advertisement .

..4..

I get the “this class is not key value coding compliant for the key” issue when trying to link a UILabel with an IBOutlet. Here is the detail of the error I got the error message:

*** Terminating app due to uncaught exception 'NSUnknownKeyException', reason: '[<UIViewController 0x6e36ae0> setValue:forUndefinedKey:]: this class is not key value coding-compliant for the key XXX.'

Please give me some advice to solve this problem.

♦ Suggestions of ITtutoria Team

This is the error that you are making

NSUnknownKeyException', reason: '[<UIViewController 0x3927310> setValue:forUndefinedKey:]: this class is not key value coding-compliant for the key string.

Possible causes of this error:

  • Bad Outlet

You either removed, or renamed the outlet name in your .h file. It can be removed in the .xib and .storyboard files’ Connection Inspector.

  • Extension of UIView using bindable property and setting values for those bindable attributes (i.e. shadow, corner radius etc.) Those properties were removed from UIView extension. However, the following <userDefinedRuntimeAttributes> remained unchanged in xml (of foo.storyboard).

Solution:

Right-click on foo.storyboard > Open As Source Code > Search by KeyPath (i.e. ShadowRadius > Delete the </userDefinedRuntimeAttributes> causing the problem

compliant for the key
Share

1 Answer

  1. Your xib may be experiencing a poor connection.

    This error has happened to me many times. TechZen’s solution is correct in this instance. However, there is another common cause: changing the name of an IBOutlet property within your.h/.m that you have already connected to File’s owner in the nib.

    From your home:

    1. Click on the object you want to view in IB, then go to the “Connections Inspector”.

    2. Check under ‘Referencing Outlets’ to make sure your object isn’t still linked to an old property name. Click the small x’ to delete this reference and rebuild again.


      this%20class%20is%20not%20key%20value%20coding%20compliant%20for%20the%20key

    If you use Storyboard, another common problem is that your UIButton may have multiple assignings. (Solution works almost exactly the same way as nib).

    1. Right click on the UIButton in your storyboard.

    2. This button has more than one assign/ref. You can remove one of the “Main …” greyed Windows with the small “x”.


      this%20class%20is%20not%20key%20value%20coding%20compliant%20for%20the%20key

    • 17

Leave an answer

You must login to add an answer.

Need An Account,