Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

iOS Ugh, the UITableView is not refreshing. Ever.

M

MobiusStrip

macrumors 6502
Original poster
Dec 11, 2009
488
367
Hi all.

I have a pretty simple scenario: a view with one control on it, a UITableView. It's in a XIB owned by a controller for this view, derived from UIViewController. The controller has an IBOutlet for the UITableView, and it implements the necessary delegate protocol methods:

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

These methods DO get called, and the cellForRowAtIndexPath is pretty much the boilerplate example that everyone uses, with mods for the way I'm storing data.

Here's the hookup in IB:

5076024257_50d1d1f5de_b_d.jpg


I don't have any separate threads, and I do call reloadData on the TableView. Nothing ever shows up in it; it stays empty. Any ideas?

Thanks!
 
Well, here are the delegate functions:

Code: 
- (UITableViewCell*) tableView:(UITableView*)tableView cellForRowAtIndexPath:(NSIndexPath*)indexPath
{
    UITableViewCell* cell = [tableView dequeueReusableCellWithIdentifier:@"MyIdentifier"];

    if (cell == nil)
    {
        cell = [[UITableViewCell alloc] initWithStyle:UITableViewCellStyleSubtitle reuseIdentifier:@"MyIdentifier"];
        cell.selectionStyle = UITableViewCellSelectionStyleNone;
    }

    if(indexPath.row < stashes.size())
    {
        Stash* pCurrStash = stashes.at(indexPath.row);
        if(pCurrStash)
        {
            cell.textLabel.text = [NSString stringWithUTF8String:pCurrStash->getName().c_str()];
        }
    }

    return cell;
}


- (NSInteger) tableView:(UITableView*)tableView numberOfRowsInSection:(NSInteger)section
{
    return stashes.size();
}

Occasionally, an application event will occur and I call reloadData on the TableView, to pull in changed data from the collection. That's pretty much it for the code.
 
So have you put log statements in to check the sanity of various conditions? You know, ultra-basic debugging that any programmer would do? As an example the first thing I would log would be stashes.size().
 
Yes, I've stepped through it. The collection contains entries, and the cell text is set to a legitimate string provided by that getName() call.
 
Solved

SOLVED. Turns out to be a simulator bug, or a bug in the way Xcode is loading apps into the simulator.

The simulator was showing a UI from a XIB that had long since been deleted from disk and removed from the project. And yet the compiled nib from it was turning up in the app package, even after cleans.

Even deleting that nib from the app bundle or deleting the whole build directory wasn't enough; it still showed up in the simulator. I had to manually invoke the app deletion on the simulator screen to get rid of it.

Hopefully this info will save someone else some time. Needless to say, I filed it with Apple.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back