I haven’t talked about what my app will be yet. And I have been very shy on detailing my progress. Even though it’s the main purpose of this blog, it often felt worthless… I don’t write as much as I would want to, so when I do, I talk about things that seem more useful.
Today I came accross an issue. Actually I have been having this issue for a few days, but until today, I could avoid it. So I did.
I tried to debug as much as I could, checking the debug navigator, outputting everything that seemed relevant to the console, trying to analyse the call stack so I could figure out what the app was trying to accomplish… Because of course, the error I got was EXC_BAD_ACCESS code = 1. Which means: you have a memory error, now find it.
Where do I go to? Being an indie developer, I can’t turn to a collegue. I don’t do code review. An old collegue of mine use to help me out via screen sharing, but he’s charging me… I finally turned to my best friend stackoverflow.com. I asked my question, trying to be as detailed as possible. But I am always shy to ask a question there! I am always afraid I will look stupid, too new to do anything useful, or just helpless! I am always glad someone asked the same question I have before me so I can just read the answer and be happy!
I create custom views on one of my UIViewController. These views have two labels that I set with specific values; one int and one string. In the first iteration of the UIView class, the int (called number) was an actual int. So the property was declared:
@property (assign, nonatomic) int number;
Later on, I changed number to be an NSNumber, but didn’t change the property declaration. It caused a memory error when the view was accessing _number to set the label properly. Changing the property to:
@property (strong, nonatomic) NSNumber *number;
fixed my issue.
Back to coding!