Hint: "self: import: submanifests": file not found

RE: Hint: "self: import: submanifests": file not found

ryan_mulder_antrum — Wed, 19 Nov 2025 17:54:31 GMT

I found the issue.

I had a .west directory in the my-library directory, causing VS Code to treat it like a west workspace.

Once I removed that, everything works as expected.

RE: Hint: "self: import: submanifests": file not found

Edvin — Thu, 13 Nov 2025 11:35:26 GMT

Hello,

The issue could possibly be that you have two manifests. Can you please try to use just one manifest? I believe that is the "normal" way to do it. Either have a single manifest that imports my-library but directly from GitHub ('import: true'), or have a manifest that pulls in (no import) my-library and also imports the nRF Connect SDK.

Best regards,

Edvin

RE: Hint: "self: import: submanifests": file not found

ryan_mulder_antrum — Fri, 07 Nov 2025 20:51:56 GMT

Yes, I was intentionally using the branch, but I accept your recommendation to use the stable version.

Still, I prefer to use west to manage the SDK (rather than installing it) to simplify setup for developers and continuous integration.

The sdk version didn't make a difference, but I do think I stumbled on the problem while experimenting with the different versions.

My VS Code workspace includes the folder of a library we wrote with a west.yml (or something that nRF Connect is finding). When I remove the folder, the issue clears up.

Here's my files:

folder structure:

MyProject
  my-project.code-workspace
  .west
    config
  my-project
    west.yml
  my-library
    west.yml

MyProject/my-project.code-workspace:

{
  "folders": [
    {
      "path": "."
    },
    {
      "path": "my-library"
    }
  ],
  "settings": {
    "nrf-connect.applications": [
      "${workspaceFolder}/my-project"
    ],
    "nrf-connect.boardRoots": [
      "${workspaceFolder}/my-library"
    ]
  }
}

MyProject/.west/config

[manifest]
path = my-project
file = west.yml

[zephyr]
base = zephyr

MyProject/my-project/west.yml

manifest:
  projects:
    - name: my-library
      url: git@github.com:my-library.git
      revision: main
      import: west.yml
      clone-depth: 1
  self:
    path: my-project

MyProject/my-library/west.yml

manifest:
  projects:
    - name: nrf
      url: https://github.com/nrfconnect/sdk-nrf.git
      revision: v3.1.1
      import: true
      clone-depth: 1

  self:
    path: my-library

So when I remove this from the folders array in MyProject/my-project.code-workspace, the issue clears up:

    {
      "path": "my-library"
    }

But, then VS Code won't interact with the code in my-library, which I'm often developing at the same time as my-project.

RE: Hint: "self: import: submanifests": file not found

Edvin — Fri, 07 Nov 2025 09:37:51 GMT

Thank you!

Are you intentionally trying to use the v3.1 branch? Is there any reason why you don't want to check out a tag, e.g. v3.1.1? It is often better to work on stable releases. If so, you can install the SDK by using the "Manage SDKs" button (right below "Manage toolchains").

If you for some reason want to use the live v3.1-branch, then can you please upload your entire manifest file? Our VS Code team believes there is something else in that file, causing it to be corrupt. At least they tested with this, and that worked without any issues:

$ cat west.yml 
manifest:
  projects:
    - name: nrf
      url: https://github.com/nrfconnect/sdk-nrf.git
      revision: v3.1-branch
      import: true
      clone-depth: 1
...

If you can't post it here, feel free to send it to me in a DM here on DevZone.

Best regards,

Edvin

RE: Hint: "self: import: submanifests": file not found

ryan_mulder_antrum — Thu, 06 Nov 2025 18:21:47 GMT

RE: Hint: "self: import: submanifests": file not found

Edvin — Thu, 06 Nov 2025 08:35:08 GMT

Try installing a second one, e.g. v3.0.0, just to see the list.

BR,
Edvin

RE: Hint: "self: import: submanifests": file not found

ryan_mulder_antrum — Wed, 05 Nov 2025 20:28:51 GMT

Sorry for the delayed response.

When I select Manage toolchains -> Uninstall toolchain, it prompts me to remove it with a dialog. Perhaps because I only have one toolchain installed?

RE: Hint: "self: import: submanifests": file not found

Edvin — Fri, 31 Oct 2025 10:14:15 GMT

Ok, perhaps they are different for linux and windows.

Can you check whether it is listed if you select Uninstall toolchain using the menu above?

BR,
Edvin

RE: Hint: "self: import: submanifests": file not found

ryan_mulder_antrum — Thu, 30 Oct 2025 12:59:06 GMT

I'm trying to use toolchain 3.1.1 and SDK v3.1-branch

$ nrfutil toolchain-manager list
  Version  Toolchain
* v3.1.1   /home/rmulder/ncs/toolchains/b2ecd2435d

$ ls /home/rmulder/ncs/toolchains
b2ecd2435d  toolchains.json

$ cat /home/rmulder/ncs/toolchains/toolchains.json 
[
  {
    "default_toolchain": {
      "ncs_version": "v3.1.1"
    },
    "schema": 1,
    "toolchains": [
      {
        "identifier": {
          "bundle_id": "b2ecd2435d"
        },
        "ncs_versions": [
          "v3.1.1"
        ]
      }
    ]
  }
]

$ cat west.yml 
manifest:
  projects:
    - name: nrf
      url: https://github.com/nrfconnect/sdk-nrf.git
      revision: v3.1-branch
      import: true
      clone-depth: 1
...

RE: Hint: "self: import: submanifests": file not found

Edvin — Thu, 30 Oct 2025 11:47:34 GMT

What toolchain and SDK version are you trying to use? Because the SHA b2ecd2435d doesn't belong to v3.1.1.

What NCS version are you using in your application?

Best regards,

Edvin

RE: Hint: "self: import: submanifests": file not found

ryan_mulder_antrum — Wed, 29 Oct 2025 19:20:50 GMT

I tried that, but no change.

Here's my toolchain info from the Output pane:

=========== Toolchain validation report for nRF Connect SDK Toolchain v3.1.1 ===========
📦 Using the nRF Connect SDK v3.1.1 at /home/rmulder/devel/<project root folder name was here>
No issues were detected with the toolchain.

RE: Hint: "self: import: submanifests": file not found

Edvin — Tue, 28 Oct 2025 09:53:50 GMT

can you try to uninstall and reinstall the toolchain using VS Code?

I have a new computer, so I don't have all the toolchains installed, but I guess you know what toolchain you are trying to use, and you can try to re-install that one in particular.

Best regards,

Edvin

RE: Hint: "self: import: submanifests": file not found

ryan_mulder_antrum — Mon, 27 Oct 2025 14:52:01 GMT

Hi Edvin,

The `manifest-schema.yml` file that the log refers to is actually present.

Here's a screenshot:

Thanks for your help,

Ryan

RE: Hint: "self: import: submanifests": file not found

Edvin — Mon, 27 Oct 2025 13:59:33 GMT

Hello,

Is the file that the log refers to actually present at that path?

And can you please show me a screenshot of what it looks like?

Best regards,

Edvin