-
Notifications
You must be signed in to change notification settings - Fork 306
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
Compatibility with React Native New Architecture #2202
Comments
There's nothing in New Architecture that should prevent Maestro from working - Maestro is implementation agnostic. So long as it's still 'accessible' (in both the technical and a11y meanings) then I'd expect it to work. I'd also expect that given how long New Architecture has been kicking around that we'd have seen a lot of complaints by now if it weren't working. |
This issue has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar problem, please file a new issue. Make sure to follow the template and provide all the information necessary to reproduce the issue. |
Reopening this, given some info from Slack that implies that this could end up as a bug rather than a question. Me:
Brett:
This could really use someone pointing at an example app in the New Architecture that would help us know one way or another. |
@Fishbowler awesome, thanks to give more context about the internal discussion. |
Hi team,
I would like to confirm Maestro's compatibility with React Native's New Architecture (Fabric and TurboModules). As React Native evolves, tools like Detox have had some challenges with supporting the New Architecture fully.
I couldn't find specific details in the documentation about this, and I want to ensure a smooth integration for my project.
Thank you in advance for your time and for building such a great tool!
The text was updated successfully, but these errors were encountered: