Launch not available in some of the vault's entries?

I am using latest Bitwarden on my A13-5G Galaxy. Within in its vault there are entries that when selecting the 3 dots to their right, Launch is among the list in the dropdown. However, there are entries that have the same listing without Launch. I have no idea why some entries don’t have Launch? Thanks.

@Adam_S Welcome to the forum!

If you open one of the items that does not offer a Launch function and go to the Edit screen, what is the value of the field URI1, and what is the corresponding URI match detection setting?

URL value=New Entry, and no url site listed.
Furthermore, when looking at the Authenticator Key, there is a lowercase “y” with two dots above it. What does this signify?

Now looking at entries with Launch, I note that their Authenticator Key’s field has a camera icon and “Set up TOTP,” while the URL field says “New URL.”

If you don’t have a URI set, then there’s nothing to launch. All entries with a URI will be available for you to open from your vault.

OK, so the solution would be that when saving a PW for a web site, then I have to put in its url in that field???

And, I assume, PWs for apps, I don’t have to do this???

Lastly, any explanation for “…when looking at the Authenticator Key, there is a lowercase “y” with two dots above it. What does this signify?”

Yes, see Step 4 in these instructions. For websites that will be accessed using a desktop browser, this is easier to do with the Bitwarden browser extension, which automatically fills in the URL of the website that you have visited in your browser.

I’ve seen such characters occasionally (never in Bitwarden, though), and it is usually when I open a binary file in a text editor, or when I open a text file that has been corrupted (so that the data values in the file do not represent ASCII characters anymore).

Did you enter any TOTP Authentication Keys, either manually or using the QR code and camera? Or have you imported vault data from another password manager? Likely something went wrong in an import or possibly in the QR code scan.