Unable to deploy managed custom fields to a Winter 25 scratch org

[simonwatson]

I have a project which can sf project deploy start to a Summer 24 scratch org but fails to deploy to a Winter 24 preview org. It seems to be a problem with custom fields which are already in a managed package (linked to the project).

I can deploy static resources, custom permissions, connected apps, apex classes (which don’t depend on custom objects/fields). I can create a new custom object with a field and deploy it ok. I can also deploy an existing custom object (with fields removed) ok, and even deploy new custom fields added to it, but deploying one of its existing fields fails with an error An unexpected error occurred. Please include this ErrorId if you contact support: 2119260834-1194743 (-1516727936)

I'm using the latest SF CLI: @salesforce/cli/2.57.7 darwin-arm64 node-v20.15.0

[github-actions]

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]

Hello @simonwatson 👋 It looks like you didn't include the full Salesforce CLI version information in your issue.
Please provide the output of version --verbose --json for the CLI you're using (sf or sfdx).

A few more things to check:

• Make sure you've provided detailed steps to reproduce your issue.
  • A repository that clearly demonstrates the bug is ideal.
• Make sure you've installed the latest version of Salesforce CLI. (docs)
  • Better yet, try the rc or nightly versions. (docs)
• Try running the doctor command to diagnose common issues.
• Search GitHub for existing related issues.

Thank you!

[simonwatson]

{
  "architecture": "darwin-arm64",
  "cliVersion": "@salesforce/cli/2.57.7",
  "nodeVersion": "node-v20.15.0",
  "osVersion": "Darwin 23.6.0",
  "rootPath": "/Users/simon/.nvm/versions/node/v20.15.0/lib/node_modules/@salesforce/cli",
  "shell": "zsh",
  "pluginVersions": [
    "@muenzpraeger/sfdx-plugin 0.5.0 (user) published 1582 days ago (Tue May 12 2020)",
    "@oclif/plugin-autocomplete 3.2.2 (core)",
    "@oclif/plugin-commands 4.0.13 (core)",
    "@oclif/plugin-help 6.2.10 (core)",
    "@oclif/plugin-not-found 3.2.18 (core)",
    "@oclif/plugin-plugins 5.4.6 (core)",
    "@oclif/plugin-search 1.2.7 (core)",
    "@oclif/plugin-update 4.5.5 (core)",
    "@oclif/plugin-version 2.2.11 (core)",
    "@oclif/plugin-warn-if-update-available 3.1.13 (core)",
    "@oclif/plugin-which 3.2.12 (core)",
    "@salesforce/cli 2.57.7 (core)",
    "apex 3.4.5 (core)",
    "api 1.2.1 (core)",
    "auth 3.6.51 (core)",
    "data 3.6.3 (core)",
    "deploy-retrieve 3.12.0 (core)",
    "dev 1.3.3 (user) published 304 days ago (Sat Nov 11 2023) (latest is 2.4.2)",
    "info 3.4.2 (core)",
    "limits 3.3.27 (core)",
    "marketplace 1.2.24 (core)",
    "org 4.5.4 (core)",
    "packaging 1.27.1 (user) published 314 days ago (Wed Nov 01 2023) (latest is 2.8.4)",
    "schema 3.3.26 (core)",
    "settings 2.3.15 (core)",
    "signups 2.0.13 (user) published 255 days ago (Sat Dec 30 2023) (latest is 2.5.14)",
    "sobject 1.4.32 (core)",
    "source 3.5.16 (core)",
    "telemetry 3.6.10 (core)",
    "templates 56.3.14 (core)",
    "trust 3.7.25 (core)",
    "user 3.5.26 (core)",
    "@salesforce/sfdx-scanner 4.3.0 (user) published 76 days ago (Tue Jun 25 2024) (latest is 4.5.0)",
    "sfdx-plugin-cli 1.5.0 (link) /Users/simon/git/axsy/sfdx-plugin-cli"
  ]
}

[DallasDeuce]

fyi - we were getting similar error (although different error number) today Sept 10, 2024. We logged sfdc support case & sfdc support responded:

"Upon initial investigation of the Gack ID mentioned in the description, it seems like there is a new bug logged for the issue you are facing during your Deployment.
 The Bug ID is W-16488056 and currently, the product team is doing their investigation for this issue. Currently, I don't see any public Known issue like yet on the Bug. You can refer to the Bug ID W-16488056 to get future updates on this Bug."

[iowillhoit]

That error code (Gack ID) is coming from the server. There probably not anything the CLI team can do about this one.

Could you try running the failing command with the --dev-debug flag and sharing the output?

Also, unrelated, we now bundle plugin-packaging with the CLI. Uninstall your "user" installed version with sf plugins uninstall @salesforce/plugin-packaging and it will fall-back to the version bundled with the CLI

[simonwatson]

Could you try running the failing command with the --dev-debug flag and sharing the output?

@iowillhoit: yes, here's the output debug.txt

Also, unrelated, we now bundle plugin-packaging with the CLI. Uninstall your "user" installed version with sf plugins uninstall @salesforce/plugin-packaging and it will fall-back to the version bundled with the CLI

Thanks for the tip, I'd forgotten the user-installed version was there.

[iowillhoit]

Thanks @simonwatson. I don't see notice anything that would indicate that this is an issue with the CLI. I see some folks looking into this on the ticket @DallasDeuce mentioned (W-16488056)

[github-actions]

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.