Al: Error when setting breakpoint: Cannot create empty object for type 'TableData'

Created on 28 Sep 2020  Â·  9Comments  Â·  Source: microsoft/AL

Describe the bug
I just tried to 'Debug without publishing' and upon 'Set a breakpoint' I get the error below.

[2020-09-28 14:25:59.82] Error: Cannot create empty object for type 'TableData'

When I add the breakpoints first and then start the debugger, the breakpoint state changes to 'Unverified' and the same error is added to the debug console.

What's might be the cause / how to resolve?

5. Versions:

  • AL Language:

image

bug debugger in-progress

All 9 comments

Seems like the issue is related to the 6.0 vsix used to target a 5.0 / BC 16 NST. When reverting back to the 5.0 vsix, all seems to work fine.

Does this happen when you target a 6.0 / BC 17 NST as well, or is this just a backwards compatibility issue?

I don't have any 6.0 / BC 17 NST running yet. I used the insider vsix to be able to fix newest CodeCop warnings and checked if previously reported issues had been fixed. Then I started targetting my BC 16 NST with the 6.0 vsix and found out about the debugging issue.

Thanks for the clarification. We'll investigate this further.

Does this happen on a basic AL:Go! project? It looks like we've broken something with breakpoints here. If there's a minimal repro you can share, that would help a lot.

There's not a lot I can share. Tried a simple AL : Go! project with the insider vsix (6.x) ... and it fails once the app is publish / webclient is shown, the breakpoint state changes to unverified.

vsix6

and the same with the marketplace vsix (5.x). Once published / webclient is shown, I can freely add/remove breakpoints.

vsix5

In both scenarios, I published with debugging, targetting the same NST (BC 16).

Thank you, this is still very helpful. We're looking into this now and this helps.

@fvet this has been fixed in the latest marketplace release of the VSIX. By extension, the next docker images should contain this soon. We pushed out the marketplace fix first because of the severity.

This is fixed in v6.0.344420

Was this page helpful?
0 / 5 - 0 ratings