-
Notifications
You must be signed in to change notification settings - Fork 78
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
Mutliple issues with both beta and non-beta commands #1814
Comments
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. |
Update. Well, neither or beta or non-beta commands function properly. Using command sfdx force:package:uninstall also fails Uninstall Failed for the previous QA Console Package version 0.8.0.6 (0.8.0) with subscriber install id 04t5Y000001nUp0QAE from com sandbox ([email protected]) with errors null Uninstall has been performed successfully but the command execution failed. |
Uninstall Failed for the previous Finalize package version 1.25.0.56 (1.25.0 HotFix troubleshoot) with subscriber install id 04t5Y000001eUhSQAU from com sandbox ([email protected]) with errors Missing message package_uninstall_report:InProgress for locale en_US. |
@bdovh Could you provide the errors you are seeing, aside from the missing message. I could also use the results of |
We want to move towards the beta commands and away from the packaging commands that are in the |
I had multiple issues with beta commands as well as with Regarding beta command. These two commands fail and do not provide the correct results sfdx force:package:beta:uninstall:report sfdx force:package:beta:install:report |
@bdovh thank for your response. Could you provide the results of |
I am always using the latest version and I had to switch back to sfdx force: package :uninstall:report and sfdx force: package :install:report commands because these failures are blockers for our CI development process... I have outlined errors above Uninstall Failed for the previous QA Console Package version 0.8.0.6 (0.8.0) with subscriber install id 04t5Y000001nUp0QAE from com sandbox ([email protected]) with errors null and previously there was just failures but no error messages (so either install or uninstall may actually perform successfully or fail but beta commands reported status in a wrong way and didn't specify the failure reason) |
@bdovh I tried to install the package QA Console with both beta and prod commands. Both produce the same error.
Is this the error you are seeing? Also, if you give me the |
No, that's not. I was trying to uninstall it and received an error when uninstalling |
@bdovh So the uninstall error you are seeing is can you share the 04t ids I need to try and reproduce that error? I need to install before I can uninstall. |
I had the similar error with the base package version Uninstall Failed for the previous Finalize package version 1.25.0.56 (1.25.0 HotFix troubleshoot) with subscriber install id 04t5Y000001eUhSQAU from com sandbox ([email protected]) with errors Missing message package_uninstall_report:InProgress for locale en_US. |
there were several different errors: Missing message package_uninstall_report:InProgress for locale en_US |
Uninstall Failed for the previous Finalize package version 2.0.0.87 (2.0.0 Agreement Status Revamp) with subscriber install id 04t5Y000001eUgjQAE from com sandbox ([email protected]) with errors Missing message package_uninstall_report:InProgress for locale en_US. Such errors were reoccurring each time I built a new package version |
Uninstall Failed for the previous Finalize package version 1.24.0.64 (1.24.0) with subscriber install id 04t5Y000001nUovQAE from qaapp3 sandbox ([email protected]) with errors Missing message package_uninstall_report:InProgress for locale en_US. |
status=0 |
and if we are asking about the SFDX CLI version, it was always the latest one Run ./.github/workflows/installSFDX.sh added 868 packages, and audited 1079 packages in 16s 72 packages are looking for funding found 0 vulnerabilities status=0 |
Run ./.github/workflows/installSFDX.sh added 868 packages, and audited 1079 packages in 22s 72 packages are looking for funding found 0 vulnerabilities Uninstalling 04t5Y000001eUgjQAE: sfdx force:package:uninstall -p 04t5Y000001eUgjQAE --json |
v16.18.0 added 868 packages, and audited 1079 packages in 15s 72 packages are looking for funding found 0 vulnerabilities status=0 |
v16.18.0 added 868 packages, and audited 1079 packages in 14s 72 packages are looking for funding found 0 vulnerabilities Uninstall Failed for the previous Finalize package version 1.25.0.56 (1.25.0 HotFix troubleshoot) with subscriber install id 04t5Y000001eUhSQAU from com sandbox ([email protected]) with errors Missing message package_uninstall_report:InProgress for locale en_US. |
v16.18.0 added 868 packages, and audited 1079 packages in 14s 72 packages are looking for funding found 0 vulnerabilities Uninstall Failed for the previous Finalize package version 1.24.0.64 (1.24.0) with subscriber install id 04t5Y000001nUovQAE from qaapp3 sandbox ([email protected]) with errors Missing message package_uninstall_report:InProgress for locale en_US. |
The error |
@bdovh Using these packages
I was able to install each Finalize first followed by qa console into a scratch org with both beta and prod packaging commands. I was also able to uninstall each with both beta and prod commands. I used salesforce-alm v 54.8.4 and @salesforce/plugin-packaging version 1.10.8. Both of these will be available in sfdx-cli latest-rc coming out later this week (Friday, given the holiday). |
are you using --json parameter and reading the status from json response? |
|
echo $(sfdx force:package:uninstall -p $previousPackageVersion --json) > uninstall.txt |
@bdovh No I did not use |
maybe it is not working when using --json attribute |
@bdovh Are you willing to give sfdx-cli@latest-rc a try? |
I already used it. However, I switched back to non-beta commands, because using beta commands breaks our workflow and blocks our development process :( We don't have capacity to constantly debug problems with CI |
Not asking you to use beta commands. Does 7.179.0 solve the issues you describe against the prod packaging commands? |
Sorry, I don't understand. Do you mean if I tried to use the |
This issue has not received a response in 7 days. It will auto-close in 7 days unless a response is posted. |
bots, please do not close issues |
Looks like for ALM commands I am affected by this known issue https://trailblazer.salesforce.com/issues_view?id=a1p4V000001svfwQAA |
Run ./.github/workflows/installSFDX.sh added 984 packages, and audited 1195 packages in 15s 77 packages are looking for funding found 0 vulnerabilities Executing command: sfdx force:package:version:create -d force-app --postinstallscript PostInstall -x -w 60 --codecoverage -b sfdx-issues-1814 --json |
looks like the prod package version commands are working now |
Heya @bdovh, I'm glad version |
I have opened a SF Support ticket but it has been more than a month and I can't get exact answer from higher management. Should we use beta or non-beta commands if both of them fail?
Summary
Mutliple issues with both beta and non-beta commands
Steps To Reproduce:
Try to use sfdx force:package:version:create
On the same codebase but with different package id there are different multiple errors.
While if using sfdx force:package:beta:version:create, it is created without issues.
Try to use sfdx force:package:beta:install command.
If installation fails, no clues are output to troubleshoot why install fails.
Try to use sfdx force:package:beta:uninstall command.
If installation fails, no clues are output to troubleshoot why install fails.
While if using sfdx force:package:uninstall command, if there are failures, they are returned in json or other formats.
The text was updated successfully, but these errors were encountered: