wait_fences: failed to receive reply: 10004003 (Again)

Question

Another cry for help about this warning.

First of all I have looked at every and all questions on here elsewhere and none seem to fit my situation. It has nothing to do

Answer 1

? I'm a little unclear of your view/viewcontroller hierarchy...

You've got a ViewController "Calc" which creates a "DataView" for it's "master" view. "DataView" creates a textField "TextFieldKPD" as a subview of itself. "TextFieldKPD" then creates a UIView "KeyPad" subview which itself creates 13 UIButton subviews for itself.

So your views are 4 levels deep?

Apple state that a ViewController should handle a whole screenful of views (I guess this changed slightly now that we can create containerViews but the intent behind their assertion remains). Make sure your keypad button events and textfield events are handled by your viewController.

Surely you would be better creating all of these views in the viewController or the master view so your hierarchy is flatter?

Apologies if I've misunderstood your hierarchy.

Btw, one thing to try is removing the textfield entirely and seeing if you can still get the error.

Answer 2

As far as i can tell about your code description, the problem seems to occur when a subview (eg. UIAlertView) is created prior to its parent/super view. Something to do with the responder chain.

Try moving the view codes around to fix the problem or paste the relevant parts.

Answer 3

I've ran into the wait_fences error when mistakenly running UIKit code from a background thread. It doesn't sound like that's your problem, but if you haven't yet that's another thing to look into.

Answer 4

According to my knowledge. This warning appears when we are calling a UIAlertView and at the same time we are performing some operation on the UIView. To solve this problem we need not to perform operation on UIView at that time. For this we can do either of the two things : 1. We can call UIAlertView with some delay so that the operation on the UIView gets completed. 2. Or we can perform the operations on the UIView in method - (void) alertView:(UIAlertView *)alertView clickedButtonAtIndex:(NSInteger)buttonIndex; So that the UIAlertView is not on our UIView at that time when some operations are performing on the UIVIew.

Hope it will help you.

Answer 5

I've had this issues a few times before and attempted to find a solution. The closest that I got was that according to an apple engineer it is an issue caused internally and 3rd party developers should not worry about it. As far as I am aware it shouldn't cause your app to crash or cause any problems, other than a really annoying error in the debugger that seems to drive all developers mad!

Sorry that I couldn't be of more help.