Diagnostic display not working

[Serty9088]

Minecraft version: 1.21.124
Debugger version: 1.26.2
VSCode version: 1.106.2

So, if I open the "Show Live Diagnostics" or "Open Diagnostic Replay" tab, there are 2 options that I see:

1. Empty data when Minecraft is not connected or replay is not running (everything is clear here)
2. Just a grey screen with nothing on it. This happens when the debugger is connected and the world is not paused or when I press "Play" if I pressed "Open Diagnostic Replay".

And, the tab basically just doesn't work. Although the data itself doesn't seem broken (I tried decoding the diagnostic replay manually, and it's perfectly valid JSON). So, my suspicion is that it is a data reading issue. (The rest of the features seem to work correctly. And by the way, this problem exists on both of my devices.)

launch.json if needed:

{
    "version": "0.3.0",
    "configurations": [
        {
            "type": "minecraft-js",
            "request": "attach",
            "name": "Debug with Minecraft",
            "mode": "listen",
            "targetModuleUuid": "68983664-934a-4b11-bb0e-2ece40b380b5",
            "localRoot": "${workspaceFolder}/development_behavior_packs/",
            "port": 19144
        }
    ]
}

[SBLMikeDemone]

I was unable to reproduce this with:
Minecraft Version: 1.21.124 on Windows
Debugger Version: 1.26.2 and 1.27.0
VSCode Version: 1.104.0 and 1.106.3

Here's a very simple behavior pack:
SimpleRepro.zip

My repro steps were:

1. Create the world with the behavior pack added
2. Open up VSCode in the behavior pack's folder
3. In the Run And Debug window, Click the "Start Debugging" button with "Debug Simple Repro" selected
4. In Minecraft, run /script debugger connect
5. Go to the Minecraft Debugger extension view and Click "Show Live Diagnostics"

All the UI appears to populate:

Is there a step I'm missing?

[Serty9088]

@SBLMikeDemone Hello, I found the exact problem. I tried creating a new pack, and everything worked. After a couple of tests, I realized that if the pack name (specifically, in manifest.json -> header -> name) included a "+" char, these menus wouldn't open. After I removed the "+," everything started working, but I think there are other characters that could be causing the issue.