No Assistant Results

Question

I am having an issue where the code associated with some of my View Controllers is not showing up in the Assistant Editor window to the right of the Storyboard. It says "No Assistant Results" where the swift code should be.

Things I have tried (There are many things):

Cleaning project
Deleting DerivedData
Creating new, identical View Controllers to see if the issue was just in those particular views.(the same issue occurred)
Deleting and Reinstalling Xcode
Restarting my Computer.

NOTE: I also am getting a warning at the top of the editor: Internal Error has occurred, source Editor functionality is limited.

http://stackoverflow.com/questions/28925078/xcode-6-3-no-assistant-results — Amit Jagesha シ, Jul 12 '16 at 13:15
@AmitJagesha That question unfortunately does not answer mine, none of the solutions work for me. I included in my question all the solutions I have tried, which are the proposed solutions on the other question. — Ryan Cocuzzo, Jul 12 '16 at 13:28
7.3.1, the latest. I just re-downloaded it to try and fix the problem — Ryan Cocuzzo, Jul 12 '16 at 13:30
can you provide zip of your code so we can test it in own xcode? — Amit Jagesha シ, Jul 12 '16 at 13:47
@AmitJagesha I am sorry but my project is almost submission-ready, so I would rather not. — Ryan Cocuzzo, Jul 12 '16 at 13:50
Temporary "solution": You can force a file into the assistant view by alt-clicking on it on the project navigator. — HAS, Jul 12 '16 at 16:56

Glenn Posadas · Answer 1 · 2022-06-04T18:03:19.917

47

Ok, I've had this problem before. I couldn't remember how I solved this so I searched on Google and found this question. But this time, nothing helped me. These are the things I did. I believe the last one solved this.

Clear Derived Data. Go to Terminal and enter this: rm -rf ~/Library/Developer/Xcode/DerivedData
Quit the whole Xcode.
Close all tabs of Xcode and make sure to view some class files instead of Interface builder and go try again viewing assistant results.
Remove the assigned class to the View Controller nib you think causes the problem, then assign the class again. Boom! Solved!

edited Jun 04 '22 at 18:03

answered Jan 05 '17 at 15:39

Glenn Posadas

12,555
6
54
95

This just helped me after refactoring - Xcode didn't build correctly and also didn't show the Assistant file... Seems to be an issue with the Xcode project file – brainray Jun 25 '20 at 11:55
4

Still happening in Xcode 12.0.1. Quittng xcode works. It's just sad how many annoying problems xcode has with adding/syncing files and this is the *12th* major iteration... – Govind Rai Oct 02 '20 at 16:13
Still happens in XCode 12.3. As above, closing and re-opening XCode and re-selecting the project fixes the problem. – SimonKravis Aug 04 '21 at 23:03
1

Closing and re-opening XCode didn't work for the latest instance of this problem but renaming the project folder (the one containing .xcodeproj file) did ... – SimonKravis Aug 12 '21 at 08:39
Quitting Xcode and reopening is resolving this for me in 13.3.1 but it is disappointing that Apple hasn't fixed this in their flagship IDE – John Harrington May 26 '22 at 19:36

score 37 · Answer 2 · answered Apr 07 '19 at 03:40

This method worked for me: (Xcode 10.2)

1- Select the broken ViewController on the StoryBoard

2- In Identity Inspector, change the item in Class to another class (any class)

3- Change the Class back to related class

4- Save and close the project

5- Reopen the project

score 35 · Answer 3 · answered Jul 03 '20 at 02:56

35

What worked for me was to close Xcode entirely, open again, and then I tried assistant.

answered Jul 03 '20 at 02:56

black

353
3
6

score 19 · Answer 4 · answered Oct 05 '20 at 07:57

19

Just do a simple close the app and open the app again. It worked for me

answered Oct 05 '20 at 07:57

arman

191
1
5

score 11 · Answer 5 · answered Mar 31 '22 at 13:02

11

Go to Assistant Mode on the upper right.

Click Command + Shift + T. New window will be opened and close the old one. You will be able to see something. Now go to Top Level Objects and select your file.

answered Mar 31 '22 at 13:02

user11894123

131
1
4

score 8 · Answer 6 · answered May 14 '20 at 08:04

Deleting derived data did not work for my problem. This is how I solved this when I encountered this issue,

Go to the file that contains your class, go to File inspector > Target Membership, and then make sure that there is a check mark in the target of your project.

I hope this solves your issue.

score 7 · Answer 7 · answered May 12 '21 at 10:36

7

Click option+alt and click on the view controller you want to present.

answered May 12 '21 at 10:36

ortalPozniak

131
1
3

Chris Birch · Answer 8 · 2017-07-16T15:49:54.163

Argh! This annoyance happens to me all the time.

I'm not 100% sure I know what the fix is, however I think I may have just "fixed" this a few seconds ago using the following voodoo:

1) Delete derived Data

2) Close xcode, reopen Xcode. Maybe Wait for indexing to finish?

3) View a source code file (.m,.h, .swift) in the main editor, the assistant editor should now show "Counterparts".

4) Change this to "Manual" rather than "Automatic"

5) Switch back to your nib/storyboard

6) Change back to "Automatic" rather than "Manual"

7) Probably continue pulling hair out :)

Edit

Seems as though maybe only step 3 is required as this happened again just now.

score 2 · Answer 9 · answered Sep 15 '17 at 15:21

I had this issue and was able to resolve it. I resolved it by viewing the storyboard as source. I then removed everything in and including the tags (Saving it to restore later). I then went back and viewed the storyboard normally and created a new ViewController. Once the new ViewController was on the storyboard the assistant editor acted as normal. I then went back and viewed the storyboard as source code once again and replaced the current tags with the one I removed previously. This resolved my issues hopefully it will help for you.

score 2 · Answer 10 · answered Jan 28 '20 at 14:55

2

For me (Xcode 11) it was cause by installing cocoapods, tried all the trick that I could find. Finally this helped me. Go to Xcode File Menu -> WorkSpace Settings -> enable legacy build systems

answered Jan 28 '20 at 14:55

M.Yessir

202
3
11

score 2 · Answer 11 · edited Feb 16 '21 at 17:22

2

The same problem happened to me. I only have to restart Xcode (12.2)

edited Feb 16 '21 at 17:22

Dharman

30,962
25
85
135

answered Feb 16 '21 at 17:16

Nguyễn Trí

41
1
1
4

score 2 · Answer 12 · answered Mar 28 '22 at 07:17

For any one who is encountering the same problem in Xcode version 13.3

Explanation: for me, the reason why it wasn't working is that I created a controller, view, and model Folder and I put the Main.storyboard inside the view folder and the viewController.swift inside the controller view, therefore when I try to access the assistant Result Xcode doesn't know where the viewController file is, so he is not able to connect between the storyboard file and the latter.

Solution: What worked for me is that I simply ran the app and it automatically connected the viewController with the storyboard.

I hope this was helpful.

score 1 · Answer 13 · answered May 11 '17 at 01:02

I don't know if this is still helpful or not, for what is worth, the way I managed to restore this when it's been working perfectly and all of a sudden it stopped is by changing Assistant Editor view-mode.

I usually have it in Assistant Editors at bottom, so just change it to whatever else, such as All Editors Stacked Vertically and go back, and it should be working ok now.

xcode 8.3.2, if it's any use.

Gary Z · Answer 14 · 2020-01-20T07:56:07.157

1

I tried various ideas mentioned here but nothing worked for me. So in the Project navigator, I right clicked on the .DS_Store file, clicked on Delete, and then chose "Move to Trash" on the confirmation prompt. After closing Xcode and opening it again, a new .DS_Store file was created. The Assistant Editor is working again and the .h and .m files appear in the Project navigator again. I am using Visual Studio for Mac which communicates with Xcode. Today I had to close and open both Visual Studio and Xcode after deleting the .DS_Store file.

edited Jan 20 '20 at 07:56

answered Jan 19 '19 at 02:11

Gary Z

155
2
6

Where was this .DS_Store file that you deleted? I'm using Xamarin as well and am facing the same issue. – Justin Jan 15 '20 at 17:20

score 1 · Answer 15 · answered Oct 11 '20 at 05:46

you may have changed the name of the .swift file after you connected your IB oulets and IB actions.

select main.storyboard and select your view controller. at the far right select identity inspector. check if the class name is the same name as your .swift file, if it is not you need to put in the file name and the assistant should show up now.

score 0 · Answer 16 · answered Oct 10 '17 at 07:52

0

In my case, the class name of File's Owner is incorrect (the class doesn't exist). I corrected the class name and it works again

answered Oct 10 '17 at 07:52

sweet-2

157
1
4

score 0 · Answer 17 · edited Aug 06 '19 at 21:03

0

Identity Inspector

Go to the view controller Identity Inspector (see the image). Change your controller to something incorrect, then change it back.

edited Aug 06 '19 at 21:03

Machavity

30,841
27
92
100

answered Aug 06 '19 at 20:44

gregory gadbois

1
1

Ricardo Montesinos · Answer 18 · 2020-03-10T14:28:27.607

0

I had the same problem and I realized that selecting the Outlets option in the top of the Assistant Editor View solves the problem.

In addition to this, I found that if your classes are in several groups for some reason Xcode losses the reference to the class.

edited Mar 10 '20 at 14:28

answered Mar 10 '20 at 14:09

Ricardo Montesinos

74
4

araferna · Answer 19 · 2020-06-24T00:57:46.123

0

I setup the folder for the derived data when I installed Xcode in a folder I deleted cleaning my disk! So I created a new folder and I assigned in locations as above. Thats it! I was cleaning a file that didn't exist.

edited Jun 24 '20 at 00:57

answered Jun 24 '20 at 00:52

araferna

71
1
5

score 0 · Answer 20 · answered Aug 10 '20 at 12:42

0

If the problem started after renaming the ViewController, first check whether you've changed the class name inside the ViewController file as well.

answered Aug 10 '20 at 12:42

2apreety18

181
3
8

score 0 · Answer 21 · answered Aug 28 '20 at 16:32

0

I have disabled xcode indexing, so after enabling indexing it starts working

answered Aug 28 '20 at 16:32

shmakova

6,076
3
28
44

score 0 · Answer 22 · answered Sep 23 '20 at 16:30

0

Faced same issue. For me it happen when I moved my view controllers to the new group. The solution was unfortunate, but at least it worked again - I just moved the files back to the origin folder.

answered Sep 23 '20 at 16:30

Valentin Minkovich

1
1

score 0 · Answer 23 · answered Oct 22 '20 at 11:37

In Xcode 12.x, this will happen if you rename your ViewController file after creating it. If this is the case, just simply delete that ViewController file, and create a new one with a file name that you will not change, and then the Assistant window should automatically populate.

score 0 · Answer 24 · answered Apr 06 '21 at 07:46

0

Please make sure that there is

no error in your project and your project is complining succesfully.

In my case, there was an error om some other class due to which I was not able to see assistant results.

answered Apr 06 '21 at 07:46

Ghulam Rasool

3,996
2
27
40

score 0 · Answer 25 · answered May 29 '21 at 06:52

0

After 7 imaginary hours, I finally found the answer. this is only for the storyboard for other people out there reading this is the answer if it does not help I don't care but here it is.

(This is an example project I cloned from GitHub)

Just select veiwcontroller.swift in the document outline, it should work.

Here is a screenshot.

Like i told, example project.

answered May 29 '21 at 06:52

Ishan Bhattacharyya

1
2

3

Please do not include pictures of code, instead paste the code in your answer. – C. Peck May 30 '21 at 04:15

score 0 · Answer 26 · answered Oct 04 '21 at 10:25

0

Had the same problem on Xcode Version 13.0 (13A233). As Glenn Posadas mentioned, deleting the derived data rm -rf ~/Library/Developer/Xcode/DerivedData then closing and re-opening the project solved the problem for me.

answered Oct 04 '21 at 10:25

Alexandros Tzimas

43
7

score 0 · Answer 27 · answered Nov 22 '21 at 11:11

0

I had the same problem, so I re-organized files in folders and it got fixed. If you have the file in a specific folder, please put it outside that folder.

answered Nov 22 '21 at 11:11

ee.bt

308
1
4
9

score 0 · Answer 28 · answered Feb 15 '22 at 12:07

Try this (XCode 13.2.1):

In Storyboard, select the object whose class definition you want to bring up in the assistant editor.
Delete the custom class in the Identity Inspector, being sure to press the return key to lock in the change.
Quit XCode and reopen.
Re-enter your custom class name in the Identity Inspector.

I tried all the suggestions above and this was the only thing that worked for me.

score 0 · Answer 29 · answered May 12 '22 at 16:23

0

Xcode 13.3.1

None of these worked but I did a clean and shut everything down and reopened and it worked.

answered May 12 '22 at 16:23

devjme

684
6
12

GreenAnt · Answer 30 · 2022-07-26T17:15:36.177

One reason for this happening is moving the swift file to a different folder. If I move the swift file out of the folder, the assistant view works again. If I move the swift file back into a folder, it fails again.

After trying several tricks mentioned here, this seems to have finally worked for me:

Close the project,
Rename the project folder in Finder (i.e. the folder containing the .xcodeproj file)
Double click the .xcodeproj file to open the project.

It seems that paths stored in local cache files can be stubborn about being updated.

l1ght80x · Answer 31 · 2022-11-08T19:09:34.360

0

I recently had this issue and the resolution was to:

Rename the class in your .xib file to anything other than what you have: [1]: https://i.stack.imgur.com/Xrbqc.png
Close Xcode
Reopen Xcode
Open the Assistant editor

If the issue persists, close Xcode again after renaming your .xib class back to the correct name and open it again.

Hope this helps!

edited Nov 08 '22 at 19:09

answered Nov 08 '22 at 19:07

l1ght80x

1
1

score 0 · Answer 32 · answered Jan 25 '23 at 00:55

0

I just took the current ViewController and copied its contents to another view controller and created a new File for the controls and connected it.

answered Jan 25 '23 at 00:55

Jaylen Davis

1

score -1 · Answer 33 · answered Oct 16 '21 at 22:10

There must be a bug in Xcode. I am learning how to use it and have noticed a few bugs. In order to fix this:

Click the View Controller you are having issues with.
Click on the ID card (The Identity Inspector) in the inspector pane.
Under Custom Class, next to class, type in the class you want to connect it too.
Then save your project and close it out.
Reopen your project.

The assistant editor should pop up and be working. This happens every time I click it and click out of it. It's quite annoying.

score -2 · Answer 34 · edited Nov 13 '20 at 03:38

-2

Just add your UIViewController in Identity Inspector just like this:

edited Nov 13 '20 at 03:38

אורי orihpt

2,358
2
16
41

answered May 22 '17 at 12:56

Gowtham Sooryaraj

3,639
3
13
22

score -2 · Answer 35 · answered Jan 01 '21 at 08:50

-2

The problem for me was that I had unselected the Target Membership. Undoing (Cmd Z) didn't help.

Go to Source Control > Discard all changes.

Hopefully you use source control and commit frequently. Otherwise this lesson will teach you do so...

answered Jan 01 '21 at 08:50

Raphael Pinel

2,352
24
26

score -2 · Answer 36 · answered Jul 05 '23 at 02:28

-2

1- Select the broken ViewController on the StoryBoard

2- In Identity Inspector, change the item in Class to another class (any class)

3- Change the Class back to related class

4- Save and close the project

5- Reopen the project

answered Jul 05 '23 at 02:28

sơn nguyễn

7

1

This is a repost of an answer posted more than 4 years ago. – HangarRash Jul 05 '23 at 02:38

No Assistant Results

36 Answers36