ios - UITableView dataSource must return a cell from tableView:cellForRowAtIndexPath: but I do -


i dont understand this: cellforrowatindexpath: indexpath: returns proper uitableviewcell. (i have assertion effect not nil , trace prove it)

but stil getting sporadic exception?

this how allocate / reuse cell:

... {   uitableviewcell *cell = [tv dequeuereusablecellwithidentifier: cellidentifier];   if (cell == nil)   {       cell = [[[uitableviewcell alloc] initwithstyle: uitableviewcellstyledefault                                      reuseidentifier:  cellidentifier] autorelease];       cell.selectionstyle = uitableviewcellselectionstylenone;   }   assert(cell);   // (code populate cell)   // ...   assert( cell != nil);   nslog(@"returning cell %@ type %@", cell, nsstringfromclass([cell class]));   // edit: showing actual return value   return cell; }

the crash looks in log:

2013-04-17 16:46:05.323 .. -[someeditviewcontroller tableview:cellforrowatindexpath:] returning cell <uitableviewcell: 0x20d1a2e0; frame = (0 351; 320 43); hidden = yes; autoresize = w; layer = <calayer: 0x20d1a410>> type uitableviewcell 2013-04-17 16:46:15.296 ... *** assertion failure in -[uitableview _configurecellfordisplay:forindexpath:], /sourcecache/uikit/uikit-2380.17/uitableview.m:5471 2013-04-17 16:46:15.301 ... *** terminating app due uncaught exception 'nsinternalinconsistencyexception', reason: 'uitableview datasource must return cell tableview:cellforrowatindexpath:'

i have looked @ numerous other entries similar question. stumped! did homework, ensuring cell returned not nil, , still assertion!

anyone can this? thanks

it turns out did return cell after (as far cellforrowatindexpath: concerned)

the problem solved assigning tableview.datasource , tableview.delegate nil in dealloc.

the table view still pending dealloc when container view controller deallocated, , not call cellforrowatindexpath implementation. @ least, able reproduce problem (and fix).


Comments

Post a Comment

Popular posts from this blog

Why does Ruby on Rails generate add a blank line to the end of a file? -

running rails generate controller foo home results in: class foocontroller < application controller def home end end (there's nothing on line in actual file, blank line) is there purpose blank line? it's common use newline indicate end of line, last line. many editors (like vi, use) add in newline silently. consensus text files (especially in unix world) should end in newline, , there have been problems historically if wasn't present. why should text files end newline? the tool used count lines in file "wc" counts newlines in file, without trailing newline show 3 instead of 4. it improves readability of templates used in generator. consider: https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/controller/templates/controller.rb to remove trailing newline, template have last line of: end<% end -%> instead of: end <% end -%> that seems less readable me. the discussion below refers
Read more

keyboard - Smiles and long press feature in Android -

i've created android keyboard. how add features inserting smilies, , using long keypresses display symbols? to create long-press behavior allows select several options pop-up menu, follow guide (specifically pop-up menu section): http://developer.android.com/guide/topics/ui/menus.html smileys (also known emoticons) combination of keys, understood programs , parsed same way. have do, when clicks smiley face on keyboard, simulate pressing of key combination matching emoticon. example, when clicks smiley, should simulate key presses ':' , ')' :). here's list of emoticons: http://en.wikipedia.org/wiki/list_of_emoticons
Read more

node.js - Bad Request - node js ajax post -

i'm using express 3.0 , node v0.11.0. have button submits form , i'm using ajax post data json object node server. client code is: $('#contact').submit(function(e) { console.log('submit called'); var formdata = json.stringify($('form').serializeobject()); console.log(formdata); $.ajax({ url: "http://localhost:3000/savedata/", type: "post", datatype: 'json', data: {objectdata: formdata}, contenttype: "application/json", complete: function() { console.log('process complete'); }, success: function(data) { console.log('process sucess'); }, error: function() { console.log('process error'); }, }); return false; }); then on server: var express = require('express'); var app = express(); app.set('views', __dirname + '/views'); app.set('view engine', 'jade'); app.use(express.bodyparser());
Read more