Studio and flow cannot be run at the same time

[jreimone]

Is there an existing issue for this?

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

Steps to reproduce

I cannot run the Maestro Studio and a test flow against an Android Emulator app at the same time on MacOs. But I could run the test flow when I closed the Studio.

Actual results

Test Flow fails with the launch command:

Running on emulator-5554                  
                                          
 ║                                        
 ║  > Flow: android-flow                  
 ║                                        
 ║    ❌   Launch app "org.wikipedia"     
 ║                                        
                                          
Unable to launch app org.wikipedia: null

==== Debug output (logs & screenshots) ====

Expected results

I can run the Studio and the test at the same time.

About app

Downloaded with maestro download-samples and used sample.apk

About environment

MacOS Sequoia 15.1.1 with

java --version
openjdk 17.0.13 2024-10-15 LTS

Logs

Logs

maestro.log
───────┼──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
   1   │ 14:21:27.362 [ INFO] MAESTRO.logSystemInfo: ---- System Info ----
   2   │ 14:21:27.363 [ INFO] MAESTRO.logSystemInfo: Maestro Version: 1.39.4
   3   │ 14:21:27.364 [ INFO] MAESTRO.logSystemInfo: CI: Undefined
   4   │ 14:21:27.364 [ INFO] MAESTRO.logSystemInfo: OS Name: Mac OS X
   5   │ 14:21:27.364 [ INFO] MAESTRO.logSystemInfo: OS Version: 15.1.1
   6   │ 14:21:27.364 [ INFO] MAESTRO.logSystemInfo: Architecture: aarch64
   7   │ 14:21:27.364 [ INFO] MAESTRO.logSystemInfo: Java Version: 17
   8   │ 14:21:27.611 [DEBUG] io.micrometer.common.util.internal.logging.InternalLoggerFactory.newDefaultFactory: Using SLF4J as the default logging framework
   9   │ 14:21:28.038 [ INFO] MAESTRO.logSystemInfo: Xcode Version: 16.2
  10   │ 14:21:28.043 [ INFO] MAESTRO.logSystemInfo: Flutter Version: Undefined
  11   │ 14:21:28.047 [ INFO] MAESTRO.logSystemInfo: Flutter Channel: Undefined
  12   │ 14:21:28.047 [ INFO] MAESTRO.logSystemInfo: ---------------------
  13   │ 14:21:28.682 [ INFO] maestro.cli.command.TestCommand.runShardSuite: [shard 1] Selected device emulator-5554 using port 7001
  14   │ 14:21:29.102 [ INFO] maestro.Maestro.invoke: Getting device info
  15   │ 14:21:29.206 [ INFO] maestro.Maestro.invoke: Got device info: DeviceInfo(platform=ANDROID, widthPixels=1080, heightPixels=2424, widthGrid=1080, heightGrid=2424)
  16   │ 14:21:29.260 [ INFO] maestro.cli.runner.MaestroCommandRunner.invoke: Define variables RUNNING
  17   │ 14:21:29.261 [ INFO] maestro.cli.runner.MaestroCommandRunner.invoke: Define variables metadata CommandMetadata(numberOfRuns=null, evaluatedCommand=MaestroCommand(defineVariablesCommand=DefineVariablesCommand(env={MAESTRO_CLI_AI_KEY=<myKey>, MAESTRO_CLI_AI_MODEL=<myModel>, MAESTRO_FILENAME=android-flow}, la
       │ bel=null, optional=false)), logMessages=[], insight=Insight(message=, level=NONE), action=null)
  18   │ 14:21:29.263 [ INFO] maestro.cli.runner.MaestroCommandRunner.invoke: Define variables COMPLETED
  19   │ 14:21:29.263 [ INFO] maestro.cli.runner.MaestroCommandRunner.invoke: Apply configuration RUNNING
  20   │ 14:21:29.263 [ INFO] maestro.cli.runner.MaestroCommandRunner.invoke: Apply configuration metadata CommandMetadata(numberOfRuns=null, evaluatedCommand=MaestroCommand(applyConfigurationCommand=ApplyConfigurationCommand(config=MaestroCo
       │ nfig(appId=org.wikipedia, name=null, tags=[android, passing], ext={}, onFlowStart=null, onFlowComplete=null), label=null, optional=false)), logMessages=[], insight=Insight(message=, level=NONE), action=null)
  21   │ 14:21:29.264 [ INFO] maestro.cli.runner.MaestroCommandRunner.invoke: Apply configuration COMPLETED
  22   │ 14:21:29.264 [ INFO] maestro.cli.runner.MaestroCommandRunner.invoke: Launch app "org.wikipedia" RUNNING
  23   │ 14:21:29.264 [ INFO] maestro.cli.runner.MaestroCommandRunner.invoke: Launch app "org.wikipedia" metadata CommandMetadata(numberOfRuns=null, evaluatedCommand=MaestroCommand(launchAppCommand=LaunchAppCommand(appId=org.wikipedia, clearS
       │ tate=null, clearKeychain=null, stopApp=null, permissions=null, launchArguments=null, label=null, optional=false)), logMessages=[], insight=Insight(message=, level=NONE), action=null)
  24   │ 14:21:29.590 [ INFO] maestro.Maestro.launchApp: Launching app org.wikipedia
  25   │ 14:21:34.620 [ INFO] maestro.Maestro.takeScreenshot: Taking screenshot
  26   │ 14:21:34.622 [TRACE] maestro.utils.ScreenshotUtils.takeScreenshot: Taking screenshot to output sink
  27   │ 14:21:36.752 [ INFO] maestro.cli.runner.MaestroCommandRunner.invoke: Launch app "org.wikipedia" FAILED

Maestro version

1.39.4

How did you install Maestro?

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

Anything else?

No response

[linear]

MA-2778 Studio an flow cannot be run at the same time

[Fishbowler]

This normally comes down to resources. Maestro uses a 'chatty' protocol, and polls often. On some machines or some destinations, it's not sustainable to run concurrently.

That being said, that error of simply null isn't very good. I'd expect to see an error about a driver timeout or similar.

[jreimone]

Thanks for your response @Fishbowler. Can I do something more to workaround this? Or can I support here to investigate it further (can you reproduce it)?

[tlow92]

@Fishbowler I also have this issue. I my opinion it's very easy to reproduce like this:

(btw. this is my common workflow for creating new tests, that's why it's a bit annoying for me)

1. Start maestro in continuous mode maestro test newTest.yaml -c
2. Let maestro "finish" running the current file. Maestro is waiting in continuous mode until you save the file.
3. In separate terminal run maestro studio to check some id's are other locators
4. close maestro studio again (btw. by now maestro studio is already returning a infinite loop of errors in terminal)
5. save test file to continue with writing test
6. maestro process hangs and doesn't run anymore

In my case it's not about being able to run maestro commands from two terminals at the same time. It's just about being able to write a test in continuous mode and being able to use maestro studio to find locators. I understand that technically the problem is that two instances of maestro are run at the same time.

I hope my input helps

[jerone]

Duplicate #1927

[pplourde]

This normally comes down to resources. Maestro uses a 'chatty' protocol, and polls often. On some machines or some destinations, it's not sustainable to run concurrently.

I think my main gripe about this issue is it used to work before and at some point after an update it stopped working. Surely if it worked before on the same system I'm using now it should be able to work again.

More specifically it stopped working for me (and everyone at the company I work at) after updating to 1.37.0. It's not the end of the world as I'm now used to making sure to close Maestro Studio prior to running a flow, but it's still an extra step that doesn't need to exist and didn't exist before.

[Fishbowler]

That's interesting intel. Have you taken a look at the project source, and dug into what you suspect the cause is?

[pplourde]

Unfortunately my technical knowledge is too limited to make heads or tails of this, I did provide as much info as I had in this ticket a while back #1927