I am making an app that uses a UITableView to display a list of values and when you click on one of those values it opens another view which shows editable details in a UIView that has a UITextView in it.
I can run the app and have the detail view show with out a problem but when I connect the IBOutlet binding to the textview in IB and then run it, it will crash when I click a value in the Tableview and try to display the second view with the textview.
One thing I do notice is that you've got a leak with the text view. You only release it once yet you have it in a property set to retain. I believe connecting it to an outlet gives it yet another retain count as well.
As for your problem though, I can't say from this code. Can you post the crash log? Specifically, run the app in debug mode (using build and debug, or cmd+option+y in Xcode), and when you get the crash, type "bt" in the console window and copy the output. (bt stands for backtrace. It'll give you the steps the app took that led up to the crash)
__________________
HEY! Was this post helpful?
If so, it would be MUCH appreciated if you'd just click on one of these apps:
MyD
Take 1 minute to set up your MyD and you'll always be able to prove you own your device!
Membrik
Test your memory by sliding tiles to match chains of increasing difficulty.
One thing I do notice is that you've got a leak with the text view. You only release it once yet you have it in a property set to retain. I believe connecting it to an outlet gives it yet another retain count as well.
As for your problem though, I can't say from this code. Can you post the crash log? Specifically, run the app in debug mode (using build and debug, or cmd+option+y in Xcode), and when you get the crash, type "bt" in the console window and copy the output. (bt stands for backtrace. It'll give you the steps the app took that led up to the crash)
It looks like there's an issue with interface builder (the reason being that from your stack trace, I'm seeing that there's a problem with initWithNibName, but you don't have a custom implementation of it). I'd try two things.
First, go into interface builder, and check on the lower right corner of the interface builder window where it shows you your file owner, view, first responder, etc. for either a yellow warning symbol or a red error symbol. If that's there, be sure to click it and see what it says.
Otherwise, I'd try deleting the text view, and creating it anew by dragging it from the library. Then try connecting that new text view.
__________________
HEY! Was this post helpful?
If so, it would be MUCH appreciated if you'd just click on one of these apps:
MyD
Take 1 minute to set up your MyD and you'll always be able to prove you own your device!
Membrik
Test your memory by sliding tiles to match chains of increasing difficulty.
According to some research (namely this thread), the particular error you're getting seems to have to do with having created a class, set IB to use that class, and then deleted the class. Have you deleted any class files recently?
__________________
HEY! Was this post helpful?
If so, it would be MUCH appreciated if you'd just click on one of these apps:
MyD
Take 1 minute to set up your MyD and you'll always be able to prove you own your device!
Membrik
Test your memory by sliding tiles to match chains of increasing difficulty.