react-native-copilot icon indicating copy to clipboard operation
react-native-copilot copied to clipboard

Multiple Copilot Tutorials

Open Alex-Ying opened this issue 2 years ago • 6 comments

If I wanted to create multiple copilot tutorials on the same application (but on different features), would that be possible? If so, how would I go about implementing it?

Alex-Ying avatar Aug 08 '23 14:08 Alex-Ying

Anyone found a solution for this?

virginiab10 avatar Aug 06 '24 15:08 virginiab10

this is critical for the library, currently I had to disable majority of library feature to have multiple tutorials

msidqi avatar Aug 27 '24 17:08 msidqi

Anyone found a solution for this?

Wrap your root component aka App.js with Provider. and use start() in useEffect or button in every screen you want to show tooltips.

quassainraza avatar Nov 23 '24 00:11 quassainraza

Anyone found a solution for this?

Wrap your root component aka App.js with Provider. and use start() in useEffect or button in every screen you want to show tooltips.

I'm probably doing it wrong, but this causes subsequent screens to try to run the original steps on the first screen. I have also tried number the steps independently and starting at that nubmer but it appears to not correctly run my other range of steps.

drsib avatar Nov 24 '24 23:11 drsib

I know the issue is old but maybe this can help others with the same issue. We were able to create multiple tours creating different <CopilotProvider> instances. It works even when nested inside another <CopilotProvider> (it uses the context of the closest instance). Hope this helps!

carozo avatar Apr 30 '25 18:04 carozo

I know the issue is old but maybe this can help others with the same issue. We were able to create multiple tours creating different <CopilotProvider> instances. It works even when nested inside another <CopilotProvider> (it uses the context of the closest instance). Hope this helps!

Thanks for sharing that solution! That's definitely a valid approach for handling multiple tours. We actually tackled this differently in our implementation. Instead of using multiple <CopilotProvider> instances, we created a unified tutorial system that handles multiple tutorial types through a single provider with a tutorialType parameter.

Here's what we did: Single TutorialProvider that manages all tutorial flows Parameterized components (useTutorial(tutorialType), TutorialStep tutorialType="HOME")

bartusisman avatar Jul 08 '25 05:07 bartusisman