-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Chat - Unexpected error when completing payment request. #14571
Comments
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Could be the same root of cause #14548 |
That does seem to be related. It should be fixed now though. Can you please retest? |
@luacmartins Recording.584.mp4 |
Reproducing locally with logs to see if this is a back end issue. |
@luacmartins @Luke9389 I dont see anything in console, but in case you need logs, this is account used on my side applausetester++1014mvt@applause.expensifail.com |
Thanks for that info @mvtglobally. @luacmartins these are the logs I'm getting
Looks like we're failing to send a clientID with that request. |
@Luke9389 Should we log a different issue for this or you want to track here ? |
Let's track this one here until they're able to get some logs on the other issue. I'm not convinced they're the same root cause yet. |
@Luke9389 I think this should have been fixed by https://github.com/Expensify/Auth/pull/7440, – |
@roryabraham I am seeing it right now on this account across all requests. It seem to be specific to account. Since it's the same build, anything else I need to do to verify it? |
@roryabraham that sure does seem related. @mvtglobally are you testing with a new payment request each time? |
@Luke9389 Yes, Tried a brand new request from an account I didn't have requests from before just now. Tried to pay with applausetester++1014mvt@applause.expensifail.com and get the same blank screen |
I'm unable to reproduce this issue on any platform desktop.mov |
Interesting @luacmartins, I don't see an option for you that says "I'll settle up elsewhere". Not sure why that's the case. I'm also seeing quite a few of these errors in the logs from the past hour or so. @roryabraham is it possible that PR didn't fix this after all? Or maybe we need a front end change as well? |
@Luke9389 you can see that at around 0:19. I couldn't find anything out of the ordinary in the logs for applausetester++1014mvt@applause.expensifail.com The logs Luke shared above do look suspicious |
Actually @Luke9389 those logs are from earlier today, all before 2023-01-25 19:58 UTC. Auth deploy was done at around 2023-01-25 21:06 UTC and I can't find any more instances of that error in the logs after that time |
Oh gotcha. Interesting. I just saw your ping in the thread so we'll discuss further there. |
Thanks @thienlnam. It is true that the unexpected error bug that we saw in the original description has been resolved. Later in the thread we began discussing a blank screen, which may or may not be related. We feel it's best to separate these two issues. |
sure. I will ask team if they can repro and log with the steps |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
No error message should be displayed after complete payment.
Actual Result:
Unexpected error message occurs after payment is completed.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.2.59.1
Reproducible in staging?: Yes
Reproducible in production?: Yes
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
Notes/Photos/Videos: Any additional supporting documentation
Bug5911777_payment_error.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: