You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Unable to login with non-existing account that owes money #45252
User A with gmail account go to FAB> Submit expense> Add User B email address> Complete the submit flow
Wait for a minute
Repeat step 1 to submit a second IOU to user B
As User B go to staging.new.expensify.com> Type email address and click Continue
Expected Result:
User B should be able to login
Actual Result:
Unable to login with non-existing account that owes money. "Cannot get account details, please try again or contact concierge@expensify.com"
error message is displayed on login page
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
I can reproduce this, but only specifically when submitting two IOUs to someone hasn't created an account yet. If I only submit one, I have no problem logging into the new account.
changed the title [-]Login - Unable to login with non-existing account that owes money[/-][+][$250] Login - Unable to login with non-existing account that owes money[/+]on Jul 11, 2024
Problem Statement: The problem we are trying to solve is that when a user attempts to log in with a non-existing account that owes money, the system does not handle the situation correctly, leading to a poor user experience.
Root Cause: The root cause of this problem is that the current login system does not have a mechanism to detect and handle cases where a user attempts to log in with a non-existing account that owes money. This lack of error handling and recovery flow leads to a poor user experience and potential frustration.
Proposed Solution: To solve this problem, I propose the following changes:
Implement robust error handling to detect when a user attempts to log in with a non-existing account that owes money.
Display clear and concise error messaging to the user, indicating that the account does not exist or that there is an outstanding balance.
Redirect the user to a recovery flow, where they can recover their account or resolve the outstanding balance.
Alternative Solutions Explored:
Soft Delete: Instead of completely removing the account, we could implement a soft delete mechanism that marks the account as inactive but still retains the account information. This would allow users to recover their account and resolve the outstanding balance.
Account Lookup: We could implement an account lookup feature that allows users to search for their account and recover it if it exists. This would provide an additional recovery path for users who have forgotten their login credentials.
Grace Period: We could introduce a grace period for accounts with outstanding balances, allowing users to log in and resolve the balance within a certain timeframe before the account is marked as non-existent.
These alternative solutions were explored, but the proposed solution was deemed the most effective and efficient way to solve the problem.
changed the title [-][$250] Login - Unable to login with non-existing account that owes money[/-][+]Unable to login with non-existing account that owes money[/+]on Jul 22, 2024
Activity
melvin-bot commentedon Jul 11, 2024
Triggered auto assignment to @joekaufmanexpensify (
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.joekaufmanexpensify commentedon Jul 11, 2024
I can reproduce this, but only specifically when submitting two IOUs to someone hasn't created an account yet. If I only submit one, I have no problem logging into the new account.
joekaufmanexpensify commentedon Jul 11, 2024
That said, this is a pretty bad bug for a core flow, so makes sense to me to fix now.
[-]Login - Unable to login with non-existing account that owes money[/-][+][$250] Login - Unable to login with non-existing account that owes money[/+]melvin-bot commentedon Jul 11, 2024
Job added to Upwork: https://www.upwork.com/jobs/~017518e8ff7a1d7f72
melvin-bot commentedon Jul 11, 2024
Triggered auto assignment to Contributor-plus team member for initial proposal review - @mkhutornyi (
External)mkhutornyi commentedon Jul 11, 2024
@kabeer95 Please read through contributing guideline and follow proposal template. Thanks
kabeer95 commentedon Jul 11, 2024
Problem Statement: The problem we are trying to solve is that when a user attempts to log in with a non-existing account that owes money, the system does not handle the situation correctly, leading to a poor user experience.
Root Cause: The root cause of this problem is that the current login system does not have a mechanism to detect and handle cases where a user attempts to log in with a non-existing account that owes money. This lack of error handling and recovery flow leads to a poor user experience and potential frustration.
Proposed Solution: To solve this problem, I propose the following changes:
Implement robust error handling to detect when a user attempts to log in with a non-existing account that owes money.
Display clear and concise error messaging to the user, indicating that the account does not exist or that there is an outstanding balance.
Redirect the user to a recovery flow, where they can recover their account or resolve the outstanding balance.
Alternative Solutions Explored:
Soft Delete: Instead of completely removing the account, we could implement a soft delete mechanism that marks the account as inactive but still retains the account information. This would allow users to recover their account and resolve the outstanding balance.
Account Lookup: We could implement an account lookup feature that allows users to search for their account and recover it if it exists. This would provide an additional recovery path for users who have forgotten their login credentials.
Grace Period: We could introduce a grace period for accounts with outstanding balances, allowing users to log in and resolve the balance within a certain timeframe before the account is marked as non-existent.
These alternative solutions were explored, but the proposed solution was deemed the most effective and efficient way to solve the problem.
joekaufmanexpensify commentedon Jul 12, 2024
Still pending proposals
22 remaining items
iwiznia commentedon Jul 22, 2024
PR here https://github.com/Expensify/Web-Expensify/pull/42831
iwiznia commentedon Jul 22, 2024
BTW I think it's totally fine to send clientUpdateID in all requests, even if we only need it for writes.
Julesssss commentedon Jul 22, 2024
PR merged, thanks
[-][$250] Login - Unable to login with non-existing account that owes money[/-][+]Unable to login with non-existing account that owes money[/+]joekaufmanexpensify commentedon Jul 22, 2024
Sweet, thank you both!
melvin-bot commentedon Jul 29, 2024
@iwiznia, @Julesssss Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
Julesssss commentedon Jul 30, 2024
Fix is on prod