Can select standard connection for SFDX project, resulting in error

[René Görgens]

Hi Scott,

On an org-based SFDX project, I’m able to configure a standard connection instead of an OAuth connection. This results in the following error: No such host is known when trying to create the offline symbol table or to retrieve metadata.

The documentation at https://bitbucket.org/RoseSilverSoftware/illuminatedcloud/wiki/User_Guide/Create_SFDX_Project says:

Choose an existing scratch org (sfdx_connection_icon.png) or non-scratch/OAuth org (oauth_connection_icon.png), or create one for the project following the instructions provided here.

However would it not be better not to be able to select a standard connection with an SFDX project?

[Scott Wells]

Can you please provide steps that allow you to do this? The project list should filter according to the detected project type (source format vs. metadata format) and not include native connections for source format projects. It sounds like there’s some gap in that logic, and if so, I’d need the exact path that leads to it.

[René Görgens]

Of course, sorry:

• Create a new SFDX project. The message being:

‌

• In the Modules and Connections dialogue, click Add Connection. The message being:

(I think here it said no Dev Hub detected, but I failed to capture this and now I can’t reproduce it.)

• The first time I tried this at home, I got no Authorize Org pop-up. The second time I did:

‌

• If the Authorize Org pop-up appears, close it.
• Select an existing native connection and click OK. The message being:

‌

• Confirm with OK. The message being:

‌

• Confirm with OK.

  • When I tried this at home now, the offline symbol table was successfully generated on both tries.
  • At work, the generation failed.

• Right-click the force-app folder and select Retrieve Metadata

• Select Custom and uncheck Subscribed Only
• Select some metadata (I select stuff within an object that I expect to be represented more granularly in source format) and click Retrieve
• This finally fails:

‌

[Scott Wells]

Gotcha. Yeah, that specific path wasn’t safeguarded but now is (for this weeks' build):

Thanks for providing the exact steps to reproduce.

[René Görgens]

Will be fixed in this week's build

[Scott Wells]

Partial delivery in 2.2.4.4. During final testing I found one corner case where this can still occur due to a stale cache. I’ll leave this open and plan to resolve that instance of the issue for the next build.

[Scott Wells]

Fixed the other instance of this issue for inclusion in the next build. Basically it was due to IC2 trying to cache the sfdx-project.json file during CLI-based project creation before that file is guaranteed to exist. That should put this overall issue to rest.

[Scott Wells]

Fixed the remaining corner case. Delivered in 2.2.4.5.