Release Build Crashes with ExecutionEngineException from Meta.XR.ImmersiveDebugger (Passthrough App)

[BeardyDev]

Hi everyone,

I'm working on a Unity project for Meta Quest using the Passthrough API. Everything works perfectly in the Development Build, but when I create a Release Build, the app crashes on startup.

I’ve tracked the issue down to this error:

ExecutionEngineException: Invalid call to method 'Meta.XR.ImmersiveDebugger.Manager.DebugManagerAddon'

It appears to be caused by the Immersive Debugger system still being included or invoked at runtime, even though I’ve:

• Unchecked Enable in the Immersive Debugger Settings
• Unchecked UsesImmersiveDebugger in MetaXRProjectSettings.asset
• Cleared Unity's /Library, /Bee, /Temp, and rebuilt clean

Yet it still looks like the debugger is enabled (see screenshot) and I see the ExecutionEngineException error in the logs.

I've read that using IMMERSIVE_DEBUGGER_ALLOW_USE_IN_PROD as a scripting define can prevent the crash,  but looks like this is unacceptable for production use.

[MetaQuestSupport]

Hi @BeardyDev!

Thank you so much for reaching out on our forums about this issue you've been experiencing when using our debug tool within the unity engine.

In order to get this issue resolved we would recommend going through the handy link to our developer support center we have popped in here for you and submitting a request. This will essentially act as a report to our internal engineering team and they will be happy to look deeper into this issue for you to ensure you have the easiest time possible in creating awesome experiences for the Metaverse!

[BeardyDev]

Awesome, thank you! Apologies for posting in the wrong spot, I’ll submit a request through the developer support center as suggested.