RSC permissions cause app to fail installation in personal scope

I am trying to update an existing up to send notifications. The plan is to use RSC permissions for it.

I configured the manifest (v 1.19) with the following scopes:

  "authorization": {
    "permissions": {
      "resourceSpecific": [
        { "name": "TeamsActivity.Send.Chat", "type": "Application" },
        { "name": "TeamsActivity.Send.Group", "type": "Application" },
        { "name": "TeamsActivity.Send.User", "type": "Application" }
      ]
    }
  },

I then sideloaded it successfully with this configuration into a team and also into a chat.

However when I try to install it into the personal scope directly I get the error in a dialog box: Something went wrong

In the network tab of the web inspector I see that this call fails with 403: 
https://teams.microsoft.com/api/mt/emea/beta/users/apps/definitions/appPackage

The body of the response says:

{"errorCode":"WebApplicationInfoIdConflictOnSideloadingIntoTeam"}

However, when I change the included permissions in the manifest to only TeamsActivity.Send.Group the app installs successfully into personal scope

 "authorization": {
    "permissions": {
      "resourceSpecific": [
        { "name": "TeamsActivity.Send.Group", "type": "Application" }
      ]
    }
  },

So I guess it has nothing to do with an id conflict. I also made sure to remove all old instances of the sideloaded app before (which was never a problem so far).

How can I use all three RSC scopes in my app manifest and still install the app into the personal scope.
Or what could be wrong? Anything I could check to figure out why this is not working but only the TA.Send.Group scope?