React Native Automation That Doesn't Fight the Element Tree
On iOS, React Native page source usually comes back as deeply nested wrappers with nothing worth writing a locator against. In our inspector it does not: a React Native app shows up the way any native app does, with elements you can actually address. Real Android and iOS hardware, your existing suites unchanged.
React Native Looks Like Any Native App
Every React Native team hits the same wall on iOS: a page source of nested wrappers you cannot write a sane locator against. Open the same build in our inspector and the elements come back as they would for a native app — named and addressable. React Native stops being a special case, and the hierarchy stops deciding whether your test can find a button.
Real Hardware, Both Platforms
Real Android and iOS devices — never emulators or simulators. React Native behaves differently on real hardware, and the iOS gap is exactly where the surprises live.
Your Suites Run Unchanged
Appium, WebdriverIO, Selenium and Playwright are first-class here. Point an existing suite at a device and it runs — there is no rewrite, and no new framework to learn.
Let an AI Agent Drive It
Claude, Cursor or an agent you built can drive a real phone over MCP, controlling the device directly rather than through an automation wrapper. It can explore your React Native app, write the automation, and analyse the runs afterwards.
One Accessibility ID, Both Platforms
A React Native testID maps to the accessibility id on iOS and on Android, so one locator drives both platforms. Write it once and maintain it once — provided the tooling actually surfaces those ids on iOS, which is exactly where most setups fall down and this one does not.
Debug What Actually Happened
Capture web and native network traffic on both platforms, mock responses mid-run, and set device location or language without opening a settings menu. An AI agent can do all of it while it works, and analyse the run afterwards.
Getting a React Native App Under Test
Three steps, and none of them involve rewriting your locators.
Install the build on a real device
Upload your .ipa or .apk and open it on a real Android or iOS device from the browser. No lab, no cables, no provisioning of your own.
Point your suite or your agent at it
Run an existing Appium or WebdriverIO suite against the device, or connect an AI agent over MCP and let it work the app directly.
Debug with everything visible
Watch the run live, capture web and native network traffic, mock responses mid-run, and set device location or language without opening a settings menu.
Try It on Your Own React Native App
The free tier needs no credit card. If the iOS element tree has been costing you afternoons, this takes about ten minutes to disprove or confirm.