Creating package from the installation directory gives me error

[wailoktam]

I am getting the following error:

sampleVendor: Not available for deploy for this organization
VoiceCall: Invalid fullName, must end in a custom suffix ( for ex. __c )
Service_Cloud_Voice: In field: pageOrSobjectType - no CustomObject named VoiceCall found
and another error saying that the voicecall object is invalid (the msg is originally in another language)

when following this step:

Create a Package Version
'''
sfdx force:package:version:create --package "" --codecoverage --installationkeybypass --wait 20
'''

in this guide.

Can you tell me what is wrong? I think I follow every previous step in the guide.

[wailoktam]

I sort of figure out some of the reasons for the above errors. But this leads me to more questions. The Complaint about Voicecall is because the developer edition I am using does not have Voicecall objects. I suppose this is the effect of not being able to turn on service cloud voice. But the documentation for telephony partners do not mention that partners need something other than the developer edition. Can you confirm with me that this is an edition problem, that the developer edition is not capable of developing solution for service cloud voice due to missing support for voice related objects.

The instruction on creating package version without validation in the README here is not going to solve the problem as package without validated cannot be promoted like it is mentioned in the README here.

[Ben-Liao]

We have the same errors as you describe. So to develop the scv-partner, it needs to participate to be the scv first?

[v-goyal-sfdc]

To be able to create a promotable package you will need to add SCV partner telephony to the org. You can do this by creating a case with salesforce partner support. This doc contains details on how to do this: https://quip.com/WY1nARc2mpli

[estrudels]

@wailoktam Please consider closing this Issue Salesforce representative has gotten back to you with a solution/fix to your problem. Thank you :)

[estrudels]

@v-goyal-sfdc @vivektikoo-force Would you consider closing this issue as Work As Expected? Thanks :)

[eyerean]

Hello, the way our team solved this was by defining the definitionFile prop to point to our scratch org definition json.
So we used something like:
sfdx package version create --package="our test package" --installation-key-bypass --wait 10

with an sfdx-project.json like this:

{
  "packageDirectories": [
    {
      "path": "force-app",
      "package": "our test package",
      "versionName": "ver 0.1",
      "versionNumber": "0.1.0.NEXT",
      "default": true,
      "definitionFile": "config/project-scratch-def.json" // <------ this one pointing to our scratch org
    }
  ],
  "namespace": "our-ns",
  "sfdcLoginUrl": "https://login.salesforce.com",
  "signupTargetLoginUrl": "https://gs0.salesforce.com",
  "sourceApiVersion": "58.0", // <----- important for the Voice Extension to work
  "packageAliases": {
    "our test package": "0HLALALA",
  }
}

This made our package version being created successfully and not throw errors at all.