Forum Discussion
Install failures - App cannot be installed due to a supersedence relationship conflict
From what I can see, there could be issues if there were dependencies or supersedence on the old version - but that's not the case here. How is the assignment on both apps?
This is not a fix to this issue, but if I were you, I would use PSADT, remove the old versions first, and install the newest version—without any dependencies or supersedence.
From what I can see, there could be issues if there were dependencies or supersedence on the old version - but that's not the case here. How is the assignment on both apps?
This is not a fix to this issue, but if I were you, I would use PSADT, remove the old versions first, and install the newest version—without any dependencies or supersedence.
NicklasOlsen Here's the newer app's assignment:
And the older app's assignment:
It wouldn't have anything to do with some of the members of the Test group not being part of the Required group on the older app, would it? Or a mixture of devices in the DG groups vs. users (UG groups)?
- Hi,
Sorry for the delay. Did you manage to find a solution?
A good thing to remember is to never mix devices and users in your targeting.- Making progress on this. It's been a busy week, so haven't had a chance to look at this again until today. Upon further testing, it seems that both versions can live on the computer, so perhaps supersedence isn't even necessary. Thanks for the tip on not mixing devices and users.