mohebifar / mohebifar/react-native-copilot
Calling start() on useEffect does not register/use all steps, only the first one
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.4k
- Forks
- 428
- PR merge metrics
- No merged PRs in 30d
Description
Current Behavior
Calling start on useEffect does not register steps. After clicking "next" it moves to next walkthrouable item, but in the current step always displays the first step content.
However, totalSteps displays correct number of steps.
import { useCopilot } from 'react-native-copilot';
const { start } = useCopilot();
useEffect(() => {
start()
},[])
[.. in the return function as in /example folder]
Expected behavior/code
Steps are registered and "next" press works correctly.
Environment
- Device: [iPhone 15 Pro Max Simulator]
- OS: [17.4]
react-native-copilot: [3.3.2]react-native: [71.14]react-native-svg: [14.0.0]
Possible Solution
I was able to solve this by adding timeout of 3s in the useEffect.
setTimeout(() => { start() }, 3000
Additional context/Screenshots
I don't know why it happens, any idea how we can fix it?
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 example folder and the useCopilot/start path, reproducing the provided useEffect case on the stated React Native setup. Trace when steps are registered relative to start(); done means every registered step has its own content and Next advances through matching content rather than repeating the first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100