iOS setup() and update() execution order bug?

I recently started experiencing an issue with a couple of my iOS OF apps in which update() is called before setup(). I’m guessing something has changed in the iOS SDK in regards to this call in in

[self.glView performSelector:@selector(setup) withObject:nil afterDelay:0]; //calls setup(), but on a separate thread!?
[self.glView startAnimation]; //calls update and draw

It seems that even specifying afterDelay of 0 causes setup to be called on a separate thread, so it is not guaranteed to be called before update/draw.

Is it just me, or have others experienced this - seems like a major issue, no?

Using [self.glView performSelector:@selector(setup)]; fixes the issue for me.

Excellent, thank you!