To fix this so I could deploy, I clicked “Project > Edit Project Settings”. I changed the Code Signing Identity to point to my cert.  I got the same error. I searched the file system to try and figure out where that string was coming from.  In Visual Studio, sometimes I have to edit the project file with a text editor to fix weird issues like that.  So, I opened up the *.xcodeproj file to see if I could find it there.  I use TextMate for my Ruby code so I fired it up to open that and it turns out that *.xcodeproj is not a file but a package or directory or whatever Mac fanboys call it.  Inside I found the project file and found the string.  I wanted to figure out how to fix this through the UI so I didn’t just change the text there.  I did notice though that the old cert was listed under a different profile.

So, back in the project properties, I selected “All Settings” in the configuration drop down and changed the cert once again to my cert and everything worked!

UPDATE: Well, It happened to me again but this time, changing the code signing cert didn’t help.  I had to go into the actual project file by right/command clicking on myproject.xcodeproj and selecting “Show Package Contents”.  Edit project.pbxproj with a text editor.  Search for: “CODE_SIGN_IDENTITY[sdk=iphoneos*]” = “iPhone Developer: Romain Marucchi-Foino (VC824XU999)”;  Replace all of these with your own identity.  for me it was: CODE_SIGN_IDENTITY = “iPhone Developer: Jason Rowland (2RK77WERHG)”;  Save the file, and go back to xcode.  It will prompt you to reload from disk and say yes.  Maybe another day I’ll figure out where the setting is in the GUI but now that I know I can change these things with a text editor, I probably never will

Calling Methods

This was the very first thing that jumped out at me when I started using Objective-C.  To call a method, you use the following syntax:

[object message:param1 namedParam2:param2 namedParam3:param3];

You can call a property by using a more familiar dot notation though.

[object setProperty:value];
object.property = value;

Those two lines of code are equivalent.  Even though the brackets are awkward to me, I really love the fact that it has named parameters.  You always read in your code what the heck it is you are passing in.  I love this feature.  I wish java and C# both had this feature for the readability of the code alone.

[Update: 6/11]

Thanks to Martin for pointing out to me that these are not actually named parameters.  The order matters and the parameters help make up the function name.  I confirmed this for myself by writing the following two functions.

- (void) play:(id)x withDuration:(id)y withVolume:(id)z
{
    // 
}

- (void) play:(id)x withVolume:(id)z withDuration:(id)y
{
    // 
} 

These are two different methods.  They have the names “play:withDuration:withVolume” and “play:withVolume:withDuration”

Garbage Collection

This one is interesting to me.  Objective-C supports garbage collection the same as C#.  The unfortunate thing is that it is only supported when developing for the Mac.  It is not supported on the iPhone.  When programming for the iPhone, you have to worry about memory management like you did back in the old days.  This means you have to concern yourself with error prone reference counting with methods “release”, “retain”.  This has been the cause of many bugs in the past and could cause your app to suddenly quit unexpectedly if you aren’t careful with memory leaks.  The confusion usually was around who was responsible for freeing an object.  Was it the library or the calling object?  Fortunately, Apple has a firm policy on when to free objects.  Basically, you free any object you create.  You“create”an object using a method whose name begins with “alloc” or “new” or contains “copy”.  If you own an object, you are responsible for calling “release” on the object.  Do NOT call release on an object you do not own or you will most likely cause very bad things to happen because the object will have been freed before it was supposed to.  If you just follow this convention in your own code, you should reduce your chance for this kind of bug.

There are some classes that have convienience methods that return new objects but are not considered created by the calling method.  They are not named with “alloc”, “new”, or “copy”.  One example is [NSString stringWithFormat].  This returns a newly created string, but it is created as an autoreleased object.  Since we don’t control when they are released, it’s good practice to avoid using them unless there’s a good reason.

I know this is going to trip me up since I’ve been using garbage collection in java and C# for for a LONG time.

Class Methods and Instance Methods

- (id) foo {
    return foo;
}

+ (id) foo {
    return foo;
}

The first thing this c# developer noticed was that little “-” minus sign at the start of the line.  In the java and c# worlds, we are used to putting private/protected/public in front of these methods.  I assumed that this was probably a private designator.  Wrong.  This minus sign actually identifies this method as a method that can be used on an instance object.  In both java and C#, you do not put anything in front of the method to identify it as an instance method.  The “+” plus sign designates a class method.  This is similar to “static” in java and C#.  When I thought about it a little more, it makes sense.  In Objective-C you have an interface file where you declare the public methods.

Object Identifiers

The second thing is (id).  id is a built in type in Objective-C.  It is the object identifier.  It is a pointer to a struct. All objects are of type id.  In a similar way every object in C# inherit from “Object”.

[Updated: 6/11]

id is more similar to the “var” keyword in C#.  It’s simply a way of using dynamic typing instead of static typing.  Thanks Martin.

Properties

You declare your property i the import file as follows:

@property (retain, nonatomic) UILabel* foo;

The retain here is required because the iPhone is not garbage collected.  It will give you a warning if you do not put it here.  The other attribute nonatomic tells the compiler that it doesn’t need to worry about creating thread safe code for the methods.

There are two different ways to implement the property.  We will discuss the verbose way first.  When creating a property called “foo”, you need to create two instance methods “foo” and “setFoo”.  This is more similar to the java way of handling properties except in java it is “getFoo”.

- (UILabel*) foo {
    return foo;
}
- (void) setFoo: (UILabel*) aFoo {
    if (aFoo != foo) {
        [aFoo retain];
        [foo release];
        foo = aFoo;
    }
}

The other way to implement the property is a shortcut where the compiler implements it for you.  It would only work for simple getters and setters but it saves typing when they are boring methods anyway. You simply add the following to the top of your implementation file:

@synthesize foo;

MVC

It seems to me that the MVC architecture is used by default when writing an app for the iPhone.  You can write MVC in any platform, but what I’ve noticed is that most developers tend to program based on the first examples they read. One aspect that I haven’t quite figured out is the whole Interface Builder and the whole IBOutlet stuff.  IBOutlet is basically just a define, but Interface Builder uses these tags to know what is available to connect things.  You can drag connections and events using these tags.  I don’t think I fully understand what I’m doing when I’m making the connections.  I understand how to make things work, but I guess I don’t understand on an intuitive level yet.  Hopefully more experience will give that to me.

Playing a sound

Whenever this button was pressed, I wanted to play a sound.  Here is the code I used to do this:

SystemSoundID soundId;
NSBundle *mainBundle = [NSBundle mainBundle];
NSString *path = [mainBundle pathForResource:@"filename" ofType:@"wav"];
NSURL *filePath = [NSURL fileURLWithPath:path isDirectory:NO];
AudioServicesCreateSystemSoundID((CFURLRef)filePath, &soundId); 
AudioServicesPlaySystemSound(soundId);

I have these in different classes but this is the correct sequence.  I created a SoundEffect class do do the actual audio work so I don’t have a reference to the audio includes in the main part of my program.  This should work, but if not, I followed this good tutorial: http://www.iphonedevcentral.org/tutorials.php?page=ViewTutorial&id=50&uid=57348970.  You will need to include the AudioToolbox in your Frameworks in order for this to work.