xcode 6 assistant editor Automatic results will not display
I can not drag anything to the code from the storyboard. Files were in assistant editor under automatic but now there gone how do i get them back other then deleting and recreating them? Opening them up under manual it will come up but Xcode can't find the referance when dragging to the code and i get the error when naming it.
ios xcode editor assistant
add a comment |
I can not drag anything to the code from the storyboard. Files were in assistant editor under automatic but now there gone how do i get them back other then deleting and recreating them? Opening them up under manual it will come up but Xcode can't find the referance when dragging to the code and i get the error when naming it.
ios xcode editor assistant
add a comment |
I can not drag anything to the code from the storyboard. Files were in assistant editor under automatic but now there gone how do i get them back other then deleting and recreating them? Opening them up under manual it will come up but Xcode can't find the referance when dragging to the code and i get the error when naming it.
ios xcode editor assistant
I can not drag anything to the code from the storyboard. Files were in assistant editor under automatic but now there gone how do i get them back other then deleting and recreating them? Opening them up under manual it will come up but Xcode can't find the referance when dragging to the code and i get the error when naming it.
ios xcode editor assistant
ios xcode editor assistant
asked Oct 22 '14 at 16:59


dscrowndscrown
316417
316417
add a comment |
add a comment |
6 Answers
6
active
oldest
votes
The most common cause is a mismatch between your class name and the name registered in the identity tab of the view controller. This will happen if you for example rename your class but don't update the classname in the storyboard.
To set/check the class name, open the storyboard and click on the leftmost icon in the titlebar of your UIViewController. Then open the identity inspector in the utility pane (right side) and double check the name given as the custom class.
This worked for me. I added the Custom Class name for the storyboard. But my class doesn't show up in the automatic results in the assistant editor. However now I am able to create the outlet for the label.
– Ronald Randon
Nov 1 '15 at 17:12
I have a whole bunch of xibs where it doesn't automatically load the associated file. Some it does. I have all theClass
properties set as you suggested.
– toast
Nov 19 '16 at 10:12
add a comment |
I don't know if anyone else is still having this issue, but I get it a few times a week on Xcode 6.1.1 and I usually do the following to fix it (once I have checked that there are no class name mismatches):
- Clean build
- Delete Derived Data (using Organiser)
- Force Quit Xcode
- Re-open and Build
I know this is crazy, but it continues to work for me o_O
1
I was forced to do this after renaming a CustomViewController.m to CustomViewController.mm, only this worked. :)
– Corwin Newall
Jun 23 '15 at 0:58
Yuppi it's worked :D seems like derived data mess up.
– mert
Dec 11 '15 at 14:59
Worked on Xcode 7.3 as well.
– leanne
Apr 28 '16 at 19:28
I tried a bunch of these recommended fixes but this one was the one that worked. if you turned off indexing, turn it back on before attempting this fix. Your associated files will only show up after Xcode is done indexing.
– Trig3rz
May 30 '16 at 15:16
2
I encountered the same issue again today. These steps did not work until I clicked "Top Level Objects" instead of "Automatic". When I did that, something indexed at the top and then I clicked "Automatic" and bam...there was my viewController :)
– Adrian
May 29 '17 at 22:29
|
show 1 more comment
The issue is due to not completion of indexing - so there are few alternatives, that you can try for-
Way 01 : Check if indexing is showing in processes - then let it complete. Then, close the editor and reopen it
Way 02 : Just perform the clean action. It will start showing appropriate Viewcontrollers.
Way 03 : This is the most effective way - Just perform "Build" and then restart editor - it will surely going to work.
Thanks, this worked.
– nenchev
Aug 15 '17 at 15:56
I can tell that this did not work for me. The "Automatic" option is disabled and if I use "Manual", then Xcode complains. I have a regular Storyboard based project in Xcode 10 and Swift 4.2. Sometimes it works, sometimes it doesn't. Right now I can't figure out how to make it work again.
– Alex
Nov 9 '18 at 17:47
add a comment |
I had the same problem, and I managed to solve it by selecting the correct Target on the File Inspector of both files (Swift and XIB in my case, you can check the file inspector in the storyboard).
It can happen if your project has a lot of targets (mine had a few, the file was checked on the wrong one).
add a comment |
You'll want to turn XCode indexing 'on' and set the Assistant editor to “Automatic”. This helped in my situation when the other suggested answers didn't. Details on turning on indexing at Stopping xcode from indexing
add a comment |
I just deleted build folder completely.And it works for me!
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f26512966%2fxcode-6-assistant-editor-automatic-results-will-not-display%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
6 Answers
6
active
oldest
votes
6 Answers
6
active
oldest
votes
active
oldest
votes
active
oldest
votes
The most common cause is a mismatch between your class name and the name registered in the identity tab of the view controller. This will happen if you for example rename your class but don't update the classname in the storyboard.
To set/check the class name, open the storyboard and click on the leftmost icon in the titlebar of your UIViewController. Then open the identity inspector in the utility pane (right side) and double check the name given as the custom class.
This worked for me. I added the Custom Class name for the storyboard. But my class doesn't show up in the automatic results in the assistant editor. However now I am able to create the outlet for the label.
– Ronald Randon
Nov 1 '15 at 17:12
I have a whole bunch of xibs where it doesn't automatically load the associated file. Some it does. I have all theClass
properties set as you suggested.
– toast
Nov 19 '16 at 10:12
add a comment |
The most common cause is a mismatch between your class name and the name registered in the identity tab of the view controller. This will happen if you for example rename your class but don't update the classname in the storyboard.
To set/check the class name, open the storyboard and click on the leftmost icon in the titlebar of your UIViewController. Then open the identity inspector in the utility pane (right side) and double check the name given as the custom class.
This worked for me. I added the Custom Class name for the storyboard. But my class doesn't show up in the automatic results in the assistant editor. However now I am able to create the outlet for the label.
– Ronald Randon
Nov 1 '15 at 17:12
I have a whole bunch of xibs where it doesn't automatically load the associated file. Some it does. I have all theClass
properties set as you suggested.
– toast
Nov 19 '16 at 10:12
add a comment |
The most common cause is a mismatch between your class name and the name registered in the identity tab of the view controller. This will happen if you for example rename your class but don't update the classname in the storyboard.
To set/check the class name, open the storyboard and click on the leftmost icon in the titlebar of your UIViewController. Then open the identity inspector in the utility pane (right side) and double check the name given as the custom class.
The most common cause is a mismatch between your class name and the name registered in the identity tab of the view controller. This will happen if you for example rename your class but don't update the classname in the storyboard.
To set/check the class name, open the storyboard and click on the leftmost icon in the titlebar of your UIViewController. Then open the identity inspector in the utility pane (right side) and double check the name given as the custom class.
answered Jan 20 '15 at 15:33


oflibaeroflibaer
13624
13624
This worked for me. I added the Custom Class name for the storyboard. But my class doesn't show up in the automatic results in the assistant editor. However now I am able to create the outlet for the label.
– Ronald Randon
Nov 1 '15 at 17:12
I have a whole bunch of xibs where it doesn't automatically load the associated file. Some it does. I have all theClass
properties set as you suggested.
– toast
Nov 19 '16 at 10:12
add a comment |
This worked for me. I added the Custom Class name for the storyboard. But my class doesn't show up in the automatic results in the assistant editor. However now I am able to create the outlet for the label.
– Ronald Randon
Nov 1 '15 at 17:12
I have a whole bunch of xibs where it doesn't automatically load the associated file. Some it does. I have all theClass
properties set as you suggested.
– toast
Nov 19 '16 at 10:12
This worked for me. I added the Custom Class name for the storyboard. But my class doesn't show up in the automatic results in the assistant editor. However now I am able to create the outlet for the label.
– Ronald Randon
Nov 1 '15 at 17:12
This worked for me. I added the Custom Class name for the storyboard. But my class doesn't show up in the automatic results in the assistant editor. However now I am able to create the outlet for the label.
– Ronald Randon
Nov 1 '15 at 17:12
I have a whole bunch of xibs where it doesn't automatically load the associated file. Some it does. I have all the
Class
properties set as you suggested.– toast
Nov 19 '16 at 10:12
I have a whole bunch of xibs where it doesn't automatically load the associated file. Some it does. I have all the
Class
properties set as you suggested.– toast
Nov 19 '16 at 10:12
add a comment |
I don't know if anyone else is still having this issue, but I get it a few times a week on Xcode 6.1.1 and I usually do the following to fix it (once I have checked that there are no class name mismatches):
- Clean build
- Delete Derived Data (using Organiser)
- Force Quit Xcode
- Re-open and Build
I know this is crazy, but it continues to work for me o_O
1
I was forced to do this after renaming a CustomViewController.m to CustomViewController.mm, only this worked. :)
– Corwin Newall
Jun 23 '15 at 0:58
Yuppi it's worked :D seems like derived data mess up.
– mert
Dec 11 '15 at 14:59
Worked on Xcode 7.3 as well.
– leanne
Apr 28 '16 at 19:28
I tried a bunch of these recommended fixes but this one was the one that worked. if you turned off indexing, turn it back on before attempting this fix. Your associated files will only show up after Xcode is done indexing.
– Trig3rz
May 30 '16 at 15:16
2
I encountered the same issue again today. These steps did not work until I clicked "Top Level Objects" instead of "Automatic". When I did that, something indexed at the top and then I clicked "Automatic" and bam...there was my viewController :)
– Adrian
May 29 '17 at 22:29
|
show 1 more comment
I don't know if anyone else is still having this issue, but I get it a few times a week on Xcode 6.1.1 and I usually do the following to fix it (once I have checked that there are no class name mismatches):
- Clean build
- Delete Derived Data (using Organiser)
- Force Quit Xcode
- Re-open and Build
I know this is crazy, but it continues to work for me o_O
1
I was forced to do this after renaming a CustomViewController.m to CustomViewController.mm, only this worked. :)
– Corwin Newall
Jun 23 '15 at 0:58
Yuppi it's worked :D seems like derived data mess up.
– mert
Dec 11 '15 at 14:59
Worked on Xcode 7.3 as well.
– leanne
Apr 28 '16 at 19:28
I tried a bunch of these recommended fixes but this one was the one that worked. if you turned off indexing, turn it back on before attempting this fix. Your associated files will only show up after Xcode is done indexing.
– Trig3rz
May 30 '16 at 15:16
2
I encountered the same issue again today. These steps did not work until I clicked "Top Level Objects" instead of "Automatic". When I did that, something indexed at the top and then I clicked "Automatic" and bam...there was my viewController :)
– Adrian
May 29 '17 at 22:29
|
show 1 more comment
I don't know if anyone else is still having this issue, but I get it a few times a week on Xcode 6.1.1 and I usually do the following to fix it (once I have checked that there are no class name mismatches):
- Clean build
- Delete Derived Data (using Organiser)
- Force Quit Xcode
- Re-open and Build
I know this is crazy, but it continues to work for me o_O
I don't know if anyone else is still having this issue, but I get it a few times a week on Xcode 6.1.1 and I usually do the following to fix it (once I have checked that there are no class name mismatches):
- Clean build
- Delete Derived Data (using Organiser)
- Force Quit Xcode
- Re-open and Build
I know this is crazy, but it continues to work for me o_O
answered Jun 5 '15 at 7:23
mdstroebelmdstroebel
24126
24126
1
I was forced to do this after renaming a CustomViewController.m to CustomViewController.mm, only this worked. :)
– Corwin Newall
Jun 23 '15 at 0:58
Yuppi it's worked :D seems like derived data mess up.
– mert
Dec 11 '15 at 14:59
Worked on Xcode 7.3 as well.
– leanne
Apr 28 '16 at 19:28
I tried a bunch of these recommended fixes but this one was the one that worked. if you turned off indexing, turn it back on before attempting this fix. Your associated files will only show up after Xcode is done indexing.
– Trig3rz
May 30 '16 at 15:16
2
I encountered the same issue again today. These steps did not work until I clicked "Top Level Objects" instead of "Automatic". When I did that, something indexed at the top and then I clicked "Automatic" and bam...there was my viewController :)
– Adrian
May 29 '17 at 22:29
|
show 1 more comment
1
I was forced to do this after renaming a CustomViewController.m to CustomViewController.mm, only this worked. :)
– Corwin Newall
Jun 23 '15 at 0:58
Yuppi it's worked :D seems like derived data mess up.
– mert
Dec 11 '15 at 14:59
Worked on Xcode 7.3 as well.
– leanne
Apr 28 '16 at 19:28
I tried a bunch of these recommended fixes but this one was the one that worked. if you turned off indexing, turn it back on before attempting this fix. Your associated files will only show up after Xcode is done indexing.
– Trig3rz
May 30 '16 at 15:16
2
I encountered the same issue again today. These steps did not work until I clicked "Top Level Objects" instead of "Automatic". When I did that, something indexed at the top and then I clicked "Automatic" and bam...there was my viewController :)
– Adrian
May 29 '17 at 22:29
1
1
I was forced to do this after renaming a CustomViewController.m to CustomViewController.mm, only this worked. :)
– Corwin Newall
Jun 23 '15 at 0:58
I was forced to do this after renaming a CustomViewController.m to CustomViewController.mm, only this worked. :)
– Corwin Newall
Jun 23 '15 at 0:58
Yuppi it's worked :D seems like derived data mess up.
– mert
Dec 11 '15 at 14:59
Yuppi it's worked :D seems like derived data mess up.
– mert
Dec 11 '15 at 14:59
Worked on Xcode 7.3 as well.
– leanne
Apr 28 '16 at 19:28
Worked on Xcode 7.3 as well.
– leanne
Apr 28 '16 at 19:28
I tried a bunch of these recommended fixes but this one was the one that worked. if you turned off indexing, turn it back on before attempting this fix. Your associated files will only show up after Xcode is done indexing.
– Trig3rz
May 30 '16 at 15:16
I tried a bunch of these recommended fixes but this one was the one that worked. if you turned off indexing, turn it back on before attempting this fix. Your associated files will only show up after Xcode is done indexing.
– Trig3rz
May 30 '16 at 15:16
2
2
I encountered the same issue again today. These steps did not work until I clicked "Top Level Objects" instead of "Automatic". When I did that, something indexed at the top and then I clicked "Automatic" and bam...there was my viewController :)
– Adrian
May 29 '17 at 22:29
I encountered the same issue again today. These steps did not work until I clicked "Top Level Objects" instead of "Automatic". When I did that, something indexed at the top and then I clicked "Automatic" and bam...there was my viewController :)
– Adrian
May 29 '17 at 22:29
|
show 1 more comment
The issue is due to not completion of indexing - so there are few alternatives, that you can try for-
Way 01 : Check if indexing is showing in processes - then let it complete. Then, close the editor and reopen it
Way 02 : Just perform the clean action. It will start showing appropriate Viewcontrollers.
Way 03 : This is the most effective way - Just perform "Build" and then restart editor - it will surely going to work.
Thanks, this worked.
– nenchev
Aug 15 '17 at 15:56
I can tell that this did not work for me. The "Automatic" option is disabled and if I use "Manual", then Xcode complains. I have a regular Storyboard based project in Xcode 10 and Swift 4.2. Sometimes it works, sometimes it doesn't. Right now I can't figure out how to make it work again.
– Alex
Nov 9 '18 at 17:47
add a comment |
The issue is due to not completion of indexing - so there are few alternatives, that you can try for-
Way 01 : Check if indexing is showing in processes - then let it complete. Then, close the editor and reopen it
Way 02 : Just perform the clean action. It will start showing appropriate Viewcontrollers.
Way 03 : This is the most effective way - Just perform "Build" and then restart editor - it will surely going to work.
Thanks, this worked.
– nenchev
Aug 15 '17 at 15:56
I can tell that this did not work for me. The "Automatic" option is disabled and if I use "Manual", then Xcode complains. I have a regular Storyboard based project in Xcode 10 and Swift 4.2. Sometimes it works, sometimes it doesn't. Right now I can't figure out how to make it work again.
– Alex
Nov 9 '18 at 17:47
add a comment |
The issue is due to not completion of indexing - so there are few alternatives, that you can try for-
Way 01 : Check if indexing is showing in processes - then let it complete. Then, close the editor and reopen it
Way 02 : Just perform the clean action. It will start showing appropriate Viewcontrollers.
Way 03 : This is the most effective way - Just perform "Build" and then restart editor - it will surely going to work.
The issue is due to not completion of indexing - so there are few alternatives, that you can try for-
Way 01 : Check if indexing is showing in processes - then let it complete. Then, close the editor and reopen it
Way 02 : Just perform the clean action. It will start showing appropriate Viewcontrollers.
Way 03 : This is the most effective way - Just perform "Build" and then restart editor - it will surely going to work.
edited Aug 17 '17 at 5:32
answered Jun 7 '17 at 11:38


Mehul ThakkarMehul Thakkar
9,30273663
9,30273663
Thanks, this worked.
– nenchev
Aug 15 '17 at 15:56
I can tell that this did not work for me. The "Automatic" option is disabled and if I use "Manual", then Xcode complains. I have a regular Storyboard based project in Xcode 10 and Swift 4.2. Sometimes it works, sometimes it doesn't. Right now I can't figure out how to make it work again.
– Alex
Nov 9 '18 at 17:47
add a comment |
Thanks, this worked.
– nenchev
Aug 15 '17 at 15:56
I can tell that this did not work for me. The "Automatic" option is disabled and if I use "Manual", then Xcode complains. I have a regular Storyboard based project in Xcode 10 and Swift 4.2. Sometimes it works, sometimes it doesn't. Right now I can't figure out how to make it work again.
– Alex
Nov 9 '18 at 17:47
Thanks, this worked.
– nenchev
Aug 15 '17 at 15:56
Thanks, this worked.
– nenchev
Aug 15 '17 at 15:56
I can tell that this did not work for me. The "Automatic" option is disabled and if I use "Manual", then Xcode complains. I have a regular Storyboard based project in Xcode 10 and Swift 4.2. Sometimes it works, sometimes it doesn't. Right now I can't figure out how to make it work again.
– Alex
Nov 9 '18 at 17:47
I can tell that this did not work for me. The "Automatic" option is disabled and if I use "Manual", then Xcode complains. I have a regular Storyboard based project in Xcode 10 and Swift 4.2. Sometimes it works, sometimes it doesn't. Right now I can't figure out how to make it work again.
– Alex
Nov 9 '18 at 17:47
add a comment |
I had the same problem, and I managed to solve it by selecting the correct Target on the File Inspector of both files (Swift and XIB in my case, you can check the file inspector in the storyboard).
It can happen if your project has a lot of targets (mine had a few, the file was checked on the wrong one).
add a comment |
I had the same problem, and I managed to solve it by selecting the correct Target on the File Inspector of both files (Swift and XIB in my case, you can check the file inspector in the storyboard).
It can happen if your project has a lot of targets (mine had a few, the file was checked on the wrong one).
add a comment |
I had the same problem, and I managed to solve it by selecting the correct Target on the File Inspector of both files (Swift and XIB in my case, you can check the file inspector in the storyboard).
It can happen if your project has a lot of targets (mine had a few, the file was checked on the wrong one).
I had the same problem, and I managed to solve it by selecting the correct Target on the File Inspector of both files (Swift and XIB in my case, you can check the file inspector in the storyboard).
It can happen if your project has a lot of targets (mine had a few, the file was checked on the wrong one).
answered Aug 23 '18 at 19:39
MaviMavi
3718
3718
add a comment |
add a comment |
You'll want to turn XCode indexing 'on' and set the Assistant editor to “Automatic”. This helped in my situation when the other suggested answers didn't. Details on turning on indexing at Stopping xcode from indexing
add a comment |
You'll want to turn XCode indexing 'on' and set the Assistant editor to “Automatic”. This helped in my situation when the other suggested answers didn't. Details on turning on indexing at Stopping xcode from indexing
add a comment |
You'll want to turn XCode indexing 'on' and set the Assistant editor to “Automatic”. This helped in my situation when the other suggested answers didn't. Details on turning on indexing at Stopping xcode from indexing
You'll want to turn XCode indexing 'on' and set the Assistant editor to “Automatic”. This helped in my situation when the other suggested answers didn't. Details on turning on indexing at Stopping xcode from indexing
edited May 23 '17 at 12:10
Community♦
11
11
answered Feb 7 '16 at 10:32
user4806509user4806509
1,12011750
1,12011750
add a comment |
add a comment |
I just deleted build folder completely.And it works for me!
add a comment |
I just deleted build folder completely.And it works for me!
add a comment |
I just deleted build folder completely.And it works for me!
I just deleted build folder completely.And it works for me!
answered Nov 20 '18 at 10:54


ali shekariali shekari
4551925
4551925
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f26512966%2fxcode-6-assistant-editor-automatic-results-will-not-display%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown