Property gets released in a strange manner

[alexeyndru]

I have a property in the app delegate which is a NSMutableArray. I store there some results I get from the web. The problem is that the second time I try to set this property (I call the setter from another class) I get EXC_BAD_ACCESS. Just right when I step into "synthesize". I solved the problem by retaining this property. I would like to understand why this property gets released since it's in the app-delegate class. What is happening to it when I try to set it the second time? Thanks.

Bellow in the code: when I get back in the current view controller to make another search, when it gets to setting locArray I get EXC_BAD_ACCESS unless I retain locArray. So, what could happen to the property which belongs to app delegate? Why do I need to retain it?


[(RedAppDelegate *)[[UIApplication sharedApplication] delegate] setLocArray:foundLocations];
[[(RedAppDelegate *)[[UIApplication sharedApplication] delegate] locArray] retain];


RezViewController *aRez = [[RezViewController alloc] init];
[self.navigationController pushViewController:aRez animated:YES];
[aRez release];

[BrianSlick]

Do you really expect to get an answer without posting any code?

[alexeyndru]

Originally Posted by BrianSlick

Do you really expect to get an answer without posting any code?

[(RedAppDelegate *)[[UIApplication sharedApplication] delegate] setLocArray:foundLocations];
[[(RedAppDelegate *)[[UIApplication sharedApplication] delegate] locArray] retain];


RezViewController *aRez = [[RezViewController alloc] init];
[self.navigationController pushViewController:aRez animated:YES];
[aRez release];

[BrianSlick]

The view controller stuff is not relevant. You need to post more about locArray. How is it declared in the .h file? And you need to post more about foundLocations. Use your head and provide useful code if you want a solution.

[alexeyndru]

Originally Posted by BrianSlick

The view controller stuff is not relevant. You need to post more about locArray. How is it declared in the .h file? And you need to post more about foundLocations. Use your head and provide useful code if you want a solution.

-locArray is a NSMutableArray declared in app-delegate;
-foundLocations is a NSMutableArray initialized with data from a remote database and it is declared as a property in the current view controller;

The app I am working makes use of maps. I let the user search locations and the results I put first in foundLocations and then in locArray (which sits in app - delegate as I mentioned before). Now everythings work fine after I retained locArray (it was just a guess), but I want to understand what is going on with that property which is initialized in app-did-launch. Why it works when the first search is performed and why I need retain it in order to be able to use it the next time I search.

[BrianSlick]

How many more times am I going to have to ask for code before you will actually show it? What your app does is completely useless information. You get one more chance to post relevant code before I'm done with this thread. Don't describe or summarize anything else. Copy. Paste. Code.

[alexeyndru]

Originally Posted by BrianSlick

How many more times am I going to have to ask for code before you will actually show it? What your app does is completely useless information. You get one more chance to post relevant code before I'm done with this thread. Don't describe or summarize anything else. Copy. Paste. Code.

Ok, I am too noob for a conversation with you. I just don't know what would be more relevant than what I have already shown. Thank you for your help and have a nice day.

[BrianSlick]

Ok look. There are only two possibilities here. Either you have made a mistake, or you misunderstand something. The only way we are going to figure that out is to see what you have actually done.

You have not shown how your property is declared. This would be the relevant lines from your .h file.

You have not shown how this other array is created or destroyed. This would be the code before and possibly after what you posted previously.

You are expecting me to assume that your verbal descriptions indicate that things were done correctly. If they were done correctly, then you wouldn't have a problem, so this is a bad assumption. And if you don't even know what code to show in order to solve the problem, then I have no reason to assume that you know what you're doing. So, show what you are doing.