Given this detail about referencing an explicit version of a connected app from a 1GP managed package to include it in a 2GP package, what are the implications of updating an expiring certificate for this connected app in the packaging org?

Will the 2GP package need any updates in order for the connected app to continue to function in subscriber orgs? Will it work seamlessly using the newly updated certificate just as 1GP packages do?

Package Connected Apps in Second-Generation Managed Packaging


2 Answers 2


You don't need to upload a new version of the Connected App, as it is a "live" system. The only requirement is that you include the correct version so that the dependency is formed.


This is not true. You will require a new version of the package to be uploaded. I have tried it, and it doesn't allow any connected app version that's not in a managed package.

  • Your answer could be improved with additional supporting information. Please edit to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center.
    – Community Bot
    Commented Mar 26, 2022 at 4:43

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .