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.

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

Error: exports.getOrgApiVersion is not a function #4938

Closed
Deepak-K-Anand opened this issue Jun 21, 2023 · 5 comments
Closed

Error: exports.getOrgApiVersion is not a function #4938

Deepak-K-Anand opened this issue Jun 21, 2023 · 5 comments

Comments

@Deepak-K-Anand
Copy link

Deepak-K-Anand commented Jun 21, 2023

Summary

Unable to deploy code after the recent extension update (58.3.0 - June 21, 2023). Error: exports.getOrgApiVersion is not a function

Steps To Reproduce:

  1. Open any Metadata (Apex, VF Page, LWC etc.)
  2. Right-click and run SFDX: Deploy This Source to Org

Expected result

The metadata should be deployed to the Salesforce org.

Actual result

Presented with an error in the console that says: exports.getOrgApiVersion is not a function

Additional information

Observation: This most likely started appearing after the recent release of 58.3.0 - #4917

image

Salesforce Extension Version in VS Code:
v58.3.0

SFDX CLI Version:

{
  "cliVersion": "@salesforce/cli/1.77.1",
  "architecture": "darwin-x64",
  "nodeVersion": "node-v18.16.0",
  "osVersion": "Darwin 22.5.0",
  "shell": "zsh",
  "rootPath": "/Users/deepakkanand/.local/share/sfdx/client/7.199.7-cc56357/sf",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 2.1.9 (core)",
    "@oclif/plugin-commands 2.2.14 (core)",
    "@oclif/plugin-help 5.2.9 (core)",
    "@oclif/plugin-not-found 2.3.23 (core)",
    "@oclif/plugin-plugins 2.4.7 (core)",
    "@oclif/plugin-search 0.0.16 (core)",
    "@oclif/plugin-update 3.1.13 (core)",
    "@oclif/plugin-version 1.3.3 (core)",
    "@oclif/plugin-warn-if-update-available 2.0.36 (core)",
    "@oclif/plugin-which 2.2.19 (core)",
    "@salesforce/cli 1.77.1 (core)",
    "apex 2.2.14 (core)",
    "auth 2.7.14 (core)",
    "data 2.3.12 (core)",
    "deploy-retrieve 1.8.18 (core)",
    "info 2.6.8 (core)",
    "limits 2.3.13 (core)",
    "login 1.2.7 (core)",
    "org 2.7.2 (core)",
    "schema 2.3.10 (core)",
    "settings 1.4.5 (core)",
    "sobject 0.1.18 (core)",
    "source 2.10.5 (core)",
    "telemetry 2.1.6 (core)",
    "templates 55.4.11 (core)",
    "trust 2.4.12 (core)",
    "user 2.3.9 (core)"
  ]
}

OS and version:

Chip: Apple M1 Pro
macOS: 13.4 (22F66)
@Deepak-K-Anand
Copy link
Author

Downgraded the version to v58.1.1 on the following:

  1. Salesforce CLI Integration
  2. Salesforce Extension Pack
  3. Salesforce Extension Pack (Expanded)

Observation: The Extension started working again and I was able to deploy the metadata. So this certainly validates that it was the recent release that has caused this issue.

image

@lkaneTAG
Copy link

I'm having this issue as well. Had to downgrade the Salesforce Extension Pack and the Salesforce CLI Integrations to v58.2.0 to get my retrieves and deploys to work again

@lexcraw4d
Copy link

lexcraw4d commented Jun 21, 2023

Downgraded, same issue -- it will still work via command cli e.g. sfdx force:source:deploy -p pathHere

@jeffb-sfdc
Copy link
Contributor

@Deepak-K-Anand thanks for reporting this! We looked into the issue and we will be publishing a patch release in a few hours.

@jeffb-sfdc
Copy link
Contributor

@Deepak-K-Anand thanks agin for reporting this issue. We've built and published a hotfix which resolved and fixes the issue. I'm going to close this ticket. If you encounter any other issues, please let us know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants