I ended up switching to setContentOffset. Seems to be working 95% of the time which in my case is OK. At least it's not crashing. Thank you for your help
hockeyfan530
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
yes, that code does scroll to the >>>>savedRowMainFave<<<<. It works most of the time but sometimes, as the error message indicates, it says there are only 4 rows in the tableview....when in reality there are 10 rows which is why I think it has something to do with the tableView not being fully loaded. I am working on a reproducible code. Thank you for replying
Yes viewWillDisappear() is called. It sets savedRowMainFave and (for test purposes prints "Leaving indexPath = savedRowMainFave). The variable does not disappear. When I come back in viewWillAppear() runs i also print out savedRowMainFave coming in = savedRowMainFave to verify it is still set properly. I do have an else statement as you suggested but the code never runs.