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

Cannot create package version while converting 1GP to 2GP managed package using sf package convert. #2474

Closed
ashishrajbanshi opened this issue Sep 19, 2023 · 3 comments
Labels
area:packaging investigating We're actively investigating this issue owned by another team The Salesforce CLI team does not own this work but will pass on the information to the correct team. validated Version information for this issue has been validated

Comments

@ashishrajbanshi
Copy link

ashishrajbanshi commented Sep 19, 2023

Summary

While migrating 1st gen package to 2nd gen managed package using sf package convert only package is created with 0Ho id. The command should also create package version.

Steps To Reproduce

  • Identify 1st generation Package Id starts with 033.
  • Create a test DX project
  • Convert the package using command.
    sf package convert --installation-key test -v debhubUsername --package 033.. --wait 20
  • Run following command to verification:
    sf package list --verbose
    sf package version list -p 0Ho.. -v debhubUsername

IMPORTANT
You can use any test project.

Expected result

There should be package version list of newly converted package while viewing version lists after using sf package command.

Actual result

Only package id is shown while using sf package convert.

System Information

{
"cliVersion": "@salesforce/cli/2.9.8",
"architecture": "win32-x64",
"nodeVersion": "node-v18.17.1",
"osVersion": "Windows_NT 10.0.22621",
"shell": "cmd.exe",
"rootPath": "C:\Users\user21\AppData\Roaming\nvm\v18.17.1\node_modules\@salesforce\cli",
"pluginVersions": [
"@oclif/plugin-autocomplete 2.3.8 (core)",
"@oclif/plugin-commands 2.2.25 (core)",
"@oclif/plugin-help 5.2.19 (core)",
"@oclif/plugin-not-found 2.4.1 (core)",
"@oclif/plugin-plugins 3.6.1 (core)",
"@oclif/plugin-search 0.0.22 (core)",
"@oclif/plugin-update 3.2.3 (core)",
"@oclif/plugin-version 1.3.10 (core)",
"@oclif/plugin-warn-if-update-available 2.1.0 (core)",
"@oclif/plugin-which 2.2.32 (core)",
"@salesforce/cli 2.9.8 (core)",
"apex 2.3.14 (core)",
"auth 2.8.16 (core)",
"data 2.5.9 (core)",
"deploy-retrieve 1.17.13 (core)",
"info 2.6.42 (core)",
"limits 2.3.34 (core)",
"login 1.2.30 (core)",
"marketplace 0.2.1 (core)",
"org 2.10.7 (core)",
"packaging 1.22.1 (user)",
"schema 2.3.25 (core)",
"settings 1.4.28 (core)",
"sobject 0.2.7 (core)",
"source 2.10.33 (core)",
"telemetry 2.3.2 (core)",
"templates 55.5.11 (core)",
"trust 2.6.10 (core)",
"user 2.3.32 (core)",
"@salesforce/sfdx-scanner 3.15.0 (user)"
]
}

PASTE_VERSION_OUTPUT_HERE

Additional information

I have followed the following steps in attach screenshot.
image

@ashishrajbanshi ashishrajbanshi added the investigating We're actively investigating this issue label Sep 19, 2023
@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.

@github-actions github-actions bot added the validated Version information for this issue has been validated label Sep 19, 2023
@mshanemc mshanemc added area:packaging owned by another team The Salesforce CLI team does not own this work but will pass on the information to the correct team. labels Sep 19, 2023
@github-actions
Copy link

We have determined that the issue you reported exists in code owned by another team that uses only the official support channels. To ensure that your issue is addressed, open an official Salesforce customer support ticket with a link to this issue. We encourage anyone experiencing this issue to do the same to increase the priority. We will keep this issue open for the community to collaborate on.

@mshanemc
Copy link
Contributor

@ashishrajbanshi Thanks for reporting this, but the packaging team doesn't work with github issues.
They'll only work with Salesforce support cases, and that'll give you the opportunity to share the pkg1 info with them so they can replicate this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:packaging investigating We're actively investigating this issue owned by another team The Salesforce CLI team does not own this work but will pass on the information to the correct team. validated Version information for this issue has been validated
Projects
None yet
Development

No branches or pull requests

2 participants