ok got it, i was calling onCreate before the EAGLView was assigned to its motherview or its motherview assigned to the window. the EAGLView is picky to integrate atm, but not bugged here so far.

i modified several things, no more addSubview to the UIViewController but a setView, and i also modify updateApplicationStatus so that i call QCAR:onResume when i show the camera but atm it crashes the iPad after several seconds where i can see the camera properly

Hi Goshua,

It is odd that you don't get the message 100% of the time - what could be so variable in the view hierarchy?

I assume you are never getting the camera view shown on the iPad?

MoSR wrote:

When onResume is invoked, QCAR searches the view hierarchy for an EAGLView that implements renderFrameQCAR. The message you've reported will be given if it isn't found.

There may be some subtle difference between your view hierarchy in iPhone and iPad - are you coding them or using different .xib files?

i don't use xib files at all, everything is implemented by hand
i had that message and so no camera output on my ihpone4 then i changed my scheduling to have the onCreate message called earlier or later and finally found an order where it wasn't appearing on iphone4, but now i start to work on the ipad2 version and it appears 90% of the time
i don't see any problem in my view hierarchy but i keep searching anyway

When onResume is invoked, QCAR searches the view hierarchy for an EAGLView that implements renderFrameQCAR. The message you've reported will be given if it isn't found.

There may be some subtle difference between your view hierarchy in iPhone and iPad - are you coding them or using different .xib files?