Clarification needed: Updating existing Platform v2.3 apps vs migrating to v3.0

App Platform
, ,
1

Hi community,

During yesterday’s Community Hours, the host mentioned that existing Platform v2.3 apps will retain their install options, but developers will no longer be able to update them on v2.3.
I would like to clarify what this means for our deployment workflow moving forward:

  • Can we upgrade the existing app to v3.0 directly? If we migrate our current v2.3 codebase to Platform v3.0 (following the migration guide), can we publish that v3.0 code as an update/new version to the same existing app listing in the Developer Portal?

  • Or do we have to publish it as an entirely new app? Will we be forced to create a completely separate app listing on the marketplace/custom app portal for the v3.0 version, requiring users to reinstall a new app?

I want to ensure we don’t disrupt our current users, so any confirmation on whether the app ID/listing can be preserved during the v3.0 upgrade would be incredibly helpful!

Thanks in advance for the clarity!

2

Hi @Krishna_M,

To clarify, you do not need to publish a completely new app listing or force your users to reinstall.

The upgrade process is handled as a standard application update:

  • Preserve App Identity: You can migrate your existing Platform v2.3 codebase to Platform v3.0 using the migration guide.

  • Publish as an Update: The newly packaged v3.0 code can be submitted as a new version under the exact same app listing in the Developer Portal.

  • Seamless Transition: This ensures that your App ID remains unchanged and that your existing users receive the update smoothly, without disruption to their current installations.

The restriction mentioned during Community Hours only applies to submitting updates built on the legacy v2.3 platform architecture. Upgrading the framework of your existing app listing to v3.0 is the recommended path forward.

Best,

Himanshu