Closed tarcang closed 8 months ago
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.
huh. I don't have my windows machine this week, sorry. Can you try a few things for me?
[remove the = stuff for flags and refer to the --metadata-dir
sf project deploy start -o <your_scratch_org> -g --metadata-dir b2clocal21ToDeploy.zip -w 60 --verbose --api-version 59.0 --json --single-package
[same but without --single-package]
sf project deploy start -o <your_scratch_org> -g --metadata-dir b2clocal21ToDeploy.zip -w 60 --verbose --api-version 59.0 --json
huh. I don't have my windows machine this week, sorry. Can you try a few things for me?
[remove the = stuff for flags and refer to the --metadata-dir
sf project deploy start -o <your_scratch_org> -g --metadata-dir b2clocal21ToDeploy.zip -w 60 --verbose --api-version 59.0 --json --single-package
[same but without --single-package]
sf project deploy start -o <your_scratch_org> -g --metadata-dir b2clocal21ToDeploy.zip -w 60 --verbose --api-version 59.0 --json
I will 👍
Hello @mshanemc , I have tried the commands you have shared but unfortunately still got the same output. I have looked into this a little bit. Looking into the deployment logic I don't see any apparent reason why this wouldn't work other than the fact that there is something wrong with the JSZip
library with its Windows compatibility. I am not sure, just putting out an idea on where it could be going wrong.
This issue has not received a response in 7 days. It will auto-close in 7 days unless a response is posted.
Hello @mshanemc, any updates on this issue? I will try to help as much I can.
This issue has not received a response in 7 days. It will auto-close in 7 days unless a response is posted.
This issue has not received a response in 7 days. It will auto-close in 7 days unless a response is posted.
I've tried replicating this on windows.
I created a scratch org using this scratch definition file https://github.com/forcedotcom/commerce-on-lightning/blob/develop/config/b2b-project-scratch-def.json
When I deploy the zip file, I got back various errors (navigation menus that don't have network associated with them)
I also tried installing the commerce plugin and running sf commerce scratchorg create
but that resulted in a lot of errors like INVALID_EMAIL_ADDRESS
. Looks like it requires a --username
for some reason? That at least got the org to create.
Then I deployed your zip file. I got more failures.
In all cases, I didn't have long deploys and it seemed to behave correctly (returning results for the errors).
What am I missing?
This issue has not received a response in 7 days. It will auto-close in 7 days unless a response is posted.
Summary
sf project deploy start
is not able to deploy single package as a zip file in Powershell. If I run the same command in MacOS bash terminal, the behavior is fine.Steps To Reproduce
Prereq: Have an Windows VM or an environment that runs Powershell 5.
sf commerce scratchorg create
given that you have a devhub, from @salesforce/commerceExpected result
I would get feedback about the components and they should end in success just like in my MacOS system.
Actual result
Nothing is actually deployed in my org.
System Information
Additional information
Note: the output shell says 'cmd.exe' but I am actually running that from Powershell.
$PSVersionTable output:
The doctor output of the command I shared in Windows:
I will not share the doctor command output in my macOS since it is long but I do get successes with the individual components.