You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues and didn't find mine.
Steps to reproduce
On Android, assertVisible with enabled: false fails to find a visible disabled button. It works as expected on iOS. I've created a repo that is a npx expo-create-app@latest application:
Tools
git git version 2.48.1 /opt/homebrew/bin/git
Logs
Logs
Running on emulator-5554
║
║ > Flow: disabledButton
║
║ ✅ Launch app "com.maestrodisabled.bug"
║ ✅ Assert that "Enabled Button" is visible
║ ❌ Assert that "Disabled Button" is visible
║ 🔲 Assert that "Enabled Button" is not visible
║ 🔲 Assert that "Disabled Button" is not visible
║
Assertion is false: "Disabled Button" is visible
Maestro version
1.39.9
How did you install Maestro?
Homebrew
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Steps to reproduce
On Android,
assertVisible
withenabled: false
fails to find a visible disabled button. It works as expected on iOS. I've created a repo that is anpx expo-create-app@latest
application:Actual results
On Android, the
maestro/disabledButton.yaml
flow fails. On iOS, it passes.Expected results
Expect the flow to pass on both platforms.
About app
Here's an open source repro app: https://github.com/morganick/maestrodisabledbug
About environment
System
platform darwin
arch arm64
cpu 16 cores Apple M4 Max
directory MaestroDisabledBug
JavaScript (and globally-installed packages)
node 21.6.2
npm 10.2.4
corepack 0.24.0
eas-cli 14.4.1
npm 10.2.4
yarn 1.22.22
pnpm 9.15.4
bun - not installed
expo 52.0.27 managed
Ignite
ignite-cli 10.1.4
ignite src build
Android
java 17.0.13
iOS
xcode 16.2
cocoapods 1.16.2
Tools
git git version 2.48.1 /opt/homebrew/bin/git
Logs
Logs
Maestro version
1.39.9
How did you install Maestro?
Homebrew
Anything else?
No response
The text was updated successfully, but these errors were encountered: