Hi guys I am encountering a bug on a few peoples device and can replicate this on the meta.discourse site. When i go to login the Samsung Pass “no available sign in pops up” and when i click outside the box to get rid of it i can no longer get the keyboard up when we click in the boxes to sign in.
AI-generated summary
Users are reporting a bug on Samsung Android devices (Galaxy S22 Ultra, S20 Ultra) using Chrome where the Samsung Pass prompt appears during Discourse login, and dismissing it by tapping outside the box prevents the keyboard from appearing — making login impossible. Damian_Boon first reported the issue, sharing screenshots and a video showing the behavior. pmusaraj requested details and tested on Browserstack, but couldn’t replicate it. southpaw tested on an S21+ and found no issue, but noted Samsung Pass wasn’t triggering as expected. After further testing, Damian_Boon confirmed Firefox works fine and that the issue also occurs on other Discourse sites like talk.macpowerusers.com, pointing to Chrome as the culprit. A key discovery: tapping the “Cancel” button on the Samsung Pass prompt resolves the issue — clicking outside does not. Damian_Boon concluded this is likely a Samsung software bug, since dismissing dialogs by tapping outside works everywhere else. pmusaraj agreed and suggested filing a bug with Samsung, noting the complexity of tracing the issue across Chrome, Android, and Samsung Pass. Don speculated Chrome’s default browser status might affect WebAuthn, but Damian_Boon confirmed Chrome is default and couldn’t disable Samsung Pass. The issue appears isolated to Chrome + Samsung Pass interaction on Discourse, and while not directly fixable by Discourse, it’s a usability blocker needing upstream resolution.
2 Likes
Do you see the inputs for username and password and can’t tap them? Can you share a screenshot of what happens in the next step?
Also please share the browser and device, it’s a Samsung Android phone, but curious if this is Samsung Internet or a different browser.
We just get this screen and can click in the box to enter username pass etc and the type cursor flashes but the keyboard doesn’t show.
Using a Samsung galaxy s22 Ultra and S20 Ultra with the Chrome Browser
1 Like
I don’t have any Samsung devices here. Tested on a Browserstack emulator, and that worked fine, but I suspect the Samsung Pass stuff is disabled there.
Can you do me a favour and see if you get the same behaviour on a non-Discourse website, like github.com/login for example? They have passkey support enabled there as well, you may see the same behaviour.
Works fine, the popup doesn’t even show
1 Like
Hi @Damian_Boon,
I have a Samsung S21+ and I’ve set up Samsung Pass (which I then migrated to Samsung Wallet and set as the default passkey app.)
I’m using the latest version of Chrome (133.0.6943.49), and Android 14, One UI version 6.1, and the latest version of the Samsung keyboard.
I’m not able to replicate the issue. When I try to log into Meta, I’m able to type my username and password, and I do not see the Samsung Pass prompt.
I feel like I still don’t have something configured exactly as you have, because when I tap the Log in with a passkey option, I’m shown the Google password manager, even though I have Samsung Pass set as my preferred service for passwords, passkeys, and autofill. Please let me know if there’s anything you can think of that I’ve overlooked in trying to replicate this issue.
@pmusaraj, if it’s any help, when I tap the Log in with a passkey, I see a similar message about not having a sign-in configured, followed by a Discourse error message that states, “The security key authentication process either timed out or was cancelled.” It seems like the affected users aren’t seeing (and able to dismiss) that error. Maybe there’s a clue there as to why these Samsung users aren’t being able to access the keyboard?
then
1 Like
I haven’t set the Samsung Pass up as i have never used it. We don’t click anything , when we literally click login that auto pops up. Just had another person test it too so thats 4 out of 4 that can’t login, not sure why no one else has reported this though as you must have a fair few with these devices.
1 Like
Okay, I undid all of that, but am still not able to repro your issue. it seems there are a lot of possible settings and configurations involved.
Please open the Settings app on the phone, and tap General Management then Passswords, Passkeys and autofill. Once you’re there, tap Preferred service. Is none selected? If not, could you select it and see if that makes a difference?
What keyboard app are you using?
2 Likes
Done that and now it doesnt auto pop up. It now only pops up when i click on to enter email and the same thing happens
I sent the wrong screenshot but i have set that to none as advised. Also the keyboard is just the standard one that comes installed. I havnt changed anything
1 Like
Damian, sorry to ask for more work on your end here… but can you:
- try a different browser in the device (Firefox, for example)
- try to log in on https://talk.macpowerusers.com (it’s another Discourse community, but on an older commit)
- try switching the keyboard you are using on the device
Thanks!
Firefox works as expected so seems to be a chrome issue.
Also macpower doesnt work in chrome
Bit of an update we didn’t realise there was a cancel button at the bottom of the screen, we were just clicking outside the box to get rid of the samsung pass box. When we hit cancel it works as intended so this must be an issue out of your control but still an issue that needs to be resolved?
1 Like
One more thing that came to mind, is Chrome your default browser? That maybe can cause issues with WebAuthn if the default is the Samsung Internet. Not sure, just an idea…
1 Like
Yes Chrome is default browser, I didn’t have another browser on the device until i just installed Firefox. I can’t even find a way to remove the Samsung pass 
1 Like
Yeah, it does look like a Samsung software bug. Dismissing by clicking outside the box should at least let you focus on the next tap, right?
The primary way to resolve this seems to be to file a bug with Samsung or whoever is responsible for this interaction. Finding out who that is exactly is probably 80% of the task, super hard when there are so many layers (Chrome, Android, Samsung Pass).
Exactly this, it works in every single other application 
1 Like