Skip to content

[Due for payment 2025-04-16] [$250] iOS - Conversation History - Scroll up to the beginning loads the end of the conversation #54870

Closed

Description

@IuliiaHerets

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Version Number: v9.0.81-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5420831&group_by=cases:section_id&group_order=asc&group_id=306202
Email or phone of affected tester (no customers): applausetester+vq@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: iPhone 12 / iOS 17.7.2
App Component: Other

Action Performed:

  1. Log in with a HIGH traffic account. If unsure what this is, reach out to TTL in Slack (Note: it is possible that having many long long messages in the chat is important to reproduce)
  2. Navigate to a 1:1 chat that has a lot of messages in the conversation history
  3. Scroll to the top of the conversation

Expected Result:

Scrolling should be smooth, and a short loading animation should appear when additional messages are loaded. The user should be able to scroll to the beginning of the conversation without any issues.

Actual Result:

When scrolling up, the app repeatedly loads back to the end of the conversation

Workaround:

Unknown

Platforms:

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6708020_1736246096714.HTlongconversation_-_Trim.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021876720727427448620
  • Upwork Job ID: 1876720727427448620
  • Last Price Increase: 2025-01-21
Issue OwnerCurrent Issue Owner: @alexpensify

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jan 7, 2025
  2. melvin-bot commented on Jan 7, 2025

    @melvin-bot

    Triggered auto assignment to @aldo-expensify (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  3. melvin-bot commented on Jan 7, 2025

    @melvin-bot

    Triggered auto assignment to @alexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

  4. melvin-bot commented on Jan 7, 2025

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  5. github-actions commented on Jan 7, 2025

    @github-actions
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  6. aldo-expensify commented on Jan 7, 2025

    @aldo-expensify
    Contributor

    Tried to reproduce in Android native / web, and haven't been able. I'll try in the IOS emulator.

  7. aldo-expensify commented on Jan 7, 2025

    @aldo-expensify
    Contributor

    I was able to reproduce in IOS:

    Screen.Recording.2025-01-07.at.10.35.09.AM.mov

    I think it may be related to having these long messages in the conversation:

    image
  8. aldo-expensify commented on Jan 7, 2025

    @aldo-expensify
    Contributor

    Reproduced this in IOS checking out the production branch (version v9.0.80-6), so I do think this is reproducible in production.

    @IuliiaHerets can you double check if this is reproducible in production? please 🙏

  9. 83 remaining items

  10. changed the title [-][$250] iOS - Conversation History - Scroll up to the beginning loads the end of the conversation[/-] [+][Due for payment 2025-04-16] [$250] iOS - Conversation History - Scroll up to the beginning loads the end of the conversation[/+] on Apr 9, 2025
  11. melvin-bot commented on Apr 9, 2025

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  12. melvin-bot commented on Apr 9, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.24-10 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2025-04-16. 🎊

    For reference, here are some details about the assignees on this issue:

    • @rinej does not require payment (Contractor)
    • @dukenv0307 requires payment through NewDot Manual Requests
  13. melvin-bot commented on Apr 9, 2025

    @melvin-bot

    @dukenv0307 @alexpensify @dukenv0307 The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  14. melvin-bot commented on Apr 16, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    • Contributor: @rinej is from an agency-contributor and not due payment
    • Reviewer: @dukenv0307 owed $250 via NewDot

    BugZero Checklist (@alexpensify)

    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/1876720727427448620/hired)
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  15. alexpensify commented on Apr 16, 2025

    @alexpensify
    Contributor

    Payment Summary Contributor:

    Contributor: @rinej does not require payment (Contractor)
    Contributor+: @dukenv0307 due $250 via NewDot - please submit a request, thanks!

  16. JmillsExpensify commented on Apr 22, 2025

    @JmillsExpensify
    Contributor

    $250 approved for @dukenv0307

  17. added
    ReviewingHas a PR in review
    and removed on Oct 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.EngineeringExternalAdded to denote the issue can be worked on by a contributorReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions