React Native 0.78 ListItem.Accordion Each child in a list should have a unique "key" prop.

Open
#3,968 9 comments 9 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
react, react-native
Domain
mobile

Research direction

Start by reproducing the warning with ListItem.Accordion on React Native 0.78 using the dependency versions in the issue, then inspect the component path involving PadView. The issue provides screenshots rather than a runnable code sample, so confirm whether the warning comes from the component or its usage; done means identifying the source and preventing the warning without requiring callers to change valid keys.

Written by the indexing model from the issue text.

Description

Needs Triage
Is there an existing issue for this?
  • I have searched the existing issues
Explain what you did

I directly copied the following code in React Native 0.78 version

Image

Expected behavior

Image

Image

“Each child in a list should have a unique "key" prop. Check the render method of View. It was passed a child from PadView.”

Describe the bug

I have already set the key, but this error still occurred
“Each child in a list should have a unique "key" prop. Check the render method of View. It was passed a child from PadView.”

Steps To Reproduce
![Image](https://github.com/user-attachments/assets/16de3cf6-36af-4139-bc0c-46d39203231c)

![Image](https://github.com/user-attachments/assets/1fbdbabb-42cc-4829-bbf7-8d706b11be72)

“Each child in a list should have a unique "key" prop. Check the render method of `View`. It was passed a child from PadView.”
Screenshots

No response

Your Environment

Global Dependencies:

No related dependency found

Local Dependencies:

  • @rneui/base : ^4.0.0-rc.8
  • @rneui/themed : ^4.0.0-rc.8
  • react : 18.3.1
  • react-native : 0.78.0
  • @types/react : ^19
Dominant language
MDX
Stars
25.9k
Forks
4.7k
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from react-native-elements/react-native-elements

All issues in react-native-elements/react-native-elements

Similar issues

More Mobile Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.