If I recall correctly, permissions applied to a signed OBS binary do not apply to other secondary copies of OBS. You will have to remove all OBS related permissions, and then reapply them to the copy that you actually want them to apply to.
This is a bit mistaken, and I apologize for that.
Multiple binaries are not an issue as long as they are codesigned by the same developer. If you have granted one signed OBS binary permissions, and then you install a second OBS binary signed by the same developer as the first one (which should be the case if both were official, signed builds), then the permissions granted to the first binary should work on the second binary. The only time this
could be an issue is if you switched from an x86_64 binary to an arm64 binary, though this is just an unconfirmed theory.
If you previously granted permissions to an
unsigned OBS binary, such as a "nightly" build from our CI, and then tried to run the signed OBS 28 beta builds, then the permissions granted to the first binary will
not be respected for the second binary because the signatures do not match. In this case, the best way to ensure that you are granting permissions to the signed binaries is to remove all existing permissions for any OBS binaries completely, then grant them to the signed binary, and make sure that you only open the signed binary after that.
Deleting old binaries does not, as far as I know, delete permissions. You must delete permissions associated with those old binaries to actually delete permissions.