App
App copied to clipboard
Expensify
Adding a comment in domain char #expensifail.com crashes
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: 1.4.35-0 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 Expensify/Expensify Issue URL: Issue reported by: @aldo-expensify Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1706747593037209
Action Performed:
- Sign into https://staging.new.expensify.com/r/75431276 on a browser with an expensifail account
- Click the search bar in the upper left corner and search for "#expensifail.com" room
- Try to add a comment
- Verify you get an error (
Auth GetRestrictedAuthTokenByEmail returned an error)
Expected Result:
The comment should be added
Actual Result:
Error appears: Unexpected error while posting the comment, please try again laterAuth GetRestrictedAuthTokenByEmail returned an error
Logs: https://www.expensify.com/_devportal/tools/logSearch/#query=request_id:(%2284e610de98092d8a-YVR%22)+AND+timestamp:[2024-01-31T23:26:57.858Z+TO+2024-02-01T01:26:57.858Z]&index=logs_expensify-026557
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
- [X] Android: Native
- [X] Android: mWeb Chrome
- [X] iOS: Native
- [X] iOS: mWeb Safari
- [x] MacOS: Chrome / Safari
- [X] MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidence
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~018aa801eb047294a0
- Upwork Job ID: 1753560316765069312
- Last Price Increase: 2024-02-02
Triggered auto assignment to @Christinadobrzyn (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.
![melvin-bot[bot] avatar](https://avatars.githubusercontent.com/in/179547?v=4 "Published by a pub.dev verified publisher"){kind=small}
I can reproduce this - updated the OP with the details.
I think this needs to be internal? adding that label for a buddy check.
Job added to Upwork: https://www.upwork.com/jobs/~018aa801eb047294a0
Triggered auto assignment to Contributor Plus for review of internal employee PR - @getusha (Internal)
I think this can be part of vip-vsb since it relates to chat - I think this need to be internal based on the error
Asking in the vsb Slack channel how we want to handle this one - https://expensify.slack.com/archives/C066HJM2CAZ/p1707247660309079
Since this is internal - we're waiting for someone to pick this up
@Christinadobrzyn, @getusha Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
Auto-assigning issues to engineers is no longer supported. If you think this issue should receive engineering attention, please raise it in #whatsnext.
Going to add a few more labels to this job to try and get someone internally to pick it up. I think this is an internal job and I believe it is ready for someone to grab!
@Christinadobrzyn @getusha 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!
Keeping this internal for eng to pick up when they have the bandwidth!
@Christinadobrzyn, @getusha Whoops! This issue is 2 days overdue. Let's get this updated quick!
same status - https://github.com/Expensify/App/issues/35538#issuecomment-1946756660
same status - https://github.com/Expensify/App/issues/35538#issuecomment-1946756660
@Christinadobrzyn @getusha this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks!
Internal label so we're waiting for someone to pick this up. However gonna test again today to see if it's still happening.
This issue still exists, it's such a singular issue though... and it seems like the "Auth GetRestrictedAuthTokenByEmail returned an error" error is happening in Concierge and OldDot.
Logs: https://www.expensify.com/_devportal/tools/logSearch/#sort=asc&size=10000&query=blob%3A%22Auth%20GetRestrictedAuthTokenByEmail%20returned%20an%20error%22%20AND%20email%3A%22c.dobrzyn%2B87%40expensifail.com%22%20AND%20timestamp%3A%5B2024-02-16T00%3A00%20TO%202024-02-24T23%3A59%5D
We'll keep this open to see if someone would be able to grab it next week.
oh exciting! testing again... hum... still getting the error when trying to send a message to the #expensifail.com room.
asking QA to retest - https://expensify.slack.com/archives/C9YU7BX5M/p1709250511129789
@Christinadobrzyn @getusha this issue is now 4 weeks old and preventing us from maintaining WAQ. This should now be your highest priority. Please post below what your plan is to get a PR in review ASAP. Thanks!
There doesn't seem to be a way to add QA to our expensifail.com room in NewDot to test this. Asking @mallenexpensify if he can test for us to see if this is still happening - https://expensify.slack.com/archives/C01SKUP7QR0/p1709329998662989?thread_ts=1709307595.245699&cid=C01SKUP7QR0
I think this is still happening and I think it needs to be internal since it's affecting the expensifail.com accounts.
Was able to reproduce.
Logs - logs-2024-03-01 23_38_25.029.txt
I logged out/in, and cleared cookies + local storage and the issue persists. Even though it shows an error when sending, when I signed back in, I saw messages that went through.
Oh interesting- since it's only affecting this one room, I'm not sure if this needs to be fixed @getusha what's your take?
I think this should still be evaluated by an internal engineer so going to keep this open for pick up