ansaurus

Question

iPhone: App Crashes When Search Bar Used in TableView

Answer 1

A:

for one thing, please condense your code so we don't have to scroll through all the newlines. Furthermore, is this the dataSource of your table view, and if so, where are:

- (NSInteger)numberOfSectionsInTableView:(UITableView *)tableView
- (NSInteger)tableView:(UITableView *)tableView numberOfRowsInSection:(NSInteger)section
- (UITableViewCell *)tableView:(UITableView *)tableView cellForRowAtIndexPath:(NSIndexPath *)indexPath

they have to access copyListOfItems, which may fail and be the source of your crash.

What does the console show when it crashes?

edit: thanks for providing the extra info. Your problem lies here:

for (NSString *sTemp in searchArray)

searchArray contains "waitsup" objects, I think, not NSString. You cast it to an NSString pointer, but it's your responsibility that it actually points to an NSString object. Therefore you get the error that rangeOfString is called on a waitsup, which is "unrecognized". You cannot then call rangeOfString on the waitsup object, if you didn't provide the rangeOfString method in it yourself.

Looking at the rest of your code, I think you could fix it like this:

for (waitsup *sTemp in searchArray) {
    NSRange titleResultsRange = [sTemp.name_last rangeOfString:searchText options:NSCaseInsensitiveSearch];
    if (titleResultsRange.length > 0)
        [copyListOfItems addObject:sTemp];
}

but then only name_last is searched. Expanding this to include more fields is trivial.

mvds 2010-07-15 13:12:58

Thanks brother, but still i get some problem that i can enter only one alphabet after this app crash.

Prateek Bhanot 2010-07-19 04:59:34

could you update the question with the code you have now, and the errors you get now?

mvds 2010-07-19 06:06:45

now you can check

Prateek Bhanot 2010-07-22 08:10:01

ansaurus

tags:

views:

answers:

iPhone: App Crashes When Search Bar Used in TableView

related questions