Apple Passwords: Yab never asks for logins on Carta (two-step sign-in), so nothing shows even though it's paired and Passwords has an exact-match entry
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- swift
- Domain
- authentication, desktop
Research direction
Start by tracing how sign-in fields are recognized and how that result reaches ManagerVaults; the report points to the email-first, password-second flow on Carta and mentions #778 as a possible related case. Check whether the missing request reproduces before ApplePasswords.logins(for:) is called. Done means the paired Apple Passwords suggestion appears for the reported flow, with the helper request visible in debug logs.
Written by the indexing model from the issue text.
Description
Yab version
0.47.19 (202611150627)
Device
Mac, Apple silicon (M5)
macOS or iOS version
macOS 27.2.1
Engine of the tab
Chromium
Area
Passwords and autofill
Steps to reproduce
- Connect Apple Passwords in Settings → Passwords and enter the code. Log shows
helper started→code shown by Passwords→paired, with no errors. - Confirm the Passwords app has a login for the exact host: website
login.app.carta.com, username + password + a verification code. - In a Chromium tab, open https://app.carta.com and get redirected to the sign-in page on
login.app.carta.com. - Click the email field.
What you expected
Yab asks the helper for logins on login.app.carta.com and shows the Apple Passwords suggestion under the field.
What happened instead
No suggestion, no card, nothing. Yab never asks the helper at all.
While streaming subsystem == "dev.serafim.fast" at debug level during the attempt, there are zero ApplePasswords lines. ApplePasswords.logins(for:) always logs list helper auth required … at notice level, so the list request was never made. The helper (pid stays the same, paired session intact) shows only its own LaunchServices housekeeping.
So the failure is before the helper: the sign-in field on Carta isn't recognized as a login, so ManagerVaults is never consulted. Carta's sign-in asks for the email first and the password on a second step, so this may be the same root cause as #778.
Possibly related: with the iCloud Passwords extension disabled by ApplePasswordExtensionRoute.disabled, there's no fallback path here. The person sees nothing at all, and nothing tells them why.
How often
Every time on Carta. It also happens on many other sites, but these are the logs I checked.
Your setup (optional)
Passwords live in Apple Passwords (iCloud Keychain), not Yab's vault. 1Password extension installed but turned off for this test.
Two related things that make "shows nothing" common day to day:
- Pairing lives only in the running helper, so every relaunch or update (near daily) unpairs. The code is only offered when a login field is detected, so on a site like Carta it's never offered.
ApplePasswordsPairingis one card at a time (busy), anchored to whatever window was key. If it opens in another Space and isn't answered, every other sign-in box gets nothing until it is.
Could Yab offer the pairing once at launch (or from the toolbar) when Apple Passwords is connected but unpaired, instead of waiting for a detected login field?
Did it work before? (optional)
The iCloud Passwords extension filled Carta when Yab still let it run. It hasn't since Yab started routing it to the built-in connection.
- Dominant language
- Swift
- Stars
- 648
- Forks
- 56
- Avg merge
- 21h 14m
- Merged PRs (30d)
- 22
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from yetanotherbrowser/yab
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
yetanotherbrowser/yab#1008 ·
Maintainers usually reply within 2 days
-
area: passwords Broken bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
yetanotherbrowser/yab#923 ·
Maintainers usually reply within 2 days
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
yetanotherbrowser/yab#918 · 1 reaction ·
Maintainers usually reply within 2 days
-
iPhone: the + button and the checkmark sit on top of the Space switcher in the bottom barPossibly taken @ChaseRoofener claimed this 3 days ago. OpenAnnoying area: iphone bug needs info
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
yetanotherbrowser/yab#915 · 3 comments ·
Maintainers usually reply within 2 days
-
CONTRIBUTING.md and CI run scripts/runs/tests_for.py, which is not in the repositoryPossibly taken @serafimcloud claimed this 3 days ago. OpenAnnoying in progress
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
yetanotherbrowser/yab#875 · 1 comment ·
Maintainers usually reply within 2 days
All issues in yetanotherbrowser/yab
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
swiftlang/swift-org-website#1608 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
haacked/switchboard#460 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
manaflow-ai/cmux#47572 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
borrowcheckmate/swimlie#48 ·
Maintainers usually reply within 1 day