I currently run into some scenarios where I have different credentials for independent apps within the same domain.
They are saved independently using distinct URLs, unique by subdomain or port, but the autofill seems to put the first one that matches the domain, that is incorrect.
I believe it should have a priority rule, complete URL match, then subdomain or port match, then domain.
Something like that, to avoid mixing auto fills.
Welcome, @mencargo to the community!
Bitwarden has a wide variety of match rules that you can use to accomplish this.
Their mindset is a bit different, though. Match detection shrinks the list. It is a filtering mechanism, not a sorting mechanism.
@mencargo Welcome to the forum!
Do these independent apps have distinct login credentials, or do they all use the same username/password?
If they have different credentials, and are saved in separate login items, then you should be able to resolve the issue simply by setting the URI match detection method to Host, either globally (by changing the default URI match detection method, under Settings > Autofill), or by customizing the URI match detection individually for each of the stored URL strings (to do so, edit the Login item, click the 
icon next to the URI field, and then select “Host” in the drop-down menu; don’t forget to save the changes to the login item).
If this doesn’t address the issue, then please share the specific format of the URL strings for the apps that are not being properly matched by Bitwarden.