I'm working on a Mac OS application that should be supported on 10.7. The project was created under Xcode 5 running on Mavericks with base localization initially enabled.
I've now removed base localization so that I can support 10.7 but have been unable to get the application to run at all anymore, either on 10.7 or 10.9 because Xcode generates the following error:
Unable to load nib file: MainMenu.xib, exiting
So I added a new MainMenu.xib file via File - New File - MainMenu. I wired up the AppDelegate object and set the delegates.
Back in the project file, I made sure of the following:
MainMenu.xib is part of the build target's Copy Bundle Resources build phase.
Made sure that MainMenu.xib is selected in the targets General - Main Interface setting
Checked in the File Inspector for MainMenu.xib and saw that it was localized into English and that a checkmark was checked beside that.
I can't think of what else should be set. I've even created a new, empty project for testing. With that, I made no changes other than to delete the base localization and then attempt to re-add a new MainMenu.xib and follow the steps outlined above, but to no avail. That build fails as well when launching in Xcode with the same error.
I've even tried using a different XIB file with a different name (yet still one setup as a MainMenu) but all that did was change the error message to reflect the new XIB name I had specified in the settings.
While I'm sure base localization is great, I'm hoping to support 10.7 users so I don't believe that keeping base localization enabled is an option for me.
Any help (even if it's pointing out the obvious) would be much appreciated.
I think I finally found the culprit. When the base localization was deleted, a new MainMenu XIB file needed to be created and selected in the target. Under Targets - Deployment Info - Main Interface the drop-down menu lists all available XIB files in the project that you could specify as the Main Interface. Naturally, I selected my newly created MainMenu.xib file and that's where the problems started.
After diff'ing the changes that Xcode had made to the Project Settings file, I noticed that in the working copy, the Main Interface key was set to MainMenu whereas in the non-working copy the key was set to MainMenu.xib, which is precisely what was in the drop-down menu.
Manually removing the .xib extension from the Targets - Deployment Info - Main Interface combo-box appears to have things working again. Note that it was the combo box in the first place that added the .xib suffix.
There might be more at play here, but that simple change has resulted in the program now properly launching.
Related
I've got a 'Main app' and a 'Helper app' (sandboxed, if that matters) that share a private framework including some resources, nib files, sound files etc.
The framework gets called and used by both apps without issues. However from within in the Framework code I have a NSViewController that loads a nib file which is included in its resource folder. This seems to work as long as its called by the 'Main app'. Doing the same with the Helper app (a login item) however does not work and fails with an "Unable to find nib named" error.
The actual 'Framework' is copied to the Main app's 'Frameworks' directory and I use a #rpath in the helper app to find the framework: #executable_path/../../../../Frameworks
This setup seems to work just fine however at runtime it seems the frameworks code tries to find the named Resource under the helper app's Resource folder and not under the Framework's resource folder. Is there a setting or some flag that I can set in xcode to make the framework's always look under the exact path where the framework's executable/library is installed?
It seems the only solution is to copy the framework to the 'Helper' app as well. Resources otherwise do not get loaded if the framework was just a symbolic link to the actual framework placed inside the main app.
What you can do is making your Framework dynamic or shared like described here Dynamic Library Programming Topics
Though it is a bit of a complex process, but a very nice feature.
What else can help you?
Perhaps editing the Library Search Paths or the Framework Search Paths under your Build Settings in Xcode. there you can specify additional search paths to look for.
Even though, I would not copy the Framework to the Main app's dir. I would leave it in one place on your disk, add them to your project (Main and helper) and add the specified search path.
By the way: How is your framework implemented? Is it a folder, is it compiled, or is it only code files?
My cocos2d-iphone project has tiled maps (.tmx files along with .png textures).
Recently, I deleted all the .png textures in my project (in Xcode, you hit the delete key and then choose to send to trash).
Then, I ran the project, and it tried to load up the CCTMXTiledMap. I was expected it to crash (there shouldn't be any textures in the project, anyway), but it didn't. In fact, it ran just fine, and the maps did load. No idea why - is Xcode keeping some kind of reference to such files somehow?
I checked the .tmx file, and this is the line that defines the source image:
<image source="myMap-hd.png" width="973" height="1024"/>
There definitely is no myMap-hd.png nor myMap.png file in my project folder. Not even Xcode's search toolbar shows it!
Oh, and I also cleaned the project.
As I wrote in question's comment. Problem was not in your Xcode project. Deleted resource files will most likely be still available on device/simulator if you had run application with these resources previously. The reason is that Xcode doesn't track files that are in application bundle, they're just simply copied. That's why they land in Copy Bundle Resources build phase.
You should delete application from device/simulator and run it again. Or if you have precious data already in application, you could navigate to application bundle and delete file manually. Files won't appear again.
In the simulator, iOS Simulator (menu item) > Reset Content and Settings. Clean your project, then run again. Same thing happens without cocos2D.
I've found this to be an issue when nib files are automagically loaded, and while not in the referenced files seem to still be loaded (or attempted). Can cause some brain pain bc the files don't appear in the Xcode IDE though they do exist in the file system.
I'm trying to begin localization on a project, and I've already got an English version of Localizable.strings going. I'm now trying to add French to that file, which is creating an fr.lproj folder, as I'd expect. However, it's putting it in my project root, and I'd like it inside my project's Resources directory.
Xcode seems to have no interest in letting me move the file, and if I move it in Finder, it goes red in Xcode as expected, but doesn't let me click to locate the file.
I've tried moving it in Finder, then editing project.pbxproj in a text editor to add Resources/ in front of the only line in there that mentions fr.lproj/Localizable.strings, and that has worked, but after doing that, the project's targets also turned red in Xcode, and building the app doesn't change that fact. Very odd.. any idea what could be going on, or how to get this going?
This can be a real pain. I even had XCode crash on me when trying to correct unwanted file locations. I found that the best way is to create the localized file (be it .strings or .xib) as a copy of the source language version outside of XCode, then drag and drop it into XCode. If you do this then XCode will display it correctly and your targets' Build Phases > Copy Bundle Resources settings will include it with its correct location. I don't know why your targets are displayed in red, perhaps you could look under Copy Bundle Resources in case anything is wrong there, or also select your project and click Validate Settings in case you haven't already done so.
Also, if you have been testing in the simulator beware of how XCode does not clean up the files in your app bundle--you may want to delete the app and run it again to make sure it's working with your new location.
I'm new with Cocoa / Objective-C development and I have a question.
Last week I had to create a SWF based Screensaver for Mac, and as I didn't find a free-compatible solution for Mac OS X Snow Leopard / Lion, I created a .saver bundle with Xcode 4. It creates inside a webview and loads inside the SWF file.
You must place the SWF file inside the Resources folder inside the bundle to make it work with different SWFs.
And now, I'm trying to code a Cocoa Application to do it automatically.
It has a simple user interface so as the user can select a SWF file. Then the code makes a copy of my previously build .saver file (I have the path hardcoded), places inside it a copy of the SWF file, and saves it where the user indicates in a save panel.
And here comes my question. Now I have the path of the .saver file hardcoded, but I need to have it as a Resource inside my app. Would it be possible? How could I use/access it?
Thanks for your help and time!
Your application already has at least one resource, assuming you didn't delete the MainMenu nib. Add your .saver bundle to that build phase. In the app's code, get the URL to the screen-saver bundle the usual way.
I have created a working project in XCode + Interface Builder on my iMac. I would like to port it to my Windows XP machine, which has GNUStep installed (and it seems to work okay as long as I create programs from scratch on there). I have transferred all the files to my Windows machine, created a new project in ProjectCenter and compiled everything.
It works to that point.
My problem is with Gorm. I have used the Interface Builder to save a NIB file (instead of the default XIB file) and it basically creates a folder ("ProgramName.nib") with two files inside: "designable.nib" and "keyedobjects.nib". I have tried all kinds of different methods to actually open these files in Gorm to see the interface objects, but it just won't work (which is to say, nothing happens when I try to open a file - Gorm launches okay, but there's no evidence of the NIB file's menus or other objects). I was under the impression that Gorm could open NIB files (there's even a reference to the "keyedobjects.nib" file on the Gorm webpage). Is there something that I am missing?
Thanks,
Peter
Gorm should be able to open .nib files.
If it does not, you should either create a bug report on the GNUstep tracker or send an email to the developer list and ask there about your problem loading the .nib files.