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.