[Bug] FlatList in search results has no keyExtractor — React key warning and potential render bugs

[RUKAYAT-CODER]

Overview

The search results FlatList does not have a keyExtractor prop. React Native uses the array index as the key, causing incorrect re-renders when results are reordered or filtered, and triggering React key warnings in development.

Specifications

Features:

• Add keyExtractor={(item) => item.id} to the search results FlatList
• Confirm all other FlatLists in the app have unique, stable key extractors

Tasks:

• Add keyExtractor to the search results list
• Audit all FlatList usages in the codebase for missing keyExtractor
• Write a test that renders the list with reordered results and confirms no key warning

Impacted Files:

• src/screens/SearchScreen.tsx
• All FlatList usages missing keyExtractor

Acceptance Criteria

• No React key warnings in development mode
• List re-renders correctly when results are reordered
• All FlatLists in the app have stable keyExtractors

[macsonfleek]

@macsonfleek has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I would love to work on this issue, and give it my best, please assign me to this for gaining project experience while learning on the go

ℹ️ Repo Maintainers: To accept this application, review their application or assign @macsonfleek to this issue.

[esthereze]

@esthereze has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I would love to work on this project

ℹ️ Repo Maintainers: To accept this application, review their application or assign @esthereze to this issue.

[GreatShinro]

@GreatShinro has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi, I would like to work on this please?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @GreatShinro to this issue.

[Ibinola]

@Ibinola has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I want to take on this task. I will carefully analyze the issue, implement a clean solution, and ensure it integrates seamlessly with the current codebase without introducing regressions.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ibinola to this issue.

[drips-wave]

Congratulations, @Ibinola! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @Ibinola: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊