-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Hold #49844] [$250] HybridApp - Can't validate the account of a new sign-up on a controlled private domain #55771
Comments
Triggered auto assignment to @alexpensify ( |
I see #51090 has been closed since October. I'm still digging if this is a dupe. |
@alexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
No update |
Still on the radar |
@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! |
@alexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
I didn't get to test over the weekend and I worked limited hours today |
@alexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@alexpensify @ahmedGaber93 this issue is now 4 weeks old, please consider:
Thanks! |
|
Oh, it looks like no validation links work in the app 🥶 I'm going to debug it further |
Did this account have a secondary account? 👀 This is why we call the wallet merge flow in Authenticate: https://github.com/Expensify/Auth/blob/1ee7f511efdc0c72610da05ea4e5c02951a59dc7/auth/command/Authenticate.cpp#L112-L120 Assuming not, considering it was a brand new account...so I think there might be some logic improvements needed to the code block above |
I also found an interesting case, when creating a new account and clicking I think it's not related to your issue but still worth fixing |
Exactly, brand new account, so nope.. no secondary account attached. |
Interesting. So in the case of a non-domain controlled sign-up, the user is signed-in, but the account isn't validated. In the domain controlled sign-up case, the user isn't signed-in and the account isn't validated? |
Yes, but in that case sign-in is performed automatically when clicking I guess that the flow for |
Got it, what are the next steps here? Would it help you test if you use |
@trjExpensify that would definitely help! Let's move to slack with sending the URLs, I'll post an update here if I find something |
Sounds good! |
@ahmedGaber93 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Not overdue, still discussing. |
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. However, it'll take some time because we're waiting for the backend changes and must thoroughly test the PRs. |
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. |
@war-in @trjExpensify isn't that bug connected to bug posted here? |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Thanks for the tag. I agree with this given that we already have the task listed as high priority.
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 🤞 |
Cool, cool. Glad we're aligned. What's the best issue for me to put this on hold for? We can retest once done. |
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! |
Ah, yeah mine was with an expensifail account. Thanks for flagging, will close in favor of this one! |
I think this one. It has the latest overview of remaining tasks. |
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:
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:
Screenshots/Videos
Bug6723303_1737760238492.Samsung_A15__Android_14__v9.0.89-5.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @ahmedGaber93The text was updated successfully, but these errors were encountered: