-
-
Notifications
You must be signed in to change notification settings - Fork 391
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use copilot with custom native-base components #31
Comments
Is it Only "native" components can be made walkthroughable using the https://github.com/okgrow/react-native-copilot#custom-components-as-steps |
Could you please confirm that you're using v2.2.2? |
Okay, thanks. I'm curious to see what happens with 2.2.1. |
I have already tried version 2.2.1, but I still have the same problem. |
It'd be good if you share a minimal code that helps me reproduce this issue. |
@dirkvanherpen Can you please now try v2.2.3? |
I have tried multiple versions to try to fix this, but I can't get the highlight parts exactly on the button. |
Facing the same issue when used with https://wix.github.io/react-native-navigation. |
@mohebifar Can you take another look at this, please? |
@sujitpk-perennial It is really hard to figure out what the issue is without being able to reproduce it. It would be great if you could provide a very minimal expo snack or a gist to help me reproduce this. |
@mohebifar I found that
Then I am able to see the color for text in Android.
if (this.props.androidStatusBarVisible && Platform.OS === 'android') {
|
You can add: copilot({
androidStatusBarVisible: false
}), |
@dirkvanherpen @mohebifar facing same issue in android. have you found any solution for it? |
It seems not possible to highlight buttons in the walkthrough.
I call
this.props.start();
so that shouldn't be the problem. It might have to do with the custom components in native-base. If we are using the normal components it works perfectly, but with the custom components, it won't.How can I make copilot work with custom native-base components?
The text was updated successfully, but these errors were encountered: