ios - Code working on iPhone 5, not on iPod touch 4 -


i'm testing application on different devices. app works fine on iphone 5, however, when test on ipod touch 4g, eror:

*** terminating app due uncaught exception 'nsinvalidargumentexception', reason: '***  [__nsarrayminsertobject:atindex:]: object cannot nil' *** first throw call stack: (0x33f252a3 0x3bba397f 0x33e6f8d9 0x51e25 0x35e180c5 0x35e1814d 0x35e180c5 0x35e18077 0x35e18055 0x35e1790b 0x35e17e01 0x35d405f1 0x35d2d801 0x35d2d11b 0x37a1f5a3 0x37a1f1d3 0x33efa173 0x33efa117 0x33ef8f99 0x33e6bebd 0x33e6bd49 0x37a1e2eb 0x35d81301 0x4fc8d 0x3bfdab20) libc++abi.dylib: terminate called throwing exception

the code that's crashing one:

/********/     nsmutablearray *tituloscampotextarray = [[nsmutablearray alloc] init];     (int = 0; < campos.count; i++) {          signupcell *cell = (signupcell*)[self.tableview cellforrowatindexpath:[nsindexpath indexpathforrow:i insection:0]];         [tituloscampotextarray addobject:cell.textfield.text];     } /********/

i'm using custom prototype cells (signupcell.h), on uitableview inside uiview.

can't find error, or how fix it.

edit: both devices running ios 6.1.3, , i'm using xcode 4.6.1.

uitableview's -cellforrowatindexpath: method returns nil if cell isn't visible on screen when call it.

my guess on iphone 5 table can display rows @ once, while on shorter ipod touch, last 1 or 2 cells aren't visible , -cellforrowatindexpath: returns nil, makes app crash.

you shouldn't rely on -cellforrowatindexpath request model data! view controller responsible data, not table view.

use same way access model data setting table view cells' text in -tableview:cellforrowatindexpath: data source method of view controller.


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