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
[CRITICAL] Temporary login is seen as unvalidated login when signing in #57869
Version Number: 9.1.9-2 Reproducible in staging?: y Reproducible in production?: y If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: If this was caught during regression testing, add the test name, ID and link from TestRail: Email or phone of affected tester (no customers): Logs:https://stackoverflow.com/c/expensify/questions/4856 Expensify/Expensify Issue URL: Issue reported by:@joekaufmanexpensify Slack conversation (hyperlinked to channel name): expensify-bugs
Action Performed:
Login to an account on Staging.
Switch to Expensify Classic.
Sign out.
Sign into a different account and land in NewDot.
Go to Profile > Contact method.
Expected Result:
You shouldn't see a RBR or a temporary login shown as a unvalidated login.
Actual Result:
You see an expensify.cash temporary login shown as an unvalidated login in your account on the frontend.
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Android: Standalone
Android: HybridApp
Android: mWeb Chrome
iOS: Standalone
iOS: HybridApp
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidenceRecording.1031.mp4
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Identify the pull request that introduced this issue and revert it.
It was my fault. I tried to debug it and check if the back-end was returning the temporary logins, but I could not find where that was happening since the data from OpenApp was okay. Considering the PR was super small and it wasn't reviewed, the checklist wasn't completed, and the PR wasn't approved, what if we issue half of the bounty, $125?
It was my fault. I tried to debug it and check if the back-end was returning the temporary logins, but I could not find where that was happening since the data from OpenApp was okay. Considering the PR was super small and it wasn't reviewed, the checklist wasn't completed, and the PR wasn't approved, what if we issue half of the bounty, $125?
In this case, the contributor would be eligible for full payment, and half payment for the C+ since a complete review wasn't done.
changed the title [-][$250] Temporary login is seen as unvalidated login when signing in[/-][+][CRITICAL] emporary login is seen as unvalidated login when signing in[/+]on Mar 13, 2025
changed the title [-][CRITICAL] emporary login is seen as unvalidated login when signing in[/-][+][CRITICAL] Temporary login is seen as unvalidated login when signing in[/+]on Mar 13, 2025
Activity
melvin-bot commentedon Mar 5, 2025
Triggered auto assignment to @twisterdotcom (
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 commentedon Mar 5, 2025
Triggered auto assignment to @pecanoro (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Mar 5, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Mar 5, 2025
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
pecanoro commentedon Mar 5, 2025
Happening on prod as well so not a deploy blocker
41 remaining items
akinwale commentedon Mar 13, 2025
@blimpich I believe compensation is still due here according to the process doc since a PR was already created and reviewed.
cc @twisterdotcom
blimpich commentedon Mar 13, 2025
Apologies, wasn't aware of that part of the process. @twisterdotcom can you confirm that?
pecanoro commentedon Mar 13, 2025
It was my fault. I tried to debug it and check if the back-end was returning the temporary logins, but I could not find where that was happening since the data from OpenApp was okay. Considering the PR was super small and it wasn't reviewed, the checklist wasn't completed, and the PR wasn't approved, what if we issue half of the bounty, $125?
akinwale commentedon Mar 13, 2025
In this case, the contributor would be eligible for full payment, and half payment for the C+ since a complete review wasn't done.
[-][$250] Temporary login is seen as unvalidated login when signing in[/-][+][CRITICAL] emporary login is seen as unvalidated login when signing in[/+][-][CRITICAL] emporary login is seen as unvalidated login when signing in[/-][+][CRITICAL] Temporary login is seen as unvalidated login when signing in[/+]twisterdotcom commentedon Mar 14, 2025
Alright yes, this is pretty clear:
$250 was the job we created, so this would be $250 for @nkdengineer and $125 for @akinwale.
twisterdotcom commentedon Mar 14, 2025
Payment Summary:
JmillsExpensify commentedon Mar 17, 2025
$125 approved for @akinwale