MacOSCoders

Some times we would like to move the info.plist to other directories than the default project root directory. In such cases XCode would throw warning like “Warning: The Copy Bundle Resources build phase contains this target’s Info.plist file ‘Resources/Info.plist’.”

The Info.plist file belongs directly inside of the bundles Contents folder — that is to say, one level up from the Resources subdirectory. Thus copying Info.plist to that would serve little purpose, and might even be evidence of programmer oversight on something (as Xcode might think), hence the warning.  The Info.plist should not actually be a member of any target. The check boxes in the Get Info window of the info.plist should be unchecked and this warning can be avoided.

Hope this helps..!

When we create a new file in XCode, the default template has the company name listed as __MyCompanyName__. If you want this to show your actual company name instead of __MyCompanyName__, then execute the following command in your terminal. Make sure to replace the”YourCompanyNameHere” with the name of your company.

defaults write com.apple.Xcode PBXCustomTemplateMacroDefinitions '{ "ORGANIZATIONNAME" = "YourCompanyNameHere" ; }'

Xcode: Loading Stack Frames

Recently I encountered an new error for the first time in XCode. When my iPhone application under development crashed, instead of showing me the stack trace of where the application crashed, it threw an error “Loading Stack Frames” and was struck there indefinitely.  After researching about this for a while, I came to know my application crashed because of a stack overflow due to a non-terminating recursion in your code, and gdb is now trying to load all the stack frames on the stack . Usually, the stack of a application doesn’t get deeper than 50 frames or so (and that’s already a quite deeply nested stack). My application stack had run into 104708 frames which was quite too high.I finally figured out that the crash was due to an race condition.

Apple on Thursday released an update for the iPhone SDK, bringing the current version of the SDK to 3.1.2.

The new SDK 3.1.2, which now includes Xcode 3.2.1, is available in versions that are compatible with Leopard and Snow Leopard for iPhone and iPod Touch developers.

The update contains general bug fixes for the SDK and Xcode. Dashcode is reported to now support the creation of Web applications that are optimized for Safari on the iPhone, PC, and Mac.

If you’ve used this new update, please tell us about your experiences with it in the comments.

XCode: Could Not Support Development

Today  when I started my work on an iPhone project, my XCode failed to mount my iPhone. The XCode organizer was showing an orange dot next to it instead of the usual green one. Organizer complained “Could Not Support Development”. I tried restarting my XCode, launched iTunes but in vain. iTunes was able to mount my iPhone but XCode simply failed and I was not able to test my app’s on my phone. Read the rest of this entry »

Error Starting Executable

Quite a few times in our iPhone application development cycle we would encounter XCode error “Error Starting Executable – No provisioned iPhone OS device is connected.” even when we know the device is connected to the machine.   This error occurs when the connected device is not configured in the XCode->Organizer. Organizer would fail to mount the device as the version of XCode installed on the developer machine may not support the version of iPhone OS installed on the device.

Read the rest of this entry »

Sometimes when we are installing applications to our device through XCode, we might get a error message saying “The executable was signed with invalid entitlements“. This is most likely because the device is not included in the provision file. In tried with a device which i was sure to be included in the provision file and found that it works as expected. This error mostly occurs when we try to install applications on device which are not included in the provision file and is running iPhone OS 3.0. My iPod Touch whose UDID was not in the provision file was throwing this error where as my iPhone whose UDID is included in the provision file worked fine.

If you come across anyother reasons for getting this error message, do let me know.