Error when creating a scratch org - Error (1): A scratch org was created with username [email protected], but the settings failed to deploy due to: [Error] settings/SocialProfile.settings : Not available for deploy for this API version

[camerongoodman]

Summary

Attempt to create a new scratch org with socialProfileSettings: enableSocialProfiles true added to the project-scratch-def.json file. Returns the error

Creating Scratch Org... Error
Error (1): A scratch org was created with username [email protected], but the settings failed to deploy due to:
[Error] settings/SocialProfile.settings : Not available for deploy for this API version

Steps To Reproduce

create a new SF project

• sf project generate -n Project_Name -t Standard

modify the project-scratch-def.json file, add socialProfileSettings , so it looks like this

{
  "orgName": "BUG",
  "edition": "Developer",
  "features": ["EnableSetPasswordInApi"],
  "settings": {
    "lightningExperienceSettings": {
      "enableS1DesktopEnabled": true
    },
    "mobileSettings": {
      "enableS1EncryptedStoragePref2": false
    },
    "socialProfileSettings": {
      "enableSocialProfiles": true
    }
  }
}

attempt to create the scratch org

• sf org scratch create -f config/project-scratch-def.json -a MyOrg

Observe error

Creating Scratch Org... Error
Error (1): A scratch org was created with username [email protected], but the settings failed to deploy due to:
[Error] settings/SocialProfile.settings : Not available for deploy for this API version

Note - the scratch org is created, however the settings are not deployed and alias is not assigned.

Attempted with APIs 60, 59 and 48

IMPORTANT Provide a repository that's configured to reproduce the issue. If you are unable to provide a repo, please explain why not. The more info we have from the start, the faster we can resolve your issue. We may close your issue if you don't include proper instructions.

• Generate a project with sf project generate or fork dreamhouse-lwc.
• Provide detailed step-by-step instructions on how to reproduce the issue.

https://github.com/camerongoodman/sf-cli-org-create-bug-2729.git

Expected result

Scratch org is created successfully

Actual result

Creating Scratch Org... Error Error (1): A scratch org was created with username [email protected], but the settings failed to deploy due to: [Error] settings/SocialProfile.settings : Not available for deploy for this API version

System Information

WSL2 - Ubuntu

{
  "architecture": "wsl-x64",
  "cliVersion": "@salesforce/cli/2.28.6",
  "nodeVersion": "node-v18.19.0",
  "osVersion": "Linux 5.15.146.1-microsoft-standard-WSL2",
  "rootPath": "/home/cam/.nvm/versions/node/v18.19.0/lib/node_modules/@salesforce/cli",
  "shell": "bash",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 3.0.7 (core)",
    "@oclif/plugin-commands 3.1.2 (core)",
    "@oclif/plugin-help 6.0.12 (core)",
    "@oclif/plugin-not-found 3.0.10 (core)",
    "@oclif/plugin-plugins 4.2.1 (core)",
    "@oclif/plugin-search 1.0.13 (core)",
    "@oclif/plugin-update 4.1.10 (core)",
    "@oclif/plugin-version 2.0.12 (core)",
    "@oclif/plugin-warn-if-update-available 3.0.10 (core)",
    "@oclif/plugin-which 3.0.15 (core)",
    "@salesforce/cli 2.28.6 (core)",
    "apex 3.0.22 (core)",
    "auth 3.3.11 (core)",
    "community 2.4.5 (user)",
    "data 3.0.19 (core)",
    "deploy-retrieve 3.2.11 (core)",
    "info 3.0.21 (core)",
    "limits 3.1.7 (core)",
    "marketplace 1.0.20 (core)",
    "org 3.3.11 (core)",
    "packaging 1.26.1 (user)",
    "schema 3.1.1 (core)",
    "settings 2.0.22 (core)",
    "sobject 1.1.9 (core)",
    "source 3.1.10 (core)",
    "telemetry 3.1.11 (core)",
    "templates 56.0.13 (core)",
    "trust 3.3.6 (core)",
    "user 3.2.7 (core)",
    "@salesforce/sfdx-scanner 3.17.0 (user)",
    "rec-build-sfdx-plugin 0.1.0 (link) /home/cam/work/rec/rec-build-sfdx-plugin",
    "sfpowerkit 6.1.0 (user)"
  ]
}

Additional information

[github-actions[bot]]

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[bot]]

Hello @camerongoodman :wave: 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!

[mdonnalley]

@camerongoodman Thanks for providing a repo - super helpful 🏆

Looking at the metadata coverage report, SocialProfileSettings isn't supported for the metadata api, which is why you can't deploy it

[camerongoodman]

@camerongoodman Thanks for providing a repo - super helpful 🏆

Looking at the metadata coverage report, SocialProfileSettings isn't supported for the metadata api, which is why you can't deploy it

@mdonnalley we have used this Org Setting for more than 2 years now and it just stopped working. The metadata coverage report you linked has nothing there for v60 but it is there for v59 and earlier so please check it again.

[camerongoodman]

API Version 60

API Version 59

[mdonnalley]

@camerongoodman Sorry I missed that.

This is likely not a CLI issue, unless you can identify an older version of sf that's able to deploy those settings successfully. It's almost certainly an issue in the metadata api.

I'm going to leave this open and mark as owned by another team. Your best bet is to submit a support case since those are typically higher priority for the metadata team than github issues.

[github-actions[bot]]

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.