Error after updating maestro to CLI 1.39.9

[TsTeamDev]

Is there an existing issue for this?

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

Steps to reproduce

Error after updating maestro to CLI 1.39.9

1. In mac mini 2018 / OS 14.1.1 (23B81)
2. with previous release working - CLI 1.39.7
3. followed the steps to update to latest client
4. curl -fsSL "https://get.maestro.mobile.dev" | bash
5. after update the following error appears
6. after restart the machine the error remains

Actual results

Error after executing maestro:

with maestro version installed

• Create distribution directories...
• Downloading...
  ######################################################################## 100.0%
• Checking archive integrity...
• Extracting archive...
• Copying archive contents...
• Cleaning up...

Installation was successful!
Please open a new terminal OR run the following in the existing one:

export PATH="$PATH":"$HOME/.maestro/bin"

Then run the following command:

maestro

Welcome to Maestro!
user1@user1-Mini Maestro % maestro
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/Users/user1/.maestro/lib/logback-classic-1.2.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/Users/user1/.maestro/lib/logback-classic-1.2.3.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
Exception in thread "main" java.lang.NoSuchMethodError: 'com.fasterxml.jackson.databind.ObjectMapper com.fasterxml.jackson.module.kotlin.ExtensionsKt.jacksonObjectMapper$default(kotlin.jvm.functions.Function1, int, java.lang.Object)'
at maestro.cli.analytics.Analytics.(Analytics.kt:41)
at maestro.cli.AppKt.main(App.kt:108)

Expected results

Update process is done successfully

About app

Could not execute any test

About environment

• In mac mini 2018
• 3 GHz 6-Core Intel Core i5
• OS 14.1.1 (23B81)
• java 17.0.9 2023-10-17 LTS
• Java(TM) SE Runtime Environment (build 17.0.9+11-LTS-201)
• Java HotSpot(TM) 64-Bit Server VM (build 17.0.9+11-LTS-201, mixed mode, sharing)

Logs

Logs

<!-- Replace this line with your logs. *DO NOT* remove the backticks! -->

Maestro version

1.39.7

How did you install Maestro?

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

Anything else?

No response

[linear]

MA-2944 Error after updating maestro to CLI 1.39.9

[amanjeetsingh150]

Hey @TsTeamDev can you try updating with brew?

brew install maestro

[fuzzmonkey]

We're seeing a similar error, installing via curl -Ls "https://get.maestro.mobile.dev/" | bash

$ maestro --device "$SIMULATOR_ID" test --format junit e2e --exclude-tags=aiTest
Error: Exception in thread "main" java.lang.NoSuchMethodError: 'void maestro.debuglog.LogConfig.configure(java.lang.String, boolean)'
	at maestro.cli.report.TestDebugReporter.install(TestDebugReporter.kt:158)
	at maestro.cli.command.TestCommand.call(TestCommand.kt:176)
	at maestro.cli.command.TestCommand.call(TestCommand.kt:65)
	at picocli.CommandLine.executeUserObject(CommandLine.java:1953)
	at picocli.CommandLine.access$1300(CommandLine.java:145)
	at picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:[23](https://github.com/TreeCard/wildhero-mail-app/actions/runs/12868280063/job/35887277027?pr=1916#step:11:24)58)
	at picocli.CommandLine$RunLast.handle(CommandLine.java:2352)
	at picocli.CommandLine$RunLast.handle(CommandLine.java:2314)
	at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2179)
	at picocli.CommandLine$RunLast.execute(CommandLine.java:2316)
	at maestro.cli.DisableAnsiMixin$Companion.executionStrategy(DisableAnsiMixin.kt:22)
	at picocli.CommandLine.execute(CommandLine.java:2078)
	at maestro.cli.AppKt.main(App.kt:143)
error Command failed with exit code 1.

[amanjeetsingh150]

This should be fixed now! We've updated and fixed the script. You can try updating again. Let me know if you still see issues.

[TsTeamDev]

This should be fixed now! We've updated and fixed the script. You can try updating again. Let me know if you still see issues.

Hi,
reported error is solved,
unfortunately the following error appears after text execution starts:
Exception in thread "main" java.lang.NoSuchMethodError: 'void util.LocalSimulatorUtils.setPermissions(java.lang.String, java.lang.String, java.util.Map)' at ios.simctl.SimctlIOSDevice.setPermissions(SimctlIOSDevice.kt:164) at ios.LocalIOSDevice.setPermissions(LocalIOSDevice.kt:149) at maestro.drivers.IOSDriver$setPermissions$1$1.invoke(IOSDriver.kt:486) at maestro.drivers.IOSDriver$setPermissions$1$1.invoke(IOSDriver.kt:485) at maestro.drivers.IOSDriver.runDeviceCall(IOSDriver.kt:530) at maestro.drivers.IOSDriver.access$runDeviceCall(IOSDriver.kt:43) at maestro.drivers.IOSDriver$setPermissions$1.invoke(IOSDriver.kt:485) at maestro.drivers.IOSDriver$setPermissions$1.invoke(IOSDriver.kt:484) at maestro.utils.Metrics.measured(Metrics.kt:48) at maestro.drivers.IOSDriver.setPermissions(IOSDriver.kt:484) at maestro.Maestro.setPermissions(Maestro.kt:93) at maestro.orchestra.Orchestra.launchAppCommand(Orchestra.kt:854) at maestro.orchestra.Orchestra.executeCommand(Orchestra.kt:282) at maestro.orchestra.Orchestra.executeCommands(Orchestra.kt:197) at maestro.orchestra.Orchestra.runFlow(Orchestra.kt:130) at maestro.cli.runner.MaestroCommandRunner.runCommands(MaestroCommandRunner.kt:179) at maestro.cli.runner.TestRunner$runSingle$result$1.invoke(TestRunner.kt:63) at maestro.cli.runner.TestRunner$runSingle$result$1.invoke(TestRunner.kt:54) at maestro.cli.runner.TestRunner.runCatching(TestRunner.kt:161) at maestro.cli.runner.TestRunner.runSingle(TestRunner.kt:54) at maestro.cli.command.TestCommand.runSingleFlow(TestCommand.kt:367) at maestro.cli.command.TestCommand.access$runSingleFlow(TestCommand.kt:65) at maestro.cli.command.TestCommand$runShardSuite$2.invoke(TestCommand.kt:338) at maestro.cli.command.TestCommand$runShardSuite$2.invoke(TestCommand.kt:308) at maestro.cli.session.MaestroSessionManager.newSession(MaestroSessionManager.kt:105) at maestro.cli.session.MaestroSessionManager.newSession$default(MaestroSessionManager.kt:53) at maestro.cli.command.TestCommand.runShardSuite(TestCommand.kt:308) at maestro.cli.command.TestCommand.access$runShardSuite(TestCommand.kt:65) at maestro.cli.command.TestCommand$handleSessions$1$results$1$1.invokeSuspend(TestCommand.kt:276) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104) at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:111) at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:99) at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:585) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:802) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:706) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:693)

[github-actions]

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!