XCode inconsistent results across several computers?

Start using version control software. You are making things needlessly difficult for yourself. There is a small learning curve at first, but it pays off even on your first non-trivial project.

I sent him my half to combine with his half Start using version control software. You are making things needlessly difficult for yourself. There is a small learning curve at first, but it pays off even on your first non-trivial project.

If you are sure that you have identical copies of the codebase, then you can probably narrow it down to one of the following: Different toolchain. Make sure you are both running the same version of Xcode with the same versions of all the SDKs etc. Different data. Delete the app from your devices and try again.

Lingering files in the bundle. Installing a development version via Xcode doesn't remove old files from the bundle. You might have files in your bundle that he does not or vice-versa.

Delete the app from your devices and try again. Different hardware. Occasionally bugs manifest themselves only on certain hardware.

Different device capabilities can send the same code down different paths. Both of you try testing in the simulator temporarily.

I've checked that the version (and build) of XCode are the same on both of the computers I've tested it on. Also, I've deleted the app and it still does the same. I haven't reinstalled XCode before, I've only installed it once.

We're just testing it in the iPhone simulator, we have not done testing on actual iPhones yet. – JheeBz Oct 17 at 2:01.

I think the "inconsistent results" you mention could be due to the fact that you may have made a connection in Interface Builder for the delegate and dataSource of your tableView to the DataContainerSingleton, but your friend has a different version of the . Xib in which that connection is not present. That would not give any compile errors or warnings, but would present itself as a "bug" where none of the delegate or datasource methods are actually called.

Since you can see the logging statements, I would presume the delegate is set properly but the dataSource is not..? The other option is that your cellForRowAtIndexPath method is returning a new cell each time (without a checkmark, hence you can only check but never uncheck). EDIT: To be more precise about this, you should have code in cellForRowAtIndexPath along these lines: UITableViewCell *cell; cell = tableView dequeueReusableCellWithIdentifier:@"drinkCell"; if(cell == nil) // we need to create a new one { cell = UITableViewCell alloc initWithStyle:UITableViewCellStyleDefault reuseIdentifier:@"drinkCell"; } if(tickedIndexPaths containsObject:indexPath) { cell. AccessoryType = UITableViewCellAccessoryCheckmark; } else { cell.

AccessoryType = UITableViewCellAccessoryNone; } Otherwise, if the iPhone is low on memory, the OS will ask the application to purge any not strictly necessary objects from memory, which includes your existing cells. So the next time you go to retrieve the cell at row 2, for example, it'll have to create a new UITableViewCell object with default values, which means an accessory of None. Due to this, you should explicitly set the checkmark every time you get the cell.

After seeing your first comment: Okay. You should ensure you don't add a duplicate indexPath. If a row is selected, make sure that checkedIndexPaths doesn't contain the path you're about to add.

The first option is not possible because they are literally exact copies of one another. I have a second computer that I'm testing it on right now and it's giving me different results than the laptop I'm using right now. I copied it straight over there and opened an exact copy of the same file.

I checked the delegate and dataSource of my tableView and they're both set correctly. The didSelectRowAtIndexPath method is actually called, I checked with a checpoint. I printed out tickedIndexPaths every time I call the method above and it does in fact go above 4.

The drinks array is initialised. – JheeBz Oct 17 at 1:20.

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.