Package upgrade fails when package contains a Custom App that is assigned to a Permission Set
Last updated 2022-02-10 ·Reference W-4338165 ·Reported By 6 users
Summary
When attempting to upgrade a managed package, subscribers may encounter an error if that package contains a custom Application, and that Application has been deleted from the Subscriber organization.
Error:
1. (Permission_Set_Name) In field: application - no CustomApplication named Custom_App_Name found
Permission_Set_Name: In field: application - no CustomApplication named Custom_App_Name found
Repro
From the Developer Org:
1. Login to a Developer Org
2. Navigate to Setup | Create | App
3. Create a custom App
4. Navigate to Setup | Manage Users | Permission Sets
5. Create a new Permission Set, and edit the Assigned Apps to assign the App you just created.
6. Navigate to Setup | Create | Package
7. Create a managed package, add your App and Permission Set, and upload as two released versions.
From the Subscriber Org
8. Login to a subscriber org
9. Install Version 1
10. Navigate to Setup | Create | App and delete the App created by the package.
11. Attempt to upgrade to Version 2.
The attempt to upgrade will fail with an error:
1. (Permission_Set_Name) In field: application - no CustomApplication named Custom_App_Name found
Permission_Set_Name: In field: application - no CustomApplication named Custom_App_Name found
Workaround
In the Packaging Org, modify the Permission Set to remove the custom App from the Assigned Apps. Upload a new version, and use that to upgrade the subscriber organization.
Reported By (6)
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.