Luacrash
InvokeNative: execution failed: No current resource manager
Also seen as: No current resource manager InvokeNative execution failed no resource manager
What causes it
A native was invoked outside of a valid resource context — often from a thread or callback that ran after the resource scope was lost, or code executing before the resource fully started. Common with C#/.NET resources and with natives called from detached threads.
How to fix it
Ensure natives run inside the resource's runtime, not from a detached or stale context.
- Identify what runs the native — a timer, an external thread, or early startup code.
- Use CreateThread / Citizen.CreateThread from within the resource rather than raw OS threads.
- For C# resources, marshal work back onto the script's thread instead of a background Task.
- Make sure the code isn't running after the resource stopped (guard with onResourceStop).
Related errors
Related guides
Still stuck? We can help.
Optimized, dual-framework scripts for QBCore and ESX from Viper Development — escrow protected, delivered instantly to your Cfx portal.