I have this problem when I simulate my app, its not an error or a warning but it appears in my console, has anyone ever experienced this before?
相关问题
- CALayer - backgroundColor flipped?
- Core Data lightweight migration crashes after App
- Core Data lightweight migration crashes after App
- How can I implement password recovery in an iPhone
- State preservation and restoration strategies with
相关文章
- 现在使用swift开发ios应用好还是swift?
- UITableView dragging distance with UIRefreshContro
- Could I create “Call” button in HTML 5 IPhone appl
- TCC __TCCAccessRequest_block_invoke
- Where does a host app handle NSExtensionContext#co
- Unable to process app at this time due to a genera
- Swift - hide pickerView after value selected
- How do you detect key up / key down events from a
I had lot of problem with the same issue. I solved this by this way
1) You're not using
UIViewController's
designated initializerinitWithNibName:bundle:
. Try using it instead of justinit
.2) set
animated:YES
to a NO, and that solved the problem. eg.[self.navigationController pushViewController: viewController_Obj animated:NO];
I also got this at
I changed the
YES
to aNO
, and that solved the problem.In my case, this error occurs when you click two tabs in a tableview very fast.
The result causes wrong titlename, back button disappear. Someone mentioned that when you push a view,
set animated:NO
. The error will disappear but still causes some strange behavior. It pushes two views, then you need to back twice to get back the tableview screen.Method I tried in order to resolve this problem:
add
BOOL cellSelected;
in
viewWillAppear
cellSelected = YES;
in didselectcell delegate
if (cellSelected){cellSelected = NO; do action ; }
This helps prevent clicking two different cells very fast.
This was a tough one for me: I've overridden
without overriding:
in my window root navigation controller. then a child navigation controller complained when pushing another view controller with the above mentioned warning. The warning wasn't the worst, the big problem was, that there the delegate of the child navigation controller weren't called anymore. weired.
In my case I was fetching
NSData
fromNSURL
inside 'viewDidLoad
' method.The situation can occur if you are adding a view with a modal view controller as a sub view. Best to use:
It is basically saying the view life cycle is not streamlined for those viewControllers you are trying to display then.