bug(developer): Internal debugger no longer accessible in KMDev 17

[MattGyverLee]

Describe the bug

I recently moved up to KM 17, and while "Test Keyboard on Web" works, the internal debugger that I was using in 16 can no longer be activated.

Reproduce the bug

1. Open a keyboard (I tested sil_cameroon_qwerty, sil_cameroon_azerty, and even sil_tchad) to have one I didn't write.
2. Go to the Build tab and compile. It compiles.
3. Click "Start debugging."
4. KM jumps to the Layout Tab and displays this dialog box:
   You must include debug information to start the debugger. Check 'Include debug information' in the keyboard menu.
   
5. I checked the include option, and it was in fact checked:
   
6. Checking, unchecking, and recompiling have no effect. The dialog still comes up when trying to debug and the debugger never loads.

The internal debugger still has useful tools for dealing with dead keys and testing RALT sequences, so it would be nice if it returned to working.

Expected behavior

Debugging should load the debugger as it did in KM16 and not get stuck in a loop of enabling something that's already enabled. Can you reproduce this?

Related issues

No response

Keyman apps

• Keyman for Android
• Keyman for iPhone and iPad
• Keyman for Linux
• Keyman for macOS
• Keyman for Windows
• Keyman Developer
• KeymanWeb
• Other - give details at bottom of form

Keyman version

worked in 16.0.141, failing in 17.0.198 and later (203).

Operating system

Win 11 Pro 22H2

Device

Windows Desktop

Target application

KmDev Debugger

Browser

No response

Keyboard name

sil_cameroon_qwerty, sil_tchad, presumably all of them as it appears to be a logic bug rather than a keyboard bug.

Keyboard version

No response

Language name

No response

Additional context

No response

[MattGyverLee]

Oh, it looks like this was fixed 8 hours ago. #9901
You can close this bug if it's fixed.

[MattGyverLee]

This is a duplicate of a closed issue #9885