Need help pulling in selectors

[Skeniston489]

Is there an existing issue for this?

• [X] I have searched the existing issues and didn't find mine.

Steps to reproduce

1. Check my syntax!

Actual results

Hello! I am pulling in selectors from my android/ios js file but when I run my test, Maestro is adding "" around all id's, causing them to be identified as text and then fail. This selector js file approach works fine for my subflows.

navigationTabs.js ` // Bottom tabs for navigating the app - Android

output.navigationTabs = { usageTab: 'com.telus.myaccount.dev:id/mobility_usage', billingTab: 'com.telus.myaccount.dev:id/mobility_billing', plansAndDevicesTab: 'com.telus.myaccount.dev:id/mobility_plans_travel', offersTab: 'com.telus.myaccount.dev:id/offers', };`

My test: `appId: ${output.appId} name: Test tabs navigation env: USERNAME: ## PASSWORD: ## onFlowStart:

• runFlow: ../subflows/loadElements.yaml
• runFlow: ../subflows/login.yaml onFlowComplete:

• runFlow: ../subflows/logout.yaml

  • assertVisible: ${output.navigationTabs.usageTab}
  • tapOn: ${output.navigationTabs.usageTab}
  • assertVisible: ${output.navigationTabs.billingTab}
  • tapOn: ${output.navigationTabs.billingTab}
  • assertVisible: ${output.navigationTabs.plansAndDevicesTab}
  • tapOn: ${output.navigationTabs.plansAndDevicesTab}
  • assertVisible: "Plan"
  • assertVisible: "Device"
  • assertVisible: "Travel"
  • assertVisible: ${output.navigationTabs.offersTab}
  • tapOn: ${output.navigationTabs.offersTab} `

Results: ![Uploading Screenshot 2024-10-16 at 2.55.04 PM.png…]()

Expected results

Test to correctly identify selectors as id's

About app

This is a closed-source app

About environment

macOS: 14.7, Apple M1

Logs

Logs

``` ```

Maestro version

1.38.1

How did you install Maestro?

install script (https://get.maestro.mobile.dev)

Anything else?

No response

[linear[bot]]

MA-2349 Need help pulling in selectors

[github-actions[bot]]

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. Thank you for helping keep us our issue tracker clean!