No view is registered with id: <extension id> with `github.vscode-pull-request-github` enabled
Describe the bug When starting VSCodium, I'm getting flooded with errors in the notification area which state the following:
No view is registered with id: <extension id>
Please confirm that this problem is VSCodium-specific
- [x] This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.
Please confirm that the issue/resolution isn't already documented
- [x] I checked the Docs page and my issue is not mentioned there.
To Reproduce Steps to reproduce the behavior:
- Install
GitHub.vscode-pull-request-github - Make sure you have extensions installed which provide custom views - some of the extensions causing errors include:
eamodio.gitlensstreetsidesoftware.code-spell-checkerGitHub.vscode-pull-request-githubhbenl.vscode-test-explorermtxr.sqltools
- Open up VSCodium (you might have to restart VSCodium in order to trigger the issue)
- Notice that there is a huge load of notifications concerning missing views
Expected behavior The extensions should work properly
Screenshots

Desktop (please complete the following information):
- OS: Windows 11 Version 21H2
- Architecture x64
- Version 1.70.0
Additional context
You can work around this issue by either downgrading to 1.69.2 (thanks @Maykin-99) or by disabling the "GitHub Pull Requests and Issues" (github.vscode-pull-request-github) extension.
I think I found those few you were looking for... LMK if I got it.
Also happens on Linux.
A workaround is to downgrade to 1.69.2.
Have you tried with only GitLens? I can't reproduce the issue...
Have you tried with only GitLens? I can't reproduce the issue...
I can confirm that it doesn't seem to happen with a fresh installation with nothing but GitLens installed. I'll try to find out what's causing the error, then.
I just ran through an Extension Bisect and it looks like this issue is caused by github.vscode-pull-request-github.
However, it might be important to mention that this issue doesn't occur in Visual Studio Code.
Ok! I'm planning to look into that extension for #1152. So I guess I will also look into this issue :wink:
Awesome! Thank you so much 😄
Issue found, fix on the way. But the deployment would need to wait the next release...
I will keep the issue opened until a new release...