The error is telling you that a certain method must be run on the main thread (or the web thread, to which you don't have access). Since reloadData triggers this method eventually, one way to solve this would be to make reloadData execute on the main thread: self. TableView performSelectorOnMainThread:@selector(reloadData) withObject:nil waitUntilDone:NO .
– aherlambang Sep 21 at 6:51 Yup, replace your line self. TableView reloadData; with the proposed code from me. – DarkDust Sep 21 at 6:54 Also, you will need to use a lock to prevent concurrent access to self.
Notes (except if it already is a thread-safe container). – DarkDust Sep 21 at 6:55 I have an MBProgressHUD that is running when it's doing this, should be enough? – aherlambang Sep 21 at 13:41 I don't see the relationship here, your MBProgressHUD doesn't seem to have anything to do with your table view.
Did you replace the line with reloadData with the performSelectorOnMainThread: call? Does it fix the crash? – DarkDust Sep 21 at 14:11.
It looks like sortedArray is nil or has a retain count of zero, and that's confusing the debugger as to its class. I've seen this in my own code when I've allowed this to happen: Your problem stems from using = with no self in sight and as such you're probably creating a zombie. If in doubt, run the Analyzer in 'Product -> Analyze' (XCode 4.
To fix the problem, you need to use the synthesized getters and setters.
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.