peternhale
peternhale
Anyone seen an improvement with this issue?
@rondinardo would you share the results of `sfdx version --verbose` and `sfdx plugins`.
@Dane1986 Not sure which version of `sf` you have. ``` npm install @salesforce/cli -g sf --version @salesforce/cli/1.38.0 darwin-x64 node-v16.13.1 sf env create sandbox -h This command is in beta. Create...
@lukecotter Using your repo steps I am unable to reproduce the push conflict. I was able to cause a conflict by changing a class both locally (with end of file...
@RohitGagan16 would you mind posting the results of `sfdx version --verbose`. Thanks in advance.
@tggagne thank you for the additional info. This may be a keychain issue in the ssh session. You can try this to confirm. ``` ssh @localhost security unlock-keychain -p ""...
@RohitGagan16 I tried to reproduce this on Windows, but could not. Fresh install of sfdx-cli and a rather small set of source. Could you run the command again, but this...
@RohitGagan16 I'll ask one more favor. Run the failing command again with `--loglevel debug`. But before you do that go to folders `~/.sf` and `~/.sfdx` and rename or remove files...
Thanks for reporting the issue. We have determined the cause. The workaround will require the presence of property sourceApiVersion in your project json.
@sulemanzia When you retry the command does it succeed or does the error occur again?