Xcode shows old, deleted xib files

Question

I\'ve searched all over and haven\'t found any help...

I built a small test app with two UIViewControllers and their corresponding xibs. T

Answer 1

just clean the build using

Product -> Clean

menu.

Answer 2

I had this problem, and it was a result of xcode continuing to copy previously compiled xib's - even though the source file was deleted, the build cache wasn't. Product > Clean and then recompiling solved it.

Answer 3

I just had this issue, just delete the app from the simulator.
Then do a clean on your project.
In xCode, go to the Product menu, select Clean.

Or just press Shift+Command+K!

Answer 4

I just found (and fixed) a related problem — one that demonstrates similar symptoms but whose root cause is slightly different.

In particular, the symptoms I observed were that my iPad app would initially display an old storyboard image for the first page and, after a short delay, would bring up the most recently edited story board contents. I went through most of the above machinations to no avail.

The problem is that the iPad loader first just dumbly loads your app's launch image into the screen. You usually set up this image as part of the early administrative setup of the app in XCode. At launch time, while the end user is considering the content and cogitating about where to touch the screen, the application is in the mean time madly getting itself ready, un-archiving the xib/nib/storyboard, and doing the real work of getting ready.

In the ideal situation the provided launch image is pixel-for-pixel the same as the one generated by the nib-unarchiving-process. However, if you forgot to update your launch image after updating the story board, you'll see an image shift at the completion of the unarchiving.

I wouldn't have suspected this as the problem except that I had read Jef Raskin's description of how he did exactly this on the Canon Cat word processor to provide the illusion of an instantly ready application: it takes advantage of the fact that the typical human response time to an application startup is on the order of seven seconds — plenty of time for even a floppy-based system to load and overwrite the bitmap facade that the loader sets up. Sometimes, it's good to have read a bit of arcane history. Jef would of course later go on to found a project whose name was Macintosh, and the rest is history — and this bug.

Answer 5

I had the same problem, but i solved it by changing the datetime of my system to today. And re-saved the xib. I was testing the local notification.

Answer 6

Not sure whether this helps, but I just had this.

It took me days to work it out. In my case I enhanced an existing Xib file. The changes I applied in interface builder never appeared in the app.

Eventually I found the cause. I had my FilesOwner view outlet set to a subview below the top view. When I enhanced the view I did this as an extension to th top view. Thus the changes never appeared when running the app.

Changing the view outlet to the correct view ( the top view in my case ) did the trick and it all worked fine ...