views:

21

answers:

1

For some reason, I'm having this issue randomly pop up where a method that's being called receives a bad address and causes the app to crash. Sure, that's not uncommon, but when I check the frame above the crashing method, the address of the object that I'm passing in is completely different than the address of the argument in the called method.

A: 

Try making the property that you're accessing atomic-- also verify and make sure that there isn't another property that overlaps the name within a superclass of the object you're manipulating.

mdizzle