-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[$250] IOS - Chat - Show error when access start chat 2nd time in off-mode #42916
Comments
Triggered auto assignment to @kadiealexander ( |
@kadiealexander FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors |
@kadiealexander Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Job added to Upwork: https://www.upwork.com/jobs/~0136e2911a526a72fe |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @abdulrahuman5196 ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Show error when access starts to chat 2nd time in offline mode What is the root cause of that problem?
What changes do you think we should make in order to solve the problem?
Or clearing whenever we call What alternative solutions did you explore? (Optional)For the second issue, we can remove this block and the related error clearing logic entirely. They were meant to support the use case that there's a duplicate room name error thrown from the back-end, but we have the front-end validation logic for that in
And we already have the App/src/libs/actions/Report.ts Line 2102 in 1d5f83d
|
Proposal updated to add the fix for another observed issue |
@dominictb Hi, do you know why |
Same crash root cause as #42824 |
Proposal updated to emphasize that 1 part of the issue will be fixed in #42824 |
@abdulrahuman5196, @kadiealexander Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@abdulrahuman5196 bump! |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ishpaul777 ( |
Hey @ishpaul777 could you please review the proposals here? Thank you! |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Reviewing! 👀 |
hmm it appears that this issue partially be fixed by #42824 @kadiealexander Can we please put a HOLD and then retest if there's any other issue left for us to fix. |
@kadiealexander @ishpaul777 this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
Holding PR for this is deployed. do we still have any issues left to fix @dominictb ? if yes, please share videos/steps Thanks! |
Requested a retest here |
Issue is no longer reproduce! RPReplay_Final1718720116.MP4 |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
just want to make sure, @dominictb would you like to report any related issue left to fix here ? if no, i think we are good to close this @kadiealexander |
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.78-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause - Internal Team
Issue found when executing PR #42679
Action Performed:
Expected Result:
Can start a new chat
Actual Result:
Show error when access starts to chat 2nd time in off-mode
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6496979_1717125695227.RPReplay_Final1717123192__1_.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: