mohebifar / mohebifar/react-native-copilot
Copilot works in expo go but not in standalone (testflight)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.4k
- Forks
- 428
- PR merge metrics
- No merged PRs in 30d
Description
Current Behavior
Copilot works great when running through expo go. However, I pushed to TestFlight and all of a sudden when navigating to Copilot screen, you see a glimpse of the screen and whole screen goes plain white.
Input Code
How I setup copilot.
`const Copilot = (props) => {
const CopilotText = walkthroughable(Text);
const CopilotImage = walkthroughable(Image);
useEffect(() => {
props.copilotEvents.on();
props.start();
}, [])
useEffect(() => {
props.copilotEvents.on("stop", CopilotDone)
console.log(navigation)
})
const CopilotDone = (step) => {
navigation.navigate('CompleteScreen');
}
const navigation = useNavigation(); `
Example of how I setup a Copilot step.
`
<CopilotStep
text="This is an example of a workout program you can make"
order={1}
name="first"
>
<CopilotText
style={[
tailwind("font-[800] text-[25px] ml-4 "),
{ color: "#f4f4f4", },
]}
>
My Program
</CopilotText>
</CopilotStep>
</View>`
Expected behavior/code
I expect Copilot to start as soon as a user gets navigated to this screen.
Environment
- IOS TestFlight
- Expo Go with IPhone 12 simulator
"react-native-copilot": "^2.5.1","react-native": "0.64.3",
Additional context/Screenshots

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 with the Copilot component, its useEffect hooks, and the CopilotStep example, then reproduce the transition in Expo Go and an iOS TestFlight build using react-native-copilot 2.5.1. Compare the standalone behavior when the screen is opened; done means Copilot starts on navigation without the screen becoming white.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100