Can't install app, trapped between 'New app macro alias conflicts' and ' could not be installed as a local app as it has previously been installed from Atlassian Marketplace'

Hi

For our app we had different app keys for development, staging and production.

Then we started to get a ‘Installation failed. New app macro alias conflicts with existing app macro alias.’ recently.

Looks like that was introduced this year.. So, we changed the key to be the same for all environments, so that we can install the app in develop environments.

However, now we tried to install the app on our staging environment for the release, and we get a '‘The app “ch.mibex.confluence.include” could not be installed as a local app as it has previously been installed from Atlassian Marketplace’ error:

So, out primary staging environment is now trapped between the two errors. We can’t use another key, because we get an error that the macro keys are in use. We can’t use the production key, because we get an error that the Market place app was once installed.

Is there a way to ‘reset’ the UPM manager to accept the staging version again? Or avoid the ‘macro’ key conflict between staging and prodution app keys?

Thanks for any idea.

What seems to work is to remove the ‘alias’ fields in the ‘atlassian-connect.json’. Then we can use different app keys.

However, I’m not sure when we get the ‘New app macro alias conflices with existing app macro alias’. With which macro alias do we conflict?

  1. With our own app in the market place? That would explain why the installation works in some workspaces with the same key. If it conflicts with the ‘marketplace’ version of the app, then it would be better to keep the same app key for production, development and staging in the future.
  2. Or does it conflict with a Atlassian built in macro? The alias is ‘include’. But then why does changing to the production app key remove the warning? If it conflicts with a built in macro, then we should remove the alias and keep the different app keys between production, development and staging. @Andrew.Ngo