Patch org creation failure due to permission or feature discrepancy between dev org and patch org
Last updated 2020-03-06 ·Reference W-6183254 ·Reported By 37 users
Some partners are finding that when they create a patch org, that the patch org will be created but does not successfully work as a patch org. This is due to the package not being deployed to the org due to a discrepancy in enabled features or permissions between the patch org and the packaging developer org.
We're seeing that some of these issues are reporting an error number that contains -1568177848.
1. Login to the packaging developer org, navigate to the package, and create a new patch org on the "Patch Organization" tab
2. Observe that the patch org doesn't work as a packaging org and an email is received similar to:
Your requested patch development organization was created, but we were unable to set up your package for development. Contact Salesforce Support and provide the following information to complete the setup of this organization before use.
Package: <Package Name>
Patching Version: <Package Version>
Error Number: xxxxxxxx-xxxxxx (-1568177848)
Your user name is below. You'll be asked to set a password when you first log in. Passwords are case sensitive. You'll also be asked to set a password question and answer that will be used if you forget your password.
User Name: <Patch org username>
Create a case with support to have the package redeployed.
Reported By (37)
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.