What should be automationName capability?

Hi All,

I want to discuss about automationName capability. My app is developed
using flutter and webview(for login process).

For automating the same app, what should I use for automationName capability?

Currently I am using below capability in my appium.

“platformName”: “Android”,
“appium:deviceName”: “Pixel 5 API 30”,
“appium:automationName”: “UIAutomator2”

but my developer added keys in the code to uniquely identify the elements in the app, so, loading above capabilities and building the apk debug, I could not able to see his changes reflected while using appium inspector.

Can someone please advise me what we might be missing at our end?

Thanks :slight_smile:

check example -> https://github.com/appium-userland/appium-flutter-driver ->

I read the link and tried the below code:
My code:

 const wdio = require('webdriverio');
    const assert = require('assert');
    const find = require('appium-flutter-finder');
    const osSpecificOps = process.env.APPIUM_OS === 'android' ? {
      platformName: 'Android',
      deviceName: 'Pixel 5 API 30',
      // @todo support non-unix style path
    }: process.env.APPIUM_OS === 'ios' ? {
      platformName: 'iOS',
      platformVersion: '15.4',
      deviceName: 'iPhone 13',
      noReset: true,
      app: '/Users/builder/Library/Developer/Xcode/DerivedData/Runner-edaimyiflreloheqntgnhkmwcclv/Build/Products/Debug-iphonesimulator/Runner.app',

    } : {};

    const opts = {
      port: 4723,
      capabilities: {
        automationName: 'Flutter',
        retryBackoffTime: 500,

      (async () => {
        console.log('Initial app testing');
        const driver = await wdio.remote(opts);

        // // Enter login page
        await driver.execute('flutter:waitFor', find.byValueKey('button_sign_in_google'));


Error while testing the code
~/Dev/work/repos/gelato-api-mobile/integration-tests # APPIUM_OS=ios npm start

> [email protected] start /Users/harsha.sharmagelato.com/Dev/work/repos/gelato-api-mobile/integration-tests
> node ./src/stepDefinitions/test.js

Initial app testing
2022-06-30T15:20:23.144Z INFO webdriver: Initiate new session using the WebDriver protocol
2022-06-30T15:20:23.178Z INFO webdriver: [POST]
2022-06-30T15:20:23.178Z INFO webdriver: DATA {
  capabilities: {
    alwaysMatch: {
      platformName: 'iOS',
      platformVersion: '15.4',
      deviceName: 'iPhone 13',
      noReset: true,
      app: '/Users/builder/Library/Developer/Xcode/DerivedData/Runner-edaimyiflreloheqntgnhkmwcclv/Build/Products/Debug-iphonesimulator/Runner.app',
      automationName: 'Flutter',
      retryBackoffTime: 500
    firstMatch: [ {} ]
  desiredCapabilities: {
    platformName: 'iOS',
    platformVersion: '15.4',
    deviceName: 'iPhone 13',
    noReset: true,
    app: '/Users/builder/Library/Developer/Xcode/DerivedData/Runner-edaimyiflreloheqntgnhkmwcclv/Build/Products/Debug-iphonesimulator/Runner.app',
    automationName: 'Flutter',
    retryBackoffTime: 500
2022-06-30T15:20:23.186Z ERROR webdriver: RequestError: connect ECONNREFUSED
    at ClientRequest.<anonymous> (/Users/harsha.sharmagelato.com/Dev/work/repos/gelato-api-mobile/integration-tests/node_modules/got/dist/source/core/index.js:962:111)
    at Object.onceWrapper (events.js:520:26)
    at ClientRequest.emit (events.js:412:35)
    at ClientRequest.emit (domain.js:475:12)
    at ClientRequest.origin.emit (/Users/harsha.sharmagelato.com/Dev/work/repos/gelato-api-mobile/integration-tests/node_modules/@szmarczak/http-timer/dist/source/index.js:43:20)
    at Socket.socketErrorListener (_http_client.js:475:9)
    at Socket.emit (events.js:400:28)
    at Socket.emit (domain.js:475:12)
    at emitErrorNT (internal/streams/destroy.js:106:8)
    at emitErrorCloseNT (internal/streams/destroy.js:74:3)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16)
(node:76702) UnhandledPromiseRejectionWarning: Error: Failed to create session.
Unable to connect to "", make sure browser driver is running on that address.
If you use services like chromedriver see initialiseServices logs above or in wdio.log file as the service might had problems to start the driver.
    at startWebDriverSession (/Users/harsha.sharmagelato.com/Dev/work/repos/gelato-api-mobile/integration-tests/node_modules/webdriver/build/utils.js:72:15)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at async Function.newSession (/Users/harsha.sharmagelato.com/Dev/work/repos/gelato-api-mobile/integration-tests/node_modules/webdriver/build/index.js:46:45)
    at async Object.remote (/Users/harsha.sharmagelato.com/Dev/work/repos/gelato-api-mobile/integration-tests/node_modules/webdriverio/build/index.js:77:22)
    at async /Users/harsha.sharmagelato.com/Dev/work/repos/gelato-api-mobile/integration-tests/src/stepDefinitions/test.js:30:20
(Use `node --trace-warnings ...` to show where the warning was created)
(node:76702) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:76702) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Any idea what is missing here?

Second link on a web search gave a nice tutorial in javascript on installing and using Flutter driver. Here is the web search:


Here is the tutorial:


Similar type of details are already mentioned by @Aleksei. I have already implemented all this in my code.

Are you installed appium 2.0?
Not sure how flutter driver but with ios driver appium needs wda setup with adding dev signature. I am sure similar needed for flutter with ios (i may lie :slight_smile: and real device. Never tried flutter driver).
Try enter issue at flutter git.