Troubleshoot Package Conversion Failures

Here are some possible error scenarios that can occur when you convert a package.

API Version

Salesforce API version 57 is the minimum API version required for converting a package from first-generation packaging (1GP) to second-generation packaging (2GP). If you encounter errors during conversion, first make sure that the package version you’re converting was created using Salesforce API version 57 or later. If your package is using a lower API version, create a 1GP package version using the latest API version, then try the conversion process again.

RecordType Errors

If the package you’re converting contains a RecordType, you must specify it under object settings in a scratch org definition file. For example,

1"objectSettings": {
2    "Contact": {
3    "defaultRecordType": "default"
4    }
5    }

Then specify the scratch org definition file when you run the package conversion CLI command.

1sf package convert -p 033xx0000004Jx3 –-definition-file config/project-scratch-def.json

Org Shape Errors

An org shape is a stored representation of a source org’s baseline setup. In the conversion process, the org shape is used to create the 2GP version of the 1GP package.

When you convert a 1GP package to 2GP, and you have not previously set up an org shape for the source 1GP packaging org, we create an org shape for you so that we’re using a replica of your 1GP packaging org’s baseline setup. To learn more about org shapes, see Create and Manage Org Shapes and Troubleshoot Org Shape.

If you already have an org shape set up for your 1GP packaging org, we use your existing org shape in the conversion process. When you have an existing org shape, you can sometimes experience org shape issues in the conversion process.

If you encounter an org shape error when you run the sf package convert command, delete the packaging org’s existing org shape and then recreate the org shape. Then, try the conversion process again.

If you continue to experience org shape errors, contact Salesforce Partner Support for help.

Permission Sets for Code Coverage

When you use the sf package convert command with the --code-coverage flag, the conversion process runs the packaged Apex tests to validate the code coverage. If the permission sets required to run the tests aren’t defined, the package conversion can fail.

To resolve this issue, add the required permission sets to the sfdx-project.json file. Make sure that the package name is also in the sfdx-project.json file, so that the permission sets can be identified.

This example sfdx-project.json file adds the SampleAccess apexTestAccess permission set.

1{
2  "packageDirectories": [
3    {
4      "versionName": "ver 0.1",
5      "versionNumber": "0.1.0.NEXT",
6      "path": "<YOUR APP PATH>",
7      "default": true,
8      "package": "<YOUR PACKAGE NAME>",
9      "versionDescription": "",
10      "apexTestAccess": {
11        "permissionSets": [
12          "SampleAccess"
13        ],
14        "permissionSetLicenses": []
15      }
16    }
17  ],
18  "namespace": "<YOUR NAMESPACE>",
19  "sfdcLoginUrl": "https://login.salesforce.com",
20  "sourceApiVersion": "63.0",
21  "packageAliases": {
22    "<YOUR PACKAGE ALIAS>": "<YOUR PACKAGE ID>"
23  }
24}

After you update the sfdx-project.json file, try the conversion process again.

Picklist Value Errors

If your package references a custom picklist value that isn’t included in Salesforce’s StandardValueSet, a picklist error occurs during package conversion.

For more details on Standard Value Sets, StandardValueSet in Metadata API Developer Guide.

To resolve this error, follow these steps.

Create a package.xml file that follows this example. Replace the example AccountType value with the object identified in the error you received. Update the version field to the current Salesforce API version

1<?xml version="1.0" encoding="UTF-8"?>
2     <Package xmlns="http://soap.sforce.com/2006/04/metadata">
3       <types>
4         <members>AccountType</members>
5         <name>StandardValueSet</name>
6       </types>
7       <version>64.0</version>
8     </Package>

Authenticate to your packaging org. The required picklist values should be present in your packaging org
Run the project retrieve Salesforce CLI command. Replace the variables for org alias and path, with the actual values you need.
1sf project retrieve start --manifest package.xml --target-org <org-alias> –-output-dir <path>
After the retrieve command completes, a new file is created in your force-app/main/default/standardValueSets directory. The name of the file will be AccountType.standardValueSet-meta.xml, where AccountType is the object you specified in your package.xml file.
Create a parent and child folder in your project root

New parent folder: seed-metadata/

New child folder: standardValueSets/

Only standardValueSet metadata type is allowed in the seed-metadata folder
Note
Move the <object>.standardValueSet-meta.xml file into the seedmetadata/standardValueSets/ directory you created.
Run the package conversion CLI command and specify the --seed-metadata flag and the path to your seed metadata file.

sf package convert --package <033xxxx> --seed-metadata=<path-to-seedmetadata>

If you package encounter new errors for other picklist values, repeat these steps.

First-Generation Managed Packaging Developer Guide