-
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
[$500] Room - Unable to scroll up to the top in public room as anonymous user #34980
Comments
Triggered auto assignment to @joekaufmanexpensify ( |
Job added to Upwork: https://www.upwork.com/jobs/~015a97f638ac603602 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @mananjadhav ( |
We think that this bug might be related to #vip-vsb |
I can't reproduce this on web. Going to try on mobile |
Okay, I can reproduce on mobile web: 2024-01-23_18-18-22.mp4 |
Agreed this feels like a #vip-vsb issue. |
Got it. @mananjadhav ,do you agree? |
Yeah looks like @s-alves10 is correct. |
Current assignee @mananjadhav is eligible for the Internal assigner, not assigning anyone new. |
Got it. TY! Made it internal |
Still needs an internal volunteer |
Same |
@mananjadhav @joekaufmanexpensify 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! |
Posted in #vip-vsb cuz it's likely a priority with #exfy-roadmap Bumped to |
Sounds good! |
Still looking for internal volunteer |
Not overdue |
Waiting for engineer to grab |
Issue not reproducible during KI retests. (First week) |
Got it. I will retest! |
Will retest this afternoon |
Yep, this is no longer reproducible for me. Closing as this seems to be fixed! |
QA team is able to reproduce the issue in build 1.4.47.0, bandicam.2024-03-06.00-40-28-206.mp4 |
Got it. I will try and reproduce! |
I think this new report is a bit different than the original one. The original report here didn't really involve the skeleton UI. he new report seems like a dupe of #37661 . Closing as we're working on fixing the loading/scrolling of public rooms without showing the skeleton UI there! |
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.30-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: https://expensify.testrail.io/index.php?/tests/view/4228454
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal team
Slack conversation:
Action Performed:
Precondition: user created a public room and added multiple messages
Expected Result:
User can scroll to the beginning of the chat history
Actual Result:
Flickering loading animation displayed, anonymous user is unable to scroll up to the beginning
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6352302_1706032162727.video_2024-01-23_12-42-30.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: