Error in Xcode 6 - view controller does not have an outlet named (subview)

Question

I just got this error in one of my apps, and after checking some other apps the same error is happening. None of my IBOutlets and IBActions are con

Answer 1

Try to add the header file to the project, if it's missing.

Answer 2

Xcode 6.3.2. Similar issue. A project(s) that i've been working on suddenly 'disconnects' IBOutlets and shows the error

view controller does not have an outlet named (subview)

The project still builds and works and if you hover over the IBOutlets in code it thinks there are still connected.

I've nailed this down (at least in my case) to an issue with storing projects on dropbox (similar to an above post). The fix for me was super easy:

Drag the project folder off of dropbox to your desktop. Then drag the project back into dropbox.

This solution has fixed numerous projects with the issue.

Answer 3

I updated my project from Xcode 6.x to Xcode 7.x about two months ago without any issues. But then this morning I ran into this bug. I tried pretty much everything on this page but nothing worked. But then Justin Middleton's solution gave me an idea.

When I switched my project from the 10.9 SDK to the 10.11 SDK, I decided I wanted my code to remain backwards compatible just in case I had to revert back to Xcode 6.2. So I put Preprocessor code around several of my object declarations, e.g.:

// This caused the (!) problem in Interface Builder

#if( MAC_OS_X_VERSION_MAX_ALLOWED > MAC_OS_X_VERSION_10_10 )
@interface CLChatWindowController : NSObject <WebPolicyDelegate, WebUIDelegate, WebFrameLoadDelegate>
#else
@interface CLChatWindowController : NSObject
#endif
...


// Removing all the Preprocessor code fixed the problem

@interface CLChatWindowController : NSObject <WebPolicyDelegate, WebUIDelegate, WebFrameLoadDelegate>
....

Once I removed all the Preprocessor code, the (!) characters in Interface Builder disappeared and everything went back to normal. Hope that helps someone.

Answer 4

I had the same problem, changed the class under identity Inspector > Custom Class to something else, saved it and then set it again to the correct one, after doing that the connections appeared normally.

Answer 5

@robb actually discovered the fix for this, but the issue he found was that the group in the project that mirrored a folder on disk used a different case.

So if the project group was Broken/classone.m

and on disk it was broken/classone.m

Interface builder could not find the files. Renaming either the group or the folder to match case resolved the issue.

Answer 6

I had this in Xcode 7.0.1 on a swift project. Specifically, tableview cell connections were broken (permanently) while other things still worked. Deleting derived data, rebooting etc - nothing worked.

My solution ended up being:

1. Close xcode project
2. Delete derived data for project (Window->Projects)
3. Rename the entire project/source folder, ie. project -> project-1
4. (Update source-management bookmarks like sourcetree as required)
5. Open project in xcode (from finder): notice that the storyboard and a few other files are in red. Delete the references, re-add them. Boom, it works.

Note that deleting the reference to the storyboard and readding it, even with deleted derived data, was not enough. The rename of the entire source folder was necessary for me.