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
Login - Unable to log in manually with locked gmail but able to log in with Google #25713
👋 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.
Yeah, this is a backend issue from our side. I don't know exactly how we're triggering the suspended email message, but I think we'd need to hook up that logic to the SignInWithGoogle API command. So this can only be fixed internally.
Since this is introduced with the new Google sign-in functionality, I don't think this should be a blocker.
After some investigation, I found out this error is only shown when our email providers can't send the validation code for some reason (has the nvp expensify_emailDeliveryFailure). Since the user is trying to sign in via Google, we don't send a validation code. Also, we don't show this error in OldDot when the user has the nvp expensify_emailDeliveryFailure and sign in via SSO, so I'm going to close it out.
Activity
OSBotify commentedon Aug 22, 2023
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
StagingDeployCashdeploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:melvin-bot commentedon Aug 22, 2023
Triggered auto assignment to @grgia (
Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.lindboe commentedon Aug 22, 2023
@marcochavezf, this looks like maybe a server-side issue with Google Sign-In?
marcochavezf commentedon Aug 23, 2023
Yeah, this is a backend issue from our side. I don't know exactly how we're triggering the suspended email message, but I think we'd need to hook up that logic to the
SignInWithGoogleAPI command. So this can only be fixed internally.Since this is introduced with the new Google sign-in functionality, I don't think this should be a blocker.
grgia commentedon Aug 23, 2023
@marcochavezf could you take over this issue in that case?
roryabraham commentedon Aug 23, 2023
Since this is a back-end issue, we're not going to block NewDot deploy on this. But we'll keep it as a daily
61 remaining items
marcochavezf commentedon Jan 29, 2024
No update, focused on wave work
marcochavezf commentedon Feb 7, 2024
No update, posted in wave9 to ask if it should part of it https://expensify.slack.com/archives/C05NJ4SLBMF/p1707159629690479
marcochavezf commentedon Feb 16, 2024
No update, focused on critical wave issues and older tasks
marcochavezf commentedon Feb 27, 2024
No update, focused on critical and high wave tasks
marcochavezf commentedon Mar 6, 2024
After some investigation, I found out this error is only shown when our email providers can't send the validation code for some reason (has the nvp
expensify_emailDeliveryFailure). Since the user is trying to sign in via Google, we don't send a validation code. Also, we don't show this error in OldDot when the user has the nvpexpensify_emailDeliveryFailureand sign in via SSO, so I'm going to close it out.