[HOLD for payment 2024-10-24] [$250] iOS - IOU - The details of a single IOU are not displayed until you scroll up

[IuliiaHerets]

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: 9.0.21-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/4864475
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team

Action Performed:

1. Open New Expensify app
2. Log in with a new HT account
3. Send any IOU to a user with whom you have not had a previous expense.
4. Open the sent IOU
5. Scroll up the details
6. Close the application (kill)
7. Open the app
8. Repeat steps 3-5 several times

Expected Result:

IOU details should be automatically displayed when the IOU is opened

Actual Result:

The details of a single IOU are not displayed until you scroll up

Workaround:

Unknown

Platforms:

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6573976_1723830500223.RPReplay_Final1723810132.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~010724ba54874de1b6
• Upwork Job ID: 1826197658645316035
• Last Price Increase: 2024-09-04

Issue Owner

Current Issue Owner: @zanyrenney

[melvin-bot]

Triggered auto assignment to @zanyrenney (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.

[IuliiaHerets]

We think that this bug might be related to #vip-bills

[IuliiaHerets]

@zanyrenney z 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

[zanyrenney]

hey @IuliiaHerets can you explain what a HT account is please?

[IuliiaHerets]

@zanyrenney High traffic account, but the issue also repro with a regular Expensifail account too

[zanyrenney]

Ah cheers @IuliiaHerets helpful!

[zanyrenney]

Adding external for more support here.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~010724ba54874de1b6

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @s77rt (External)

[melvin-bot]

@s77rt, @zanyrenney Eep! 4 days overdue now. Issues have feelings too...

[s77rt]

Not overdue. Still looking for proposals

[melvin-bot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[melvin-bot]

@s77rt @zanyrenney 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!

[s77rt]

Same ^

[melvin-bot]

@s77rt, @zanyrenney Whoops! This issue is 2 days overdue. Let's get this updated quick!

[zanyrenney]

https://expensify.slack.com/archives/C01GTK53T8Q/p1725271582824419

[wildan-m]

Looks like the PR merged, but I still able to reproduce the issue when deleting one of two money request from another device

Kapture.2024-10-01.at.07.19.01.mp4

[s77rt]

@kubabutkiewicz Would you be able to look into the above ^ bug?

[kubabutkiewicz]

Yes, I will be able to @s77rt

[kubabutkiewicz]

Hey hey, I was able to find what is the issue

App/src/components/InvertedFlatList/BaseInvertedFlatList/index.tsx

Lines 21 to 23 in 78e484f

	if (shouldEnableAutoScrollToTopThreshold) {
	config.autoscrollToTopThreshold = AUTOSCROLL_TO_TOP_THRESHOLD;
	}

Issue is here, when the issue occur autoscrollToTopThreshold prop is not set to true. I am checking now why this is happening as this is only happening on iOS

[kubabutkiewicz]

@s77rt I created a PR for fixing this issue. It was actually happening on all platforms. Videos for android will be added later since I have some problems with building app after pulling latest main.

[melvin-bot]

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

[melvin-bot]

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

• Fix/47584 #50433

If no regressions arise, payment will be issued on 2024-10-24. 🎊

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

• @s77rt requires payment through NewDot Manual Requests
• @kubabutkiewicz does not require payment (Contractor)

[melvin-bot]

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

• [@s77rt] The PR that introduced the bug has been identified. Link to the PR:
• [@s77rt] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
• [@s77rt] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
• [@s77rt] Determine if we should create a regression test for this bug.
• [@s77rt] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
• [@zanyrenney] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

[s77rt]

• The PR that introduced the bug has been identified: HIGH: (Comment linking: Step 4) Main "glue" PR for Comment Linking #30269
• The offending PR has been commented on: HIGH: (Comment linking: Step 4) Main "glue" PR for Comment Linking #30269 (comment)
• A discussion in #expensify-bugs has been started: Not needed
• Determine if we should create a regression test for this bug: No, and this already seems coming from a regression test

[zanyrenney]

payment summary

@s77rt requires payment through NewDot Manual Requests - please request $250 for this issue
@kubabutkiewicz does not require payment (Contractor) - no payment required.

[JmillsExpensify]

$250 approved for @s77rt

[tgolen]

Reopening so @zanyrenney can complete the regression checklist. Can you please copy @s77rt's answers to the checklist and then finish it up?

[zanyrenney]

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

• The PR that introduced the bug has been identified: HIGH: (Comment linking: Step 4) Main "glue" PR for Comment Linking #30269
• The offending PR has been commented on: HIGH: (Comment linking: Step 4) Main "glue" PR for Comment Linking #30269 (comment)
• A discussion in #expensify-bugs has been started: Not needed
• Determine if we should create a regression test for this bug: No, and this already seems coming from a regression test

[zanyrenney]

Ah, my understanding was the contributor does the checklist as there is no regression test here @tgolen as per this comment where they answered the questions. I've done it above now but I've always thought that was the case as their name is next to the checkboxes.

[melvin-bot]

Payment Summary

Upwork Job

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

BugZero Checklist (@zanyrenney)

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

[zanyrenney]

I added the checklist again above, and the payment summary is also above. I think we now are good to close.