[WAITING ON CHECKLIST] [$250] Android - Reports - Initial values overlap navigation bar

[jponikarchuk]

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: 9.2.43-0-staging
Reproducible in staging?: Yes
Reproducible in production?: Unable to validate in Prod, Initial value is not a interactive button in Prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #73899
Email or phone of affected tester (no customers): applausetester+qbo@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Samsung A15, Android 15.
App Component: Other

Action Performed:

Precondition:
User has a workspace connected to QBO with report fields imported.
Test account: applausetester+qbo@applause.expensifail.com

1. Open Android app.
2. Navigate to the connected workspace.
3. Go to Reports
4. Under Report fields, tap Customers/Projects
5. Tap Initial Value

Expected Result:

Users should be able to view and interact with the values without obstruction.

Actual Result:

Navigation bar overlaps initial values

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021985726321360727768
• Upwork Job ID: 1985726321360727768
• Last Price Increase: 2025-11-04
• Automatic offers:
• aimane-chnaif | Reviewer | 109368509

Issue Owner

Current Issue Owner: @jliexpensify / @stephanieelliott

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

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

[github-actions]

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

[ChavdaSachin]

Proposal

Please re-state the problem that we are trying to solve in this issue.

What is the root cause of that problem?

A case was missing during refactoring of selection list
This PR introduced new optimized selection list component which has a missing case for including bottom safe area padding when footer content is empty. And this PR migrated the ReportFieldsInitialListValuePicker.tsx to use new optimized selection list.

Previously there was a logic to add bottom safe area padding to when footer content was missing

App/src/components/SelectionListWithSections/BaseSelectionListWithSections.tsx

Line 981 in 995eec3

const shouldHideContentBottomSafeAreaPadding = showConfirmButton || !!footerContent;

App/src/components/SelectionListWithSections/BaseSelectionListWithSections.tsx

Line 1053 in 995eec3

addBottomSafeAreaPadding={!shouldHideContentBottomSafeAreaPadding && addBottomSafeAreaPadding}

But current implementation does not include this padding here

App/src/components/SelectionList/BaseSelectionList.tsx

Lines 382 to 403 in 59123b4

	<FlashList
	data={data}
	renderItem={renderItem}
	ref={listRef}
	keyExtractor={(item) => item.keyForList}
	ListFooterComponent={listFooterContent}
	scrollEnabled={scrollEnabled}
	indicatorStyle="white"
	keyboardShouldPersistTaps="always"
	showsVerticalScrollIndicator={showScrollIndicator}
	onEndReached={onEndReached}
	onEndReachedThreshold={onEndReachedThreshold}
	style={listStyle as ViewStyle}
	initialScrollIndex={initialFocusedIndex}
	onScrollBeginDrag={onScrollBeginDrag}
	ListHeaderComponent={
	<>
	{customListHeaderContent}
	{textInputComponent({shouldBeInsideList: true})}
	</>
	}
	/>

What changes do you think we should make in order to solve the problem?

Include safeAreaPadding here.

App/src/components/SelectionList/BaseSelectionList.tsx

Lines 382 to 403 in 59123b4

	<FlashList
	data={data}
	renderItem={renderItem}
	ref={listRef}
	keyExtractor={(item) => item.keyForList}
	ListFooterComponent={listFooterContent}
	scrollEnabled={scrollEnabled}
	indicatorStyle="white"
	keyboardShouldPersistTaps="always"
	showsVerticalScrollIndicator={showScrollIndicator}
	onEndReached={onEndReached}
	onEndReachedThreshold={onEndReachedThreshold}
	style={listStyle as ViewStyle}
	initialScrollIndex={initialFocusedIndex}
	onScrollBeginDrag={onScrollBeginDrag}
	ListHeaderComponent={
	<>
	{customListHeaderContent}
	{textInputComponent({shouldBeInsideList: true})}
	</>
	}
	/>

                        contentContainerStyle={!footerContent && addBottomSafeAreaPadding && paddingBottomStyle}

I could notice the new selectionList component also lacks addOfflineIndicatorBottomSafeAreaPadding so we should check and add this as well if needed

Small style changes could be fixed during PR phase if needed

What alternative solutions did you explore? (Optional)

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.