Without seeing the stacktrace I bet it's a double release of your selected cell. You're fetching it from the tableView this way.
Without seeing the stacktrace I bet it's a double release of your selected cell. You're fetching it from the tableView this way CustomCell *testcell = tableView cellForRowAtIndexPath:indexPath; and not retaining it, then at the end of the method you're releasing an object you don't own testcell release; Then when you return and start scrolling, the tableView might try to release that cell crashing because of a double release. Just don't release what you don't own (with create, alloc, copy, retain).
Perfect. It solved error by either way. I gave different identifier then also it worked and even by your method it worked.
Thanks a lot :) – Anks Mar 16 at 11:01 Cell identifiers and dequeueing from the tableview is to avoid reallocation of memory for the same class. E.g. By dequeueing you'll grab a CustomCell that's already set up, and then you have to set its attributes according to the new row.
Different identifiers should be for different cell classes. – tsakoyan Mar 16 at 13:56.
Issue is solved. I just need to give different CellIdentifier for each of the cell. So I changed the code to NSString *CellIdentifier = NSString stringWithFormat:@"Cell%d", i; Where I is variable declared in header file with assigned value as zero.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.