CopilotKit / CopilotKit/CopilotKit
🐛 Bug: A2UI components are not supported in React Native environment
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 4.6k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 444
Description
♻️ Reproduction Steps
- Run CopilotKit in React Native or React Native Web environment
- Send a message containing A2UI structured content
- Observe that A2UI components are not rendered
- Content falls back to plain text or is ignored
✅ Expected Behavior
A2UI components should be properly rendered in React Native environment, similar to web behavior.
Structured UI messages should be parsed and rendered as native components instead of being ignored or rendered as raw text.
❌ Actual Behavior
A2UI works correctly in web environment but is not rendered in React Native.@copilotkit/react-native
Screenshots
No response
𝌚 CopilotKit Version
"@copilotkit/react-native": "^1.61.2",
📄 Logs (Optional)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the @copilotkit/react-native package and reproduce the issue by sending a message containing A2UI structured content in React Native or React Native Web. Compare the behavior with the web environment and trace how the structured message is handled; done means A2UI content is parsed and rendered as native components rather than ignored or shown as plain text.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- frontend, mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100