3

Suddenly, the following error message pops up when trying to build a new package using sfdx force:package:version:create.

Unable to parse package2-descriptor.json: invalid attribute 'orgPreferences' at line 1, column 353

This is reproducable on my Win10 and macOS machine. Also, I can rule out that this has something to do with me. It even appears when I revert to older commits on my repository where I know for certain that I was able to build packages from them.

For the sake of completeness, here's my scratch-org-def.json

{
  "orgName": "Partner Billing GmbH",
  "edition": "Enterprise",
  "features": ["StateAndCountryPicklist", "MultiCurrency"],
  "country": "DE",
  "language": "en_US",
  "settings": {
    "lightningExperienceSettings": {
        "enableS1DesktopEnabled": true
    },
    "pathAssistantSettings": {
        "pathAssistantEnabled": true
    },
    "languageSettings": {
        "enableTranslationWorkbench": true
    },
    "chatterSettings": {
        "enableChatter": true
    }
  }
}

Note, the non existing orgPreferences. Since this is for my open source project, you could reproduce this, using my latest commit: https://github.com/jlietzau/partner-billing/tree/feature/PB-67-community.

Does anybody has an idea where this comes from? My hunch is that salesforce fucked up their API that is responsible for creating package versions.

  • 2
    I just started getting the same thing, glad I'm not the only one. I was just about to raise a Partner Support Ticket for this – Adam Erstelle Jan 11 at 18:24
  • Should it help, my scratch org is far simpler. { "orgName": "MyCoolApp", "edition": "Developer", "hasSampleData": true, "features": [] } – Adam Erstelle Jan 11 at 18:34
  • Please do and keep us in the loop :). I'm very relieved that I'm not the only one. I also started having "unexpected errors" on my other production org. – J. Lietzau Jan 11 at 18:37
  • I suspect this is a bug in the CLI – Mohith Shrivastava Jan 11 at 18:43
  • 2
    I sent out a tweet as well. The more the merrier, right? – sfdcfox Jan 11 at 18:55
1

It does appear this error was the result of something done on the Salesforce API side. Trying again 3 hours ago, the command did execute successfully (though it took a bit longer). Should I get any details from the support case, I'll update this.

  • 1
    Something mus still be up, as their commands are taking 15-20 minutes (even for a force:package:version:list ). – Adam Erstelle Jan 12 at 19:45

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.