There are some things you can check, trying to solve this:
Callers
Go to the implementation of the method, and stand with the caret on on of the lines of code inside it. No on the top left corner of the main window click the small button with the black and gray rectangles (To the left of the arrows) and check if there is any place in your caode where someone is calling this method.
You won't see outlets here - so if the Callers
option is gray (Like in the picture below) - You are good.
Methods call stack
Try putting a breakpoint on the first line of the method implementation. When the breakpoint stops you code, look at the left in the Navigator pane, under the Debugger, you can see the exact order in which the methods called eachother to get to the call of your method. Most chances you will only need to just go one step back (Just click the line to see where it happens - btw this is kind of like a time-machine (or scope-machine?) where you can see what was the state of all the objects in your scope).
Property Outlets
Go the where the outlet is defined (in your .h
or .m
file) in click that tiny gray circle. This will show you all the outlet connections to that method/property (In the following picture I clicked a property but the beginning of method will be the same).
NIB/Storyboard connections
Open you NIB/Storyboard file, and click the View Controller itself (The top item in the Document Outline chain on the left, another options is Ctrl
+Shift
+Mouse Click
the view controller in the IB and choose the View Controller from the drop menu).
Now on the right (In the Utilities pane) go to the Connection Inspector (The most right one) to see all the connections to everything in the View Controller. Check you method to see if anything is connected that shouldn't be.