Closed lanitochka17 closed 1 year ago
Triggered auto assignment to @dylanexpensify (Bug
), see https://stackoverflow.com/c/expensify/questions/14418 for more details.
Platforms
in OP are ✅):wave: 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:
Triggered auto assignment to @marcaaron (Engineering
), see https://stackoverflow.com/c/expensify/questions/4319 for more details.
@marcaaron I believe you're on today, is that right?
Yes looking 👀
Yikes this flow seems super broken...
Crashing here:
Last touched here:
https://github.com/Expensify/App/pull/19515
possibly related to this one: https://github.com/Expensify/App/pull/20371/files
Still looking...
Fix incoming. I think we will maybe want to look into fixing this in Web-E based on the conversation here: https://expensify.slack.com/archives/C07J32337/p1687199748385919?thread_ts=1687190209.326479&cid=C07J32337 cc @Beamanator
After the crash is fixed there is an issue related to duplicate accounts showing up. Caused by report options and personal details options not having login
fields at all here:
I am going to presume it's because we removed them in Auth/Web-Expensify without first migrating the App code, but will continue to help investigate tomorrow if required!
@Beamanator @puneetlath I think whatever we did in Auth/Web is really a "web deploy blocker" in that once it goes to production it will break the current App because the code expects login
to exist on all these options. I tested this issue on staging app + production web and it doesn't exist there.
Probably a safer rollout would be to update the App code to work for all cases then introduce changes in Auth and Web-Expensify.
I'm also seeing the crashes in dev, and my own account multiple times in the result list when searching for a chat.
This is still a bug, but I'm removing the blocker label as per this comment.
@lanitochka17 can we get a retest on this one? I think it's been fixed maybe?
This seems to have been fixed, I can't reproduce it on staging.
@marcaaron Hello, still reproducible, in search dialog a lot of old chats, but in Split bill - no. Checked with yuriy.turbo+ch7@gmail.com “problematic” account
https://github.com/Expensify/App/assets/78819774/a6cc22f9-097e-43ed-8705-b7db06acb1a8
Can you sign out and sign back in to see if the issue persists? I am suspecting this is due to some bad data stored.
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:
The user should be able to select Split bill users without any issues
Actual Result:
As soon as a few users are selected - all the others disappear, the search also does not work. Only for specific Gmail accounts
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.29.0
Reproducible in staging?: Yes
Reproducible in production?: No
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
https://github.com/Expensify/App/assets/78819774/65618b61-cb06-4b5e-8a76-332c1de07e56
https://github.com/Expensify/App/assets/78819774/dcc2f393-c10d-49c5-b738-5f57cdd22d27
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub