I saw this question before, but couldn’t answer it. A few days ago, I encountered the problem of tableView’s dynamic calculation height under iOS7, which needs to be refreshed before it can be displayed normally. I checked the information and found that iOS7 has a height caching mechanism, which is different from iOS8 and In the future, the processing order of the proxy methods will be different. It can be solved by separating the height calculation method and executing it separately. The original poster's problem should be for a similar reason.
I saw this question before, but couldn’t answer it. A few days ago, I encountered the problem of tableView’s dynamic calculation height under iOS7, which needs to be refreshed before it can be displayed normally. I checked the information and found that iOS7 has a height caching mechanism, which is different from iOS8 and In the future, the processing order of the proxy methods will be different. It can be solved by separating the height calculation method and executing it separately. The original poster's problem should be for a similar reason.