Start a new topic

Wikitude + ARKit crash on scene reload


We're currently working on a multi-scene Unity project, with ARKit and Wikitude working together in one of the scenes. A script grabs the pixel data from ARKit, and feeds it to Wikitude.

It all works flawlessly the first time the AR scene is launched, but if we navigate away from the scene (to a scene that does NOT have anything Wikitude related), and come back to it, ARKit tracking crashes with the following error message:  [Sensor] Unsupported pixel format: 875704438

We have narrowed the problem down to the "WikitudeCamera" object, since the application doesn't crash on scene reload if that object is disabled. However, Wikitude being closed source, we have no idea what steps to take to fix the problem.

According to the documentation, the Wikitude plugin should be destroyed when we navigate to another scene, since the WikitudeCamera object gets destroyed by Unity. It seems however that something lingers and prevents ARKit from restarting the tracking properly.

Any help appreciated !


Is ARKit running when you switch from the non-Wikitude scene back to the tracking scene, or is ARKit initialized after the scene is loaded.

The only thing that comes to mind is that maybe during Wikitude initialization ARKit is still running and that causes something to go wrong.

Can you please make sure that ARKit is only started after the OnInputPluginRegistered callback is called on the WikitudeCamera script?

Best regards,


Hello and thanks for your reply!

ARKit is not running during Wikitude initialization. We pause the native session on scene exit, and only attempt to resume it after Wikitude has been initialized (using the "input plugin registered" callback).

We tried waiting as long as 30 seconds to restart ARKit, without avail. We also tried using DontDestroyOnLoad on both the Wikitude and the ARKit game objects, but again, nothing prevents the "invalid pixel format" crash.

Thanks in advance for your time.



Is it possible for you to send us your project, or a simplified version of it that still reproduces the problem?

You can send it to our support email if you don't want to share it in the forums.

Having the project would allow me to debug it and maybe find out why this is happening.

Thank you,



Thank you for your time!

We are preparing a lightweight version of the project that we will send over to the support email.

Thanks again.


Login or Signup to post a comment