Troubleshooting

Updated runtime but still cannot debug

1. After updating the extension, copy the latest files from the luadebug folder into the project and confirm they are loaded.
2. Unity: make sure the runtime is not still reading an old AssetBundle / cached script.
3. Confirm StartDebug is not commented out and the port matches launch.

Debugger startup indexes for a long time

Do not open the whole game / engine repo as the workspace; shrink indexing with scriptRoots / ignoreDir.

Cannot reach account server / login failed

1. Check the network and luadebug.serverUrl (must be HTTPS).
2. Confirm email verification is complete.
3. Update to the latest LuaDebug and try again.

Extension installed but cannot debug

1. Disable other Lua debugger extensions.
2. Custom loader chunknames must be real paths.
3. If LuaSocket is missing, enable it for your framework.
4. On a real device, host must be the PC LAN IP.

module 'socket.core' not found

LuaSocket is missing or not fully enabled. On Cocos, turn on network / luasocket bindings in the engine; Unity integrations differ per framework — see that framework’s docs.

Stack paths wrong / jumping files

1. Check that localRoot points at the correct script root.
2. Several game folders in one workspace: see Debug · multiple game folders.
3. For Unity DoString, drop a wrong suffix from chunkname or use a real path.

macOS LuaTest Permission denied

Check extension folder permissions, or allow the app in System Settings; reinstall the extension if needed.

Extension stuck or won't start

1. Update the editor and LuaDebug.
2. Temporarily disable C# / Unity debugger extensions.
3. Clear this extension’s data and reinstall.