ferdium / ferdium-app

All your services in one place, built by the community
https://ferdium.org
Apache License 2.0
2.65k stars 164 forks source link

Passkey Popup Spam on New Service (Linkedin) #1801

Open mtt59 opened 3 weeks ago

mtt59 commented 3 weeks ago

Avoid duplicates

Ferdium Version

6.7.4

What Operating System are you using?

Windows

Operating System Version

Windows 11 23H2 Build#22631.3672

What arch are you using?

x64

Last Known Working Ferdium version

n/a

Expected Behavior

Login page for the linkedin service, with a manual or single prompt popup for a passkey

Actual Behavior

Constant popups for logging in with a passkey when adding linkedin service. Clicking cancel makes the window go away only for it to come back about a second later. This cycle does not end after 10+ rounds. This popup happens even when the linkedin service is not in focus. See attached screenshots

Steps to reproduce

  1. Go to add services & add a default linkedin service.
  2. Click on the new service to load the login webpage
  3. popup happens

Debug link

https://debug.ferdium.org/140709c1-94bf-47b0-92a5-20070fa5f112

Screenshots

Screenshot 2024-06-04 142431 Screenshot 2024-06-04 143227

Additional information

I have only encountered this problem on linked in, and I don't know if this happens on other services since the passkey prompt is a Windows 11 OS feature.

In other words: I don't know if this is a problem with:

Edit: My workaround is to quickly paste in login info in between passkey prompts like a videogame quicktime event. The passkey prompt popups cease after the first login page; When the one-time email code page opens.

SpecialAro commented 3 weeks ago

Hello @mtt59, thank you for logging this issue!

Does this happen in a regular web browser also?

The recipe url is pointing to: https://www.linkedin.com/messaging

SpecialAro commented 3 weeks ago

Just noticed this can be, in fact, an Electron "bug"

https://www.reddit.com/r/electronjs/comments/1b4ke3g/linkedin_authentication_issues_passkey_popup/

If someone cares to pick this up, the OP updated the post with a workaround. Otherwise, once I have time I can try to make a fix