We have two Apps (a Full version and a Lite version) that used to have the same macro key (say macro-example-key). Both apps could be installed at least in Feb’s release.
A few clients installed both versions. They probably installed the Lite version first and then installed the Full version (paid). They both work fine as our Apps handle that macro the same way.
On the last release (2nd April) we noticed that neither of the two versions can be updated.
It seems to be related to Prevent Connect apps with macro alias conflicts from installing.
It is an important upgrading path for our clients to upgrade from Lite to Full. Could someone please confirm the behavior has changed? It is much appreciated if someone could advise what we can do now?
Apparently, we cannot simply rename one key as other clients are relying upon this key. Or is there a migration path that we could utilize?
@Andrew.Ngo , mentioning you because you authored the previous post.