mohebifar / mohebifar/react-native-copilot
Walkthrough doesn't appear immediately after start()
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.4k
- Forks
- 428
- PR merge metrics
- No merged PRs in 30d
Description
Current Behavior
Whenever start() has been called in Mount there is atleast 2 seconds delay for Walkthrough to appear. In this two seconds if we navigate to another screen, Walkthrough appear on the next screen. Even If I add a delay for start() as mentioned in https://github.com/mohebifar/react-native-copilot/issues/18#issuecomment-364469685 same issue exists.
Input Code
componentDidMount() {
this.props.start();
}
export default copilot({
animated: true,
overlay: 'svg',
animationDuration: 100,
tooltipComponent: Tooltip,
stepNumberComponent: StepNumberComponent,
androidStatusBarVisible: true,
backdropColor: "rgba(000, 000, 000, 0.9)",
})(App);
Expected behavior/code
Walkthrough should appear immediately or it should not appear when we navigate to some other screen. If screen A and screen B has walkthrough, And if I navigate from screen A to screen B in a second then screen B will have two walkthroughs.
Environment
- Device: OnePlus 6
- OS: Android 9
react-native-copilot: 2.4.4react-native: 0.56.0react-native-svg: 6.3.1
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 by locating the implementation of start() and how the walkthrough is scheduled after componentDidMount. Reproduce the Android behavior with the provided configuration, navigating between screens during the delay. Done means the walkthrough appears promptly or is cancelled when navigation changes, without duplicate walkthroughs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100