SFDX: Refresh SObject Definitions fails with "Cannot read property 'forEach' of undefined" on newest plugin version

[anders-norgaard]

Summary

Everytime the SFDX: Refresh SObject Definitions command is run, it fails with the message "ended with error Failure performing sObject describe Cannot read property 'forEach' of undefined".
This has been testet on multiple devices, and is happening on all refresh types (All, Custom and Standard SObjects).

Steps To Reproduce:

1. Open command palette
2. Select command SFDX: Refresh SObject Definitions
3. Choose one of the three options

Expected result

Expected SObject definitions to be fetched

Actual result

The command fails with error "ended with error Failure performing sObject describe Cannot read property 'forEach' of undefined"

Additional information

Salesforce CLI console output

VSCode console output

VS Code Version: 1.54.1

SFDX CLI Version: 7.90.2-b8f9206a5c

SFDX CLI Integration Plugin Version: v51.4.0

OS and version: Windows 10 20H2

[uip-robot-zz]

This issue has been linked to a new work item: W-9007196

[lcampos]

Hi @jardorr thanks for opening this issue. I haven't been able to replicate this on any of my orgs but I created a tests that could replicate the error on the area I think it might be happening for you. I'm thinking the problem is that the describe calls the feature does against your org are returning no results, can you confirm if you have access to sobjects in the org you are using ?

[anders-norgaard]

Hi @lcampos.
I have the System Administrator profile in the org, and I have full sObject access in the Org Browser.
I do believe the you are correct that the org is returning no results. I suspect this to be due to company policy network restrictions (VPN connection due to WFH). Curiously enough, everything else (Org browser, deploy/retrieve from org, authorize org etc.) works as expected.

[jeffb-sfdc]

@jardorr I wasn't able to reproduce this. We've made a number of enhancements to the Org Browser, so I suspect this issue was fixed and doesn't exist anymore. If you are still able to reproduce this, please let us know, and let us know the repro steps you are performing.

[no-response]

This issue has been automatically closed because there has been no response to our request for more information from the original author. Currently, there is not enough information provided for us to take action. Please reply and reopen this issue if you need additional assistance.