Web - Secondary login added in OldDot is can't be seen in NewDot

[IuliiaHerets]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: v9.0.38-3 Reproducible in staging?: Y Reproducible in production?: Y Issue reported by: Applause Internal Team

Action Performed:

1. Sign in to staging.new.expensify.com on Primary device
2. Sign in to staging.expensify.com with a secondary device with same account as step 1
3. Add and validate a secondary login with staging.expensify.com
4. On the primary device navigate to Profile > Contact Method

Expected Result:

Secondary login set in OldDot should be visible on NewDot

Actual Result:

Secondary login set in OldDot is not visible on NewDot

Workaround:

Unknown

Platforms:

• [ ] Android: Native
• [ ] Android: mWeb Chrome
• [ ] iOS: Native
• [ ] iOS: mWeb Safari
• [x] MacOS: Chrome / Safari
• [ ] MacOS: Desktop

Screenshots/Videos

https://github.com/user-attachments/assets/a07b3802-65d3-4008-a5df-e2970d45fb7e

View all open jobs on GitHub

[melvin-bot[bot]]

Triggered auto assignment to @puneetlath (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[IuliiaHerets]

@puneetlath FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

[puneetlath]

This is a backwards compatibility thing. We don't send a pusher update when this is added from OldDot. We probably should, but it's not very high priority. I'm going to put it in #wave-control.

[melvin-bot[bot]]

this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

[melvin-bot[bot]]

This issue has not been updated in over 15 days. eroding to Monthly issue.

P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

[melvin-bot[bot]]

Triggered auto assignment to @bfitzexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot[bot]]

@bfitzexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

[bfitzexpensify]

I think weekly remains the right priority for this - labelled and ready to be picked up as a hot pick