I upgraded to Xcode 6 beta 4 and now my App continuously crashes with the message
It crashes because supposedly Xcode can't find my custom classes that I have linked in my Storyboard but it shows that they are linked correctly in the Xcode interface. I've spent hours trying to figure this out, but nothing works! I'm positive everything is linked correctly. My only other option may be to delete the entire storyboard file and start from scratch because it might be corrupted somehow. Edit: I would also like to add that I tried cleaning, reseting simulator, messing with build phases etc. None of that works. | |||||||||||||
|
434 | I resolved this issue as I was typing the question. I figured I'd answer my question and leave it here for anyone else who may face this issue when using Xcode 6 beta 4. To resolve this issue, you need to select each of your custom class objects in Storyboard (this includes any custom views, even the custom view controllers themselves). Then with those objects selected, open the identity inspector and under "Custom Class" you should see the Module option. Click inside the Module text box, and press enter. That's it! The current module for all of my custom objects must have been internally incorrectly set somehow in Xcode 6 beta 4. But there was no visual indication of this in the inspector. Note that if pressing enter inside the Module text box doesn't work, try selecting the arrow to the right and manually select your current module, then clear the text box and press enter. You can also try pressing enter inside the class text box (although this usually is to resolve a different issue). Here is an image to make things more clear: | ||||||||||||||||||||
|
51 | Sometimes Xcode missed To fix it, open storyboard as source code and replace this line: to this: | ||||||||||||||||||||
|
48 | I had this problem after renaming a swift class. Solved it by using the @objc directive: | ||||||||||||
|
19 | Sometimes the controller you are providing loses its target membership from the current application. In that case, pressing enter on the "Module" field will do nothing. Go to the controller and make sure that it has target membership set to the current app. | ||||
|
12 | This worked for me.. Check your compiled source, whether that file(e.g; ViewController.m) is added or not, in my case ViewController file was not added so it was giving me the error..
| ||
5 | I faced this issue in Xcode 6.1 when I removed I fixed it by deleting the | ||
4 | What @gfrs said is correct, you need to set the Module. However I once ran into an issue that my class wasn't listed in the Also have a look at this answer, which looks like to solve the 'real' problem I encountered. | ||
4 | I googled everywhere for this. None of the answers work for me until i met 1 dude who asked me to move my project folder to desktop. It just worked automatically. Apparently if you have you project folder to deep in many folders, XCODE actually breaks. | ||
4 | These steps work for me. 1) Clear Derived Data. | ||
2 | I fixed it by doing exactly the opposite of what ChikabuZ suggested (thanks for pointing it out, though). In the storyboard file, find this: and replace it with this: I can't believe how many hours I'm losing getting around bugs in the Swift compiler and Xcode 6 | ||
2 | I solved this problem by typing in the Module name (unfortunately the drop list will show nothing...) in the Custom Class of the identity inspector for all the View controller and views. You may also need to indicate the target provider. To achieve this objective you can open the storyboard in sourcecode mode and add the "customModuleProvider" attribute in both ViewController and View angle brackets. | ||
1 | What only worked for me is actually adding the module name to the xib file... Sooo, the xib files look like this: HORRIBLE solution in my opinion, but that is supposedly how Apple wants us to do it now. This question shows 3 possible work arounds back in beta 4 ... apparently Apple has not been very helpful in this situation according to some because they call it "Working as intended." | ||
1 | I faced the problem when I ported the storyboard from Swift project to Objective-c project, noticingvvkuznetsov's answer, it turned out the two project using same identifier. I "Product -> Clean" and tap Enter key on the Module and Class text field. the issue went away. | |||
1 | The solution was different for me. You need to add the .m of the class to the build phase compiled sources of the target. Hope this helps! | ||
1 | In my case, the class referenced in the Storyboard / xib did not have Target Membership set. To fix, give that class's
| ||
1 | I solved this by opening my storyboard file as source code and using command-F to search for my unknown class and delete the custom class associated with it. | ||
0 | I had the same problem with Xcode Version 6.1 (6A1052d). I think the problem appears if you renamed your App / Xcode Project. My solution was to add the module name in the interface builder manually. | ||
0 | I had this problem after I added a new target, then created a new class using the 'New File' dialog but accidentally failed to check the new target as well as the original target in the creation dialog, so the object was only added to my original target. The solution was to delete the source files (remove reference only) then add them back using 'Add Files', this time checking both targets. | ||
0 | I faced such a problem on Xcode 6 when I deleted the already included ViewController.h & ViewController.m files from my new view based project, and deleted the scene that was related to this class from storyboard, Xcode cashes these files in derived data folder, so if you try to go to Window -> Projects -> your_project and delete the derived data everything will go fine. | ||
0 | Don't use spaces in the project name, otherwise the Custom Class will not find your own classes. | ||
0 | I faced a problem when I created a project with the same name that already existed in my projects directory (though it was deleted some time ago). I wrote my solution therehttp://stackoverflow.com/a/27763697/1654692 | ||
0 | It happened to me because my class was marked with | ||
0 | I had the same problem, but not the same fix. The project folder was kinda corrupted so i had to copy my project folder to another folder, for example your desktop and after that open the project. When it opened go to your interface builder project and you will see he recognise your script, Then you click indeed on the name of your script and press enter, u will see the module input will fill it self. And it will work like a charm! :D | ||
0 | This worked for me when nothing else did. From the project directory in terminal: Open the matched files as source code in Xcode and change any instances of ViewController to what you actually need. In my case the file I needed to open as source was Main.storyboard and I changed instances of ViewController to DetailViewController. I deleted two files from Xcode and main.storyboard which is what I believe caused this issue for me to begin with. | ||
0 | In mij case the ViewController.h/m where in a lib. The projects still builds but since Xcode 6.3 the above error was shown at run-time. Moving both files back into the project solved the issue. | ||
0 | I was playing with Spring class. And this error happend to me because i used folder as reference when moving whole folder class to project instead of creating groups. So this was my solution, dont use folder as reference but create groups. | ||
0 | in my case , i setup app as universal app, so xcode creates two storyboards.but i was only using(designed) only iPhone storyboard. and trying to run app in iPad.for resolve problem just need to make app as only for iPhone and works great. | ||
0 | My solution was to remove @objc from Custom class definition. | ||||
|
0 | I had the same problem with Xcode 6.3 when I add files to "myapp". That's because I choose "create folder reference" instead of "create groups".I delete these files and add them again with the "create groups" option.And the problem fixed. | ||
0 | Select your unknown class file, open file inspector tab, check your target name in | ||
'모바일개발(Mobile Dev) > IOS개발(ObjectC)' 카테고리의 다른 글
| A better way to access NSUserDefaults (0) | 2015.12.11 |
|---|---|
| Sending Image from Xcode to Server (0) | 2015.12.11 |
| ABOUT PLIST (0) | 2015.12.10 |
| english locale for the displayName (0) | 2015.12.10 |
| Facebook Login in iOS App (0) | 2015.12.06 |