Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Debug API Not working - Cannot read properties of undefined #319

Closed
jayendranarumugam opened this issue Jul 24, 2023 · 4 comments · Fixed by #330 · May be fixed by #322
Closed

Debug API Not working - Cannot read properties of undefined #319

jayendranarumugam opened this issue Jul 24, 2023 · 4 comments · Fixed by #330 · May be fixed by #322

Comments

@jayendranarumugam
Copy link

Does this occur consistently?
Repro steps:

  1. Trying to Debug the API

APIM Details:
Developer Tier
Platform Version: stv2
Region: EAST US 2
Network: Internal VNET
apiVersionConstraint.minApiVersion : 2019-12-01

Action: azureApiManagement.debugPolicy
Error type: TypeError
Error Message: Cannot read properties of undefined (reading 'primaryKey')

Version: 1.0.6
OS: darwin
OS Release: 22.5.0
Product: Visual Studio Code
Product Version: 1.80.1
Language: en

Call Stack 
extension.bundle.js:479:71081
OperationConsole.<anonymous> extension.bundle.js:479:71044
fulfilled extension.bundle.js:479:68637
@zakariazafar
Copy link

any update on this issue?

@quanterion quanterion mentioned this issue Aug 9, 2023
Open
@jayendranarumugam
Copy link
Author

jayendranarumugam commented Aug 10, 2023 •
edited
Loading

After some investigation, it seems this issue is happening only if the management api is 2019-12-01 . If i change this to null the issue is not happening. But the problem of this workaround will be security reason from ms

Microsoft recommends to make this to value not null and keep it 2019-12-01 or higher The reason for this would be
To prevent service secrets from being shared with read-only users, the minimum API version should be set to 2019-12-01 or higher.

So i think we should not start practising the workaround by making the api version to null and fix the extension code to support the version 2019-12-01 and above

@malincrist malincrist mentioned this issue Sep 1, 2023
Merged
@jayendranarumugam
Copy link
Author

@DeagleGross / @malincrist / @quanterion thanks for fixing the issue. Is this part of any new release ? Is there a place we can check the changelog or release doc ?

@malincrist
Copy link
Member

malincrist commented Sep 8, 2023 •
edited
Loading

Hello @jayendranarumugam , the fix will come with a new release. You can track GitHub releases or the changelog from the VSCode extension.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
3 participants
@zakariazafar @jayendranarumugam @malincrist