I have installed STV 2.0B2 in my app and am experience crashes in the app. The worst part is that I get no error messages or notices from the simulator. It just dies. I know this is a vague report, but I was wondering how to start to track/understand what is causing the app to crash. I can put in a bunch of NSLog statements but I was hoping for some hints that would be a little more direct. I noticed that the beta release version is up to 5. Is it a lot more stable? I thougth I read somewhere that it would be released by the end of Jan/2011?

thx,
wes

Hi Wes,

I'll send you our latest STV 2.0 RC now, which is quite stable according to our tests. If you still get crashes, I'd be glad to have a look at your project.

This RC helped. I did notice when I used 'Build & Analyze', there were a potential leak. Don't know if this is important. I will keep moving forward with what I have. Can't wait for the official release.

thanks again,
wes

Hi Wes,

I am glad the RC version worked well for you.

Regarding the potential leaks, these are mis-reported by the analyzer because of the compiler pre-processors that are being used (e.g. "#ifdef _COREDATADEFINES_H"). This is nothing to worry about, the code is not leaking any memory.

That's good to know about no memory leaks.

Now here is something weird. I have a controller that is built entirely with STV and the fields I have in it are in this order:
- PropertyTypeSelection
- PropertyTypeDate
- PropertyTypeTextField
- PropertyTypeTextView
- PropertyTypeTextField.

I start at the top, filling out values and when I get to the 4th value (textview), the values that I have stored in the top 3 disappear. After I put a value into this textview, I can then re-enter data in the top three and store the data. Any idea what I am doing wrong?
Right now, I start in the middle to store a record so I don't have to double type.


wes

Hi Wes,

Would you please post some code so that I would be able to replicate this? (or you can send your project to our support email if you want)