Extension randomly unlinks in Code

Hi! At some points, I’m finding that my extension randomly unlinks/doesn’t work if I move around the extension folder, even if I run the “link-app.bat” or “link-app.sh” file at random. Or, sometimes the extension unlinks during development, and a restart fixes this.

I’m running Code version 22.1.2, and the workstation specs are as follows:

CPU: 11th Gen Intel Core I5 - 11400F @2.60 GHz 6 cores
GPU: NVIDIA GeForce RTX 3060 (12GB)

Thanks for your help in advance!

Hi @natalia1. What do you mean that the extension randomly unlinks?

In regards to link_app.bat, all that script is doing is creating a symbolic link in your extension project folder to an Omniverse app folder. This is for convenience and to help enable features like intellisense in your development experience.

I imagine the app/ folder is not disappearing for you?

Hi @mati-nvidia , what I mean is that while I’m coding, at sporadic times I will get an error that my VS Code Debugger is unreachable. By restarting the system or creating a new extension, I can circumvent this, but where possible I’d rather not start a new extension.

Re: the app folder, I usually run this command, check if it works, and if it doesn’t, I manually delete the app folder and retry linking it. Everything else such as paths, folder structure, etc. is correct when this happens. Could something else be missing, perhaps? I usually follow the steps in the ReadMe from extension creation.

Ah, I understand. Could you include recent logs from Code from when you experienced the issue? Here’s how to locate them: How to Report an issue with Omniverse

It might also be helpful to get the Python output from VS Code the next time it happens:

Hi @mati-nvidia , Thanks for your continuous support! Here is an example of the errors I get when the extension randomly unlinks:

At that point I have no visible bugs in the code, it just happens as soon as I save it and suddenly my code can’t start up. Restarting Omniverse usually fixes this.

Thanks again for your help!

Ah, yes. There are certain extension errors at startup or shutdown that can leave the extensions in a bad state. This only crops up in development with hot reloading. It’s usually on an incremental save where the code might be incomplete. We are working on making that more robust.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.