Salesforce Known Issues
Trailblazer Community

2GP Managed Package version creation fails when using Ancestry and Roll-up summary field

Packaging , Metadata , Salesforce DX

2GP Managed Package version creation fails when using Ancestry and Roll-up summary field

Scheduled - Spring '21 ·Reported By 5 ·Updated 2 days ago

Some managed package fails to upgrade in partial copy sandbox if the package contains asset file

Packaging , Sandbox , Partner

Some customers may not be able to upgrade managed package in their partial copy sandbox if the package contains asset file component. Error on the component: 1. An unexpected error occurred. Please include this ErrorId if you contact support: ... (2100495319) AssetFileName: An unexpected error occurred....

In Review ·Reported By 54 ·Updated 4 days ago

Package un-installation is failing on an Internal Server Error number.

Packaging

Package un-installation is failing on an Internal Server Error number: 1705825137 or 894020651.

Scheduled - Spring '21 ·Reported By 7 ·Updated 3 days ago

Package upgrade fails if the Apex Controller for Lightning Component is newly added and is referred from a Lightning Page

Apex , Packaging , Lightning

Package upgrade fails if the Apex Controller for Lightning Component is newly added and is referred from a Lightning Page. Error message: The pull upgrade of your package failed. An unexpected error occurred. Please include this ErrorId if you contact support: 1234567890-12 (123456789) Some_Lightning_Page:...

In Review ·Reported By 4 ·Updated 3 days ago

[2GP] Package upgrades fail with gack when package has post-install script and version number is 0.x.x.x

Packaging , Salesforce DX

During upgrade of a second-generation managed package, a gack occurs during initialization of the post-install script when the version of the package being upgraded is 0.x.x.x. Note that 0 is a valid major version number for 2nd-gen packages, unlike 1st-gen. Expected: ~~~~~~~~ Package upgrade to...

In Review ·Reported By 21 ·Updated 4 days ago

Unmanaged Custom Field on Managed Package Object being returned with Namespace when making "Describe" call from Managed code in Subscriber Org

Apex , API , Packaging

Unmanaged Custom Field on Managed Package Object being returned with Namespace when making "Describe" call from Managed code in Subscriber Org. However, when called out from unmanaged code, then it has no Namespace prefix.

In Review ·Reported By 11 ·Updated 4 days ago

"An Apex Class that implements the Messaging.InboundEmailHandler interface must be selected" error occurs when upgrading package

Packaging

When upgrading the package to a new version, the following error occurs: --- The Apex Class selected is not valid. An Apex Class that implements the Messaging.InboundEmailHandler interface must be selected. --- The error occurs even valid Apex class that implements the Messaging.InboundEmailHandler...

In Review ·Reported By 10 ·Updated 4 days ago

Apex class does not respect the installed package version dependency

Apex , Packaging

Apex class is not respecting the installed package version dependency of P1 package in P2 package if we override P1 package version in subscriber class and if that is called before manage package class.

Scheduled - Spring '21 ·Reported By 4 ·Updated 4 days ago

Patch org creation fails due to deleted managed custom metadata type record

Packaging , Partner

Patch org creation fails if managed custom metadata type record is deleted

In Review ·Reported By 1 ·Updated 4 days ago

Patch Orgs fail to be created when including LWC and/or Aura components that reference a Lightning Message Channel

Packaging , Lightning

Update: November 17, 2020 A fix has been submitted for this issue. Enablement of the fix requires you to contact Salesforce Support and ask that the fix be applied to your Organization that is encountering the issue. Issue Description: When trying to create a patch org that contains an LWC and/or...

In Review ·Reported By 24 ·Updated 5 days ago

1 to 10 of 438 | Next

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.