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

Salesforce CLI and v52 compatibility #1054

Closed
firatesmer opened this issue Jun 20, 2021 · 9 comments
Closed

Salesforce CLI and v52 compatibility #1054

firatesmer opened this issue Jun 20, 2021 · 9 comments
Labels
investigating We're actively investigating this issue

Comments

@firatesmer
Copy link

Summary

Salesforce CLI can't deploy v52 (latest version) related items to org when you right click and select deploy on VS Code. I tried to create package but the version of the package was 51 but the version in package.xml was 52.0. I did try "SFDX_API_VERSION=52.0" as well but no luck.

Steps To Reproduce:

  1. Update package.xml version to 52
  2. Right click and select "SFDX: Deploy Source in Manifest ro Org"
  3. Doesn't work.

Salesforce CLI version: sfdx-cli/7.105.0 win32-x64 node-v14.17.0
OS version: Windows 10 21H1 (19043.1055)

@firatesmer firatesmer added the investigating We're actively investigating this issue label Jun 20, 2021
@github-actions
Copy link

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

@WillieRuemmele
Copy link
Member

Hi @firatesmer if you run the command via the CLI directly does it succeed? Or is this only an issue when using VSCode?

@WillieRuemmele
Copy link
Member

Hey @firatesmer have you had a chance to try it out with the CLI directly? you can also try the new beta source plugin

@WillieRuemmele WillieRuemmele added the more information required Issue requires more information or a response from the customer label Jun 24, 2021
@firatesmer
Copy link
Author

Hey @WillieRuemmele,
Sorry for delay.

Yes, I've tried with CLI and the result is still version v51 even command prints out
WARNING: apiVersion configuration overridden at 52.0

@no-response no-response bot removed the more information required Issue requires more information or a response from the customer label Jun 27, 2021
@WillieRuemmele
Copy link
Member

Hi @firatesmer and what if you run sfdx config:list or get a list of environment variables with echo %PATH% (on windows) and look for SFDX_API_VERSION being set. If any of those are set it will override. Let me know how it goes 👍

@firatesmer
Copy link
Author

Hi @WillieRuemmele,

sfdx config:list =>

WARNING: apiVersion configuration overridden at "52.0"

Name Value Location
apiVersion 52.0 Global

But still prepares the package with v51.

@rajesh-kemisetti
Copy link

I am having exactly this same issue. For me the version during deployment is always 50 no matter what I do. I even uninstalled CLI and re-installed to see if there would be any impact and no luck. I have even tried to set 52 version globally but except for this WARNING: apiVersion configuration overridden at 52.0 nothing has changed.

I am now on sfdx-cli/7.109.0-fc6b854

@mshanemc
Copy link
Contributor

are you still seeing version issues with more recent CLIs? Anyone else been able to reproduce this?

FWIW, more recent deploy commands will tell you what version they're using during the deploy or beta:push

@mshanemc mshanemc added the more information required Issue requires more information or a response from the customer label Dec 10, 2021
@firatesmer
Copy link
Author

Hey @mshanemc,

I've just updated the CLI and it works as expected now, no more error.

CLI Version : sfdx-cli/7.130.1 win32-x64 node-v16.13.1

@no-response no-response bot removed the more information required Issue requires more information or a response from the customer label Dec 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
investigating We're actively investigating this issue
Projects
None yet
Development

No branches or pull requests

4 participants