Merge pull request #529 from bugsnag/tms/new-command-timeout

Correct setting of newCommandTimeout
bugsnag · May 9, 2023 · de951b7 · de951b7
2 parents 202afa2 + dfc74d9
commit de951b7
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 2 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,4 +1,4 @@
-# 7.29.0 - TBD
+# 7.29.0 - 2023/05/09
 
 ## Enhancements
 
@@ -9,6 +9,7 @@
 
 - Only use separate BitBar accounts on CI [526](https://github.com/bugsnag/maze-runner/pull/526)
 - Ensure BitBar apiKey is provided when using the tunnel [527](https://github.com/bugsnag/maze-runner/pull/527)
+- Correct setting of `newCommandTimeout` capability for BitBar Appium sessions [529](https://github.com/bugsnag/maze-runner/pull/529)
 
 # 7.28.0 - 2023/05/02
 

diff --git a/lib/maze/client/appium/bb_client.rb b/lib/maze/client/appium/bb_client.rb
@@ -29,12 +29,12 @@ def device_capabilities
           prefix = BitBarDevices.caps_prefix(config.appium_version)
           capabilities = {
             "#{prefix}noReset" => true,
+            "#{prefix}newCommandTimeout" => 0,
             'bitbar:options' => {
               # Some capabilities probably belong in the top level
               # of the hash, but BitBar picks them up from here.
               'apiKey' => config.access_key,
               'app' => config.app,
-              "#{prefix}newCommandTimeout" => 0,
               'findDevice' => false,
               'testTimeout' => 7200
             }