[Hold #49844] [$250] HybridApp - Can't validate the account of a new sign-up on a controlled private domain

[IuliiaHerets]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: v9.0.89-5
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: No, reproducible on hybrid only
If this was caught during regression testing, add the test name, ID and link from TestRail: C2593731
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Samsung A15 Android 14 & iPhone SE 3rd generation (2022) iOS 18.2.1 | Hybrid app.
App Component: Other

Action Performed:

Prerequisite:

• Sign-up with an account on a domain controlled domain (e.g expensifail.com

1. Download the latest HybridApp
2. Sign-up for an expensifail account
3. Click the validation link in the email to be deep linked back to the app

Expected results:

The user is signed-in and the account is validated

Actual results:

Deep linked back to the mobile app home page, but the user is not signed-in and the account is not validated.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6723303_1737760238492.Samsung_A15__Android_14__v9.0.89-5.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021890456886781005940
• Upwork Job ID: 1890456886781005940
• Last Price Increase: 2025-02-28

Issue Owner

Current Issue Owner: @ahmedGaber93

[melvin-bot]

Triggered auto assignment to @alexpensify (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.

[alexpensify]

I see #51090 has been closed since October. I'm still digging if this is a dupe.

[melvin-bot]

@alexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[alexpensify]

No update

[alexpensify]

Still on the radar

[melvin-bot]

@alexpensify 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]

@alexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[alexpensify]

I didn't get to test over the weekend and I worked limited hours today

[melvin-bot]

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

[alexpensify]

[war-in]

Hi 👋 together with @trjExpensify we had a debug session when we discovered that the sign-up flow on controlled private domain differs between web and mobile. We think that the web flow was updated (to use magic code), but the Mobile-Expensify part has been omitted for some reason.
The easiest way to fix the issue would be to wait for the sign-in page replacement, which is already in progress. We're changing HybridApp to use the NewDot sign-in page, and the flow works correctly there, so no adjustments are required.

However, it'll take some time because we're waiting for the backend changes and must thoroughly test the PRs.

[trjExpensify]

Yeah, @AndrewGable @Julesssss, it seems like all our woes on mobile stem from not using the same flow with the magic code, which makes me think that's going to be quite the lift to unravel and moving to the NewDot sign-in page means we don't have to do work we'll throw away shortly after. Curious for your takes as well, but that's where my head's at as it stands.

[sosek108]

@war-in @trjExpensify isn't that bug connected to bug posted here?

[melvin-bot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[Julesssss]

Thanks for the tag. I agree with this given that we already have the task listed as high priority.

However, it'll take some time because we're waiting for the backend changes and must thoroughly test the PRs.

I know I have said this many times, but I should be able to focus on the backend tasks next week -- the issues I switched too are almost done 🤞

[trjExpensify]

Cool, cool. Glad we're aligned. What's the best issue for me to put this on hold for? We can retest once done.

[trjExpensify]

@war-in @trjExpensify isn't #57367 connected to bug posted here?

If they signed up with an expensifail.com account, probably yes, as it's domain controlled. CC: @joekaufmanexpensify I think you might have a dupe there bud!

[joekaufmanexpensify]

Ah, yeah mine was with an expensifail account. Thanks for flagging, will close in favor of this one!

[Julesssss]

Cool, cool. Glad we're aligned. What's the best issue for me to put this on hold for? We can retest once done.

I think this one. It has the latest overview of remaining tasks.

[melvin-bot]

@ahmedGaber93 Huh... This is 4 days overdue. Who can take care of this?

[ahmedGaber93]

Not overdue, still on hold.

[alexpensify]

Weekly Update: Waiting on #49844

[ahmedGaber93]

The same #55771 (comment)

[alexpensify]

Weekly Update: Still on hold and waiting for #49844

---

🚨 Heads up! I'll be offline until Monday, April 7, 2025, and won’t be actively monitoring this GitHub during that time.

If this GitHub requires an urgent update, please reapply the bug label or reach out in the #expensify-open-source Slack room for help. Otherwise, I'll pick things up when I'm back online. Thanks!

[melvin-bot]

This issue has not been updated in over 15 days. @alexpensify, @ahmedGaber93 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!

[alexpensify]

Still on hold for (#49844)