Known Issues · AppExchange

In Summer '19, upon package upgrade, profile permissions for child objects are not being applied

AppExchange , Packaging , Custom Objects , Partner

When a subscriber updates a package installed in their environment, if the package version being upgraded to introduces a child object that is related to a parent object which was added to the package in an earlier version, then object permissions for the child object are not applied to profiles. This...

Scheduled - Summer '19 Patch 15.0 ·Reported By 20 ·Updated Yesterday

Unable to install package due to error - A newer version of this package is currently installed due to connected app

AppExchange , Packaging

There are instances where a connected app is installed in the org and conflicting with a package being installed. When installing the package it will fail with the error "A newer version of this package is currently installed." Otherwise, an error ID will appear in which the background error is showing...

In Review ·Reported By 6 ·Updated Yesterday

Package install fails if it has Roll-up summary field and child object is protected

AppExchange , Packaging

Package install fails if it has a Roll-up summary field and the child object is protected. When the child object is protected the install process looks for the associated fields and fails.

No Fix ·Reported By 1 ·Updated Today

Links do not respond when adding components to a package in Lightning

AppExchange , Packaging , Partner

When adding package components in Lightning, the links on the page, such as 'next page' and the letter filters, will not respond.

In Review ·Reported By 1 ·Updated Yesterday

Stripe Data Won’t Sync to Checkout Management App (CMA)

AppExchange , Partner

When you set up data syncing using the instructions provided in the CMA’s setup wizard, the sync fails. This can happen because of an issue with the format of the site URL in the “Set Up Data Syncing” step of the instructions.

In Review ·Reported By 0 ·Updated 2 days ago

The LWC component is not getting the label value when we pass a value to a attribute of child component from parent.

AppExchange , Packaging , Platform , Lightning

Custom label values not available on custom Object records when using in parent or Child LWC(Lightning Web Component), only when we pass a value to a attribute of child component from parent ad the Org has namespace enabled.

In Review ·Reported By 0 ·Updated 5 days ago

Patch org creation failure due to permission or feature discrepancy between dev org and patch org

AppExchange , Packaging , Partner

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...

In Review ·Reported By 5 ·Updated 6 days ago

Managed Package upgrade fails due to subscriber deleting a report

Analytics , AppExchange , Packaging

Package subscribers are able to delete reports that are referenced in Lightning Pages which causes package upgrades to fail.

In Review ·Reported By 37 ·Updated 7 days ago

Unable to delete managed record under Custom Metadata Type Records

AppExchange , Packaging

Custom Metadata Records are developer deletable, but cannot be deleted once the package is released.

In Review ·Reported By 2 ·Updated 7 days ago

Deploying change set containing community fails with error: "An unknown exception has occurred"

AppExchange , Change Sets , Communities

This issue occurs when deploying a community from an org to another using change sets. Typically the error thrown when validating the change set in the target org is "An unknown exception has occurred." Below is a technical explanation of how this issue occurs. When a Force.com Site for a community...

In Review ·Reported By 34 ·Updated 8 days ago

1 to 10 of 152 | 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.