#Package Dependency0 discussing

Creating a scratch org for 2GP development with dependencies: too slow

We are just setting out on our journey with 2GP. Our first 2GP is a new "extension package" that integrates our core product (an existing 1GP) with a third-party product (another existing 1GP). As such, a scratch org for the 2GP development requires us to have both packages installed since the integration will add fields to objects from both packages and include Apex code using objects from both packages.

I have added appropriate details in the sfdx-project.json file listing the two dependencies, something like:

{

    "namespace": "mynamespace",

    "sfdcLoginUrl": "https://login.salesforce.com",

    "sourceApiVersion": "48.0",

    "packageDirectories": [

        {

            "path": "force-app",

            "default": true,

            "package": "My Integration Package",

            "versionNumber": "0.0.1.NEXT",

            "definitionFile": "config/myint-scratch-def.json",

            "dependencies": [

                {

                    "package": "CorePackage@2.1.2.1"

                },

                {

                    "package": "ThirdParty@5.10.4.1"

                }

            ]

        }

    ],

    "packageAliases": {

        "CorePackage@2.1.2.1": "04t0N000000AAAAAAA",

        "ThirdParty@5.10.4.1": "04t4P000002BBBBBBB"

    }

}

Of course, this doesn't actually handle installation of the packages when creating the scratch org, and I have written some scripting to pull required details from this JSON file (plus installation keys from "elsewhere") to handle the necessary force:package:install commands prior to pushing our new 2GP code to the scratch org. (See more on this in the final two paragraph.)

However, right now (with a basically empty 2GP development source tree) simply creating the scratch org and deploying the two dependencies is taking just short of an hour.

We normally work with a scratch org per developer per task, so we know the scratch org is clean and fit for purpose. We also have continuous integration which again creates a scratch org each time code is committed to git. This becomes untenable when it takes this long just to create the scratch org and get it populated.

In the short term we can drop CI for this package and have developers use long lived scratch orgs (30 days) for all the 2GP development, so the creation time only happens monthly, but this is not ideal and could expose us to issues with cruft the devs create on their orgs.

What I'm looking for is a way to speed up the creation of the scratch org, including the installed packages.

It appears there was some work done around allowing scratch orgs to be created using a TSO snapshot, presented at Dreamforce 18 (see https://twitter.com/FishOfPrey/status/1044644000316026880) which would be ideal here I believe. We could install the 1GPs into the TSO, create a snapshot and build the scratch org from that. However, the mechanism used (the "template" property in the scratch def JSON file) isn't documented and there's no other mention of this approach elsewhere in official documentation.

I understand from a comment on Stack Exchange (https://chat.stackexchange.com/rooms/107428/discussion-on-question-by-phil-w-how-to-speed-up-scratch-org-creation-when-it-in) that this feature hasn't been GAed, may not even be available for activation on request and only "marginally" improved performance (I am waiting for further feedback on the two latter points).

As an aside, it seems daft to me that you cannot include all the details necessary, in the sfdx-project.json file, to allow the SFDX CLI to create and initialize the scratch org completely. The only two "extras" I can see to achieve this would be to:

• Allow specification of the installationKey for a dependency in the dependencies list.
• Require any dependencies of dependencies that need an installationKey to have an explicit entry in the package dependencies list so the installationKey can be defined.

The force:org:create command could then take an additional parameter, such as "--install-dependencies", that causes the installation of the required dependencies in an appropriate order and leveraging the installation key values when required (and indeed there could be a new SFDX CLI command, e.g. force:org:install:dependencies or similar, to deal with this process directly too that the force:org:create command would simply delegate to when the parameter is set). This would avoid the need to write custom scripting just to install dependencies.

Hi All,

I have a question regarding the package version creation. I am trying to distribute our Happy soup ORG into different unlocked packages. But facing some issues.

1. we have a Docusign managed package installed in the happy soup ORG

2. One of the Object in that Docusign managed package has a reference to a custom object. 

3.  First I created an unmanaged package with that Custom object to get all the related dependencies. 

4. Once I converted from the mdapi to src format, I could see the managed package object with a single reference field in src format like dsfs__DocuSign_Status__c.object-meta.xml

5. When I tried to push it to scratch ORG, then I got issues. saying 

'Must specify a non-empty label for the CustomObject'

6. Then I copied all the metadata of that dsfs__DocuSign_Status__c object in src format and pushed the whole object metadata to scratch ORG. Then it worked fine without no issues. 

7. Once everything done with no compilation issues, I tried to create a package version. Then I am getting the issues with this object saying

You're trying to include CustomObject dsfs__DocuSign_Status__c in Package ver 0.1. This component already exists in Package null, which Package ver 0.1 depends on. You can't include the same component in both packages.

What should I do now? I am completely stuck here. Please help me.

Thanks in advance

Hi,

I'm currently struggling with a project involving dependent packages.

I currently have a child package which adds an email alert using an object created by the parent package. The parent package has no workflows at all, there's no directory named workflows/ either and installing the package and checking the components shows no workflows visible.

However, when I try to build the package, I always get a very strange error:

> $ sfdx force:package:version:create --package ChildPackage --path force-app --installationkey XXXXX --wait 10 --definitionfile config/project-scratch-def.json

> (truncated)

> ERROR running force:package:version:create:  You're trying to include Workflow namespace__Application__c in Package ver 0.2. This component already exists in Package ver 0.1, which Package ver 0.2 depends on. You can't include the same component in both packages.

I assume that Package ver 0.2 is the child object and Package ver 0.1 is the parent object which matches their actual version.

Details about the environment:

1. Both packages are attached to the same dev hub

2. Both packages created with this command: `sfdx force:package:version:create --package PackageName --path force-app --installationkey XXXXX --wait 10 --definitionfile config/project-scratch-def.json`

3. I'm trying to install them to a temporary scratch org - the parent package installs fine, the child package fails

Here's the `sfdx-project.json`

```

{

    "packageDirectories": [

        {

            "path": "force-app",

            "default": true,

            "package": "ChildPackage",

            "versionName": "ver 0.2",

            "versionNumber": "0.2.0.NEXT",

            "dependencies": [

                {

                    "package": "ParentPackage",

                    "versionNumber": "0.1.0.LATEST"

                }

            ]

        }

    ],

    "namespace": "namespace",

    "sfdcLoginUrl": "https://login.salesforce.com",

    "sourceApiVersion": "47.0",

    "packageAliases": {

        "ChildPackage": "0HoXXX",

        "ParentPackage": "0HoXXX",

        "ParentPackage@0.1.0-9": "04tXXX",

        ... multiple versions of ChildPackage ...

    }

}

```

Here is the project-scratch-def.json:

```

{

  "adminEmail": "XXX",

  "edition": "Developer",

  "features": [

    "Workflow",

    "Communities",

    "Sites"

  ],

  "settings": {

    "lightningExperienceSettings": {

      "enableS1DesktopEnabled": true

    },

    "communitiesSettings": {

      "enableNetworksEnabled": true

    }

  }

}

```

@Unlocked Packages, we are using the package strategies for the upcoming applications in our ORG. But when creating the unlocked packages, I am seeing some strange issues. Here are the two issues I see when creating package versions

1. Compilation issue

When executing the force:source:push everything looks good with no compilation errors. But when creating a package version, I am getting this issue. But, after 2-3 retrying attempts to create the package version, It would be successful. This is even happening in case of package upgrade with the same error. But, the package upgrade works fine after 2-3 retrying upgrade attempts. I even googled with this error but no luck. What exactly is this error mean? I am getting too frequently these days.

ERROR running force:package:version:create:  : Compilation Failure

        /c/ak_page/ak_page.js:0,0 : LWC1002: Error in module resolution: Maximum call stack size exceeded,ak_page: Compilation Failure

        /c/ak_page/ak_page.js:0,0 : LWC1002: Error in module resolution: Maximum call stack size exceeded

2. Error with non-related components while creating the package versions

While creating package version today, I got this issue. I am seeing errors with unrelated components. We even don't have any components with these names in our ORG/package. Why am I seeing these issues. But re-executing the creation worked fine. We have a package dependency on 04t4N000000omLKQAY package, but it's showing me 04t4N000000omLK in the logs with the following exceptions. These are not part of our ORG/Package.  

Request in progress. Sleeping 30 seconds. Will wait a total of 6000 more seconds before timing out. Current Status='Queued'

Request in progress. Sleeping 30 seconds. Will wait a total of 5970 more seconds before timing out. Current Status='Verifying dependencies'

ERROR running force:package:version:create:  An error occurred while trying to install a package dependency, ID 04t4N000000omLK: IMS_ViewBOLPdf: Invalid definition for null:IMS_ViewBOLPdfController: ApexService.getType() return null with currentNamespace: c, namespace: null, name: IMS_ViewBOLPdfController

Appreciate your response.