Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
My application has a UITabBarController. When the first view loads I start a new thread from its
- (void)viewDidAppear:(BOOL)animated;
method, which runs a task. When the task starts, it calls a delegate method from the first view and adds an activity indicator to the UINavigationItem. When it ends, it calls another delegate method from the first view, and hides activity indicator.
The problem is that the activity indicator is not shown, unless I go to another view and then back.
Without seeing your code, it’s hard to guess what is happening. In the past, UIKit methods have not been thread-safe and were required to be called on the main thread. It seems like a long shot in this scenario, but have you ruled this out?