Troubleshooting

Updated debug files still cannot debug

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

Indexing takes a long time when starting debug

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

Cannot reach account server / login fails

1. Check network and luadebug.serverUrl (must be HTTPS).
2. Confirm email verification finished.
3. Update to the latest LuaDebug and retry.

Installed but cannot debug

1. Disable other Lua debug extensions.
2. Custom loader chunkname must be a real path.
3. If LuaSocket is missing, enable it per your framework.
4. On a device, use the PC’s LAN IP as host.

module 'socket.core' not found

The project has not integrated LuaSocket (or not fully). Cocos needs network / luasocket bindings on the engine side; Unity frameworks differ — check that framework’s docs.

Stack paths wrong / jumping to wrong files

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

macOS LuaTest Permission denied

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

Extension stuck or will not start

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