[Interest] Qt iOS: how to ensure that a C++ side QObject is initialised before accessing it on Cocoa side

Nuno Santos nunosantos at imaginando.pt
Mon Dec 12 12:39:46 CET 2016


Hi,

I have an app audio which audio engine is handled completely on the iOS side, however, my audio engine is completely written on the Qt side in C++.

I have a lot of crash reports on Xcode and since I’m unable to connect this reports with the code itself I guess that this crashes happen because of inter-app audio events on the iOS side are trying to access the shared controller app in the C++ side when it is still not initialised. I would like to avoid calling the shared object if it is not initialised yet. So far I’m doing it in a very rudimentar way.

What is the proper way of doing this? Has anyone passed through a similar problem before? 

Thanks!

Regards,

Nuno Santos
Founder / CEO / CTO
www.imaginando.pt
+351 91 621 69 62




More information about the Interest mailing list