Removing slashes breaks URLs

So, eagle-eye, if you look at the first paragraph in my original post, what's this? 
A working URL with a public DNS?  What??? 
Here that working URL is again from that 1st paragraph of my original post since you missed it the 1st time. 

https://rx.meijer.com/Landing/ 

So, here's what's happening.  I can still recreate this bug.

1. I was working in the 1Password app (v 8.11.0, latest OTA update I can get via Google Play Store) on my Pixel 8A running Android 16 (latest OTA update I can get).
2. I tap + New Item.
3. I tap Login
4. I copy/paste in https://rx.meijer.com/Landing/ to the new Login entry in my 1Passwod app
5. There's a trailing forward slash or / character at the end of the URL when I do so.
6. I save my new entry in 1Password.
7. I find my new entry in 1Password for https://rx.meijer.com/Landing/
8. I tap that entry (above) to open it. 
9. I tap the website area of the above entry, which looks like https://rx.meijer.com/Landing , with NO trailing forward slash or / character at the end of the URL appearing. 
10. And I get sent to https://rx.meijer.com/Landing
    1. With NO trailing forward slash or / character at the end of the URL appearing in the URL or web address bar of my mobile web browser.
    2. This happens whether I use Firefox or Chrome.
    3. My father experiences the same behavior.
    4.  When I edit this entry in 1Password and try to fix the URL field, the URL appears as https://rx.meijer.com/Landing/
    5. But even when I save that entry again, I still get sent to https://rx.meijer.com/Landing 

I'll summarize the issue now with bullet points.

• This URL does NOT work: https://rx.meijer.com/Landing
• This URL DOES work: https://rx.meijer.com/Landing/
• 1Password makes me think I entered https://rx.meijer.com/Landing/
• 1Password actually uses https://rx.meijer.com/Landing
• The difference is the trailing forward slash or / character at the end of the URL
• I can use https://rx.meijer.com just fine.
• I can use https://rx.meijer.com/Landing/# instead.  Works fine.
• But I thought that it's probably going to cause others and 1Password an issue if their 1Password app is breaking web addresses that are otherwise correct because the 1Password Android app strips the trailing slash in the URL when it shouldn't and can break websites when it does that.

Let me know of any other questions you have.

Also, I had a typo in the URLs in the last paragraph. 
I was helping my elderly parents. 
But this is still an issue. 
My father has a website with the URL in question in his 1Password app on his Android phone, though we found a workaround.   
See above for justification for my use of has instead of "had" or for implying my father owned the website.  He doesn't.
This is still a bug to fix. 

I had a typo in https://rx.meijer.com/Landing/  .   Not the 1st time I listed the website in my 1st paragraph: https://rx.meijer.com/Landing/ .  But I did have typos in my final paragraph in both instances of the URL there.  I apologize for having a typo when reporting an issue.  I'm sure you would never do that.  I didn't have my glasses on, and I was helping my elderly parents at the time, believe it or not. 

The issue is with the trailing forward slash character at the end of URL's in 1passwrod entries entered into the 1passwor app on Android.  This forward slash character DOES get removing when I add a new Login entry to the 1password app in the Android app on my Google Pixel 8a phone.  I'm using Android version 8.11.0 (81100029, on PRODUCTION channel) of the 1password app.  I just tried to update it again today.  No updates.  I just recreated the same issue again.  My version of the Android OS itself on my Pixel 8a is Android 16, updated July 5, 2025, build number BP2A.250704.008

Step-by-step, here's how to recreate the issue using the 1Password Android app

1. Tap +New Item blue button icon in lower right.
2. Tap Login.
3. Copy in the URL https://rx.meijer.com/Landing/ 
   1. Note that there is a trailing forward slash at the end of the URL, and that is exactly how I entered it, and note that this is a real website, real public DNS and everything.
4. Chang the name of the New Item from Login to Login test, or what you will, if you want.
   1. I called mine Login test.
5. Click the Save blue button in the upper right.
6. Find and tap the new Login test item.
7. Note the website is listed as https://rx.meijer.com/Landing and there is no / or forward slash at the end of the URL.  But here in the Android app, this is NOT merely a display problem.
8. Tap the website line to open that website in your mobile web browser on your Android device.
9. Note that the website that you are taken to is https://rx.meijer.com/Landing without the trailing forward slash character at the end of the URL. 
   1. That breaks the URL
   2. That means that that URL or web address does not work without the trailing forward slash.
10. When I edit the URL or web address entry in the 1Password app, I see https://rx.meijer.com/Landing/ , but when I save it again, it still displays as https://rx.meijer.com/Landing , and it still opens from the 1Password app to https://rx.meijer.com/Landing .
    1. That means that the 1Password app does not include the trailing forward slash when you try to open the website from 1Password, nor display that, even though I entered that in.

If that isn't making sense still, or it's just too wordy, I'll use a couple of your examples.

See, when I enter in this into my 1Password Android app...

https://example.com/path/

...I unfortunately have this as the URL that gets used when I try to click and open the website from within the 1Password App on my Android phone.

 https://example.com/path 

Now, to be clear, the example.com/path website above will still work whether or not you have a / after the word path or not.

But that's not the case for  https://rx.meijer.com/Landing  , with no trailing forward slash at the end.  That URL will not work.  It does have a public DNS for the domain though.

Also, I want to thank you for being so kind.  Most people who answer forum questions see the people they help as, well, stupid, less than human.  They get off on feeling smug, or they have anger issues because of feelings of inadequacy.  Or they are trying to relive past moments where a user was a little ignorant or slow or goofy, and they got to brag about that to their friends or co-workers.  Not you.  You understand that someone took the time and effort to explain an issue they had.  You understand that most people are not going to report a problem unless they actually had a problem, and that they probably encountered a real issue.  And for most of the rest, they at least could use a little friendly guidance, or at least a friendly response.  I'm sure that's why you have this job, or volunteer your time to this forum.  Otherwise, if this job got you so angry and you hated it so much, you surely would devote time to finding a different job.  Or to finding a different way of spending your extra time, if this isn't your job.  Some people in that situation might also create a template with a friendly opening line or two and friendly closing line or two, just for the initial response, and then fill in the middle, not only so they didn't have to waste their time as much being friendly, but also so that they could just respond as they wished in the middle, and the tone of that response would probably not be noticed.  That'd be a smart way to go.   But not you.   You respond with care and real concern without a template.  And I thank you for that. 

As for any other accidental uses of words or typos, sorry for those too.  I wish I could be a master of tone in emails like you are, and say things like "what do you intend us to understand by the fact that..."  I'd be scared of using something like the royal "we" or royal "us."  It might sound arrogant or disrespectful.  Not you.

No worries if neither you nor anyone else responds to this. 

I'm perfectly happy if you don't respond to this again, or if you respond in a less friendly way.  I'm just hoping to get help either way.  Again, I'm not used to friendly customer service in these situations.

I can use the workaround fixes of either using https://rx.meijer.com/ or https://rx.meijer.com/Landing/# 

Hopefully others who have this issue will see that, as I don't expect 1Password is likely to see or acknowledge or fix this issue anytime soon, even though I'm a paying Business level user, and I couldn't find anywhere else to report this issue.  I'm sure that's somehow my fault.