Original error: Error executing adbExec. Original error: 'Command '/usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 install /users/vagrant/deploy/app-release.apk' timed out after 90000ms'

I am running my tests through Bitrise and when I run my tests, I receive this error.

Below is my log. Any help on why it is timing out would be appreciated. I do think that it is not getting the apk to the emulator but that is my speculation.

[35m[HTTP]e[39m e[37m–>e[39m e[37mPOSTe[39m e[37m/wd/hub/sessione[39m
e[35m[HTTP]e[39m e[90m{“desiredCapabilities”:{“app”:"/users/vagrant/deploy/app-release.apk",“buildToolsVersion”:“29.0.3”,“deviceName”:“PixelXL”,“avd”:“emulator”,“androidInstallTimeout”:90000,“avdLaunchTimeout”:60000,“adbExecTimeout”:180000,“automationName”:“UiAutomator2”,“skipServerInstallation”:“true”,“platformName”:“Android”,“udid”:“emulator-5554”,“ignoreHiddenApiPolicyError”:“true”},“capabilities”:{“firstMatch”:[{“appium:adbExecTimeout”:180000,“appium:androidInstallTimeout”:90000,“appium:app”:"/users/vagrant/deploy/app-release.apk",“appium:automationName”:“UiAutomator2”,“appium:avd”:“emulator”,“appium:avdLaunchTimeout”:60000,“buildToolsVersion”:“29.0.3”,“appium:deviceName”:“PixelXL”,“ignoreHiddenApiPolicyError”:“true”,“platformName”:“android”,“skipServerInstallation”:“true”,“appium:udid”:“emulator-5554”}]}}e[39m
[debug] e[35m[W3C]e[39m Calling AppiumDriver.createSession() with args: [{“app”:"/users/vagrant/deploy/app-release.apk",“buildToolsVersion”:“29.0.3”,“deviceName”:“PixelXL”,“avd”:“emulator”,“androidInstallTimeout”:90000,“avdLaunchTimeout”:60000,“adbExecTimeout”:180000,“automationName”:“UiAutomator2”,“skipServerInstallation”:“true”,“platformName”:“Android”,“udid”:“emulator-5554”,“ignoreHiddenApiPolicyError”:“true”},null,{“firstMatch”:[{“appium:adbExecTimeout”:180000,“appium:androidInstallTimeout”:90000,“appium:app”:"/users/vagrant/deploy/app-release.apk",“appium:automationName”:“UiAutomator2”,“appium:avd”:“emulator”,“appium:avdLaunchTimeout”:60000,“buildToolsVersion”:“29.0.3”,“appium:deviceName”:“PixelXL”,“ignoreHiddenApiPolicyError”:“true”,“platformName”:“android”,“skipServerInstallation”:“true”,“appium:udid”:“emulator-5554”}]}]
[debug] e[35m[BaseDriver]e[39m Event ‘newSessionRequested’ logged at 1614211779365 (00:09:39 GMT+0000 (Coordinated Universal Time))
e[35m[BaseDriver]e[39m The following capabilities are not standard capabilities and should have an extension prefix:
e[35m[BaseDriver]e[39m buildToolsVersion
e[35m[BaseDriver]e[39m ignoreHiddenApiPolicyError
e[35m[BaseDriver]e[39m skipServerInstallation
e[35m[Appium]e[39m Appium v1.20.2 creating new AndroidUiautomator2Driver (v1.61.2) session
[debug] e[35m[BaseDriver]e[39m W3C capabilities and MJSONWP desired capabilities were provided
[debug] e[35m[BaseDriver]e[39m Creating session with W3C capabilities: {
[debug] e[35m[BaseDriver]e[39m “alwaysMatch”: {
[debug] e[35m[BaseDriver]e[39m “appium:buildToolsVersion”: “29.0.3”,
[debug] e[35m[BaseDriver]e[39m “appium:ignoreHiddenApiPolicyError”: “true”,
[debug] e[35m[BaseDriver]e[39m “platformName”: “android”,
[debug] e[35m[BaseDriver]e[39m “appium:skipServerInstallation”: “true”,
[debug] e[35m[BaseDriver]e[39m “appium:adbExecTimeout”: 180000,
[debug] e[35m[BaseDriver]e[39m “appium:androidInstallTimeout”: 90000,
[debug] e[35m[BaseDriver]e[39m “appium:app”: “/users/vagrant/deploy/app-release.apk”,
[debug] e[35m[BaseDriver]e[39m “appium:automationName”: “UiAutomator2”,
[debug] e[35m[BaseDriver]e[39m “appium:avd”: “emulator”,
[debug] e[35m[BaseDriver]e[39m “appium:avdLaunchTimeout”: 60000,
[debug] e[35m[BaseDriver]e[39m “appium:deviceName”: “PixelXL”,
[debug] e[35m[BaseDriver]e[39m “appium:udid”: “emulator-5554”
[debug] e[35m[BaseDriver]e[39m },
[debug] e[35m[BaseDriver]e[39m “firstMatch”: [
[debug] e[35m[BaseDriver]e[39m {}
[debug] e[35m[BaseDriver]e[39m ]
[debug] e[35m[BaseDriver]e[39m }
e[35m[BaseDriver]e[39m Capability ‘skipServerInstallation’ changed from string to boolean. This may cause unexpected behavior
e[35m[BaseDriver]e[39m Capability ‘ignoreHiddenApiPolicyError’ changed from string to boolean. This may cause unexpected behavior
e[35m[BaseDriver]e[39m Session created with session id: a59c5be2-d4b9-4f1e-9c5b-88a9e6f59ea6
e[35m[BaseDriver]e[39m Using local app ‘/users/vagrant/deploy/app-release.apk’
[debug] e[35m[UiAutomator2]e[39m Checking whether app is actually present
e[35m[ADB]e[39m Found 22 ‘build-tools’ folders under ‘/usr/local/share/android-sdk’ (newest first):
e[35m[ADB]e[39m /usr/local/share/android-sdk/build-tools/30.0.0
e[35m[ADB]e[39m /usr/local/share/android-sdk/build-tools/29.0.3
e[35m[ADB]e[39m /usr/local/share/android-sdk/build-tools/29.0.2
e[35m[ADB]e[39m /usr/local/share/android-sdk/build-tools/29.0.1
e[35m[ADB]e[39m /usr/local/share/android-sdk/build-tools/29.0.0
e[35m[ADB]e[39m /usr/local/share/android-sdk/build-tools/28.0.3
e[35m[ADB]e[39m /usr/local/share/android-sdk/build-tools/28.0.2
e[35m[ADB]e[39m /usr/local/share/android-sdk/build-tools/28.0.1
e[35m[ADB]e[39m /usr/local/share/android-sdk/build-tools/28.0.0
e[35m[ADB]e[39m /usr/local/share/android-sdk/build-tools/27.0.3
e[35m[ADB]e[39m /usr/local/share/android-sdk/build-tools/27.0.2
e[35m[ADB]e[39m /usr/local/share/android-sdk/build-tools/27.0.1
e[35m[ADB]e[39m /usr/local/share/android-sdk/build-tools/27.0.0
e[35m[ADB]e[39m /usr/local/share/android-sdk/build-tools/26.0.2
e[35m[ADB]e[39m /usr/local/share/android-sdk/build-tools/26.0.1
e[35m[ADB]e[39m /usr/local/share/android-sdk/build-tools/25.0.3
e[35m[ADB]e[39m /usr/local/share/android-sdk/build-tools/24.0.3
e[35m[ADB]e[39m /usr/local/share/android-sdk/build-tools/23.0.3
e[35m[ADB]e[39m /usr/local/share/android-sdk/build-tools/22.0.1
e[35m[ADB]e[39m /usr/local/share/android-sdk/build-tools/21.1.2
e[35m[ADB]e[39m /usr/local/share/android-sdk/build-tools/19.1.0
e[35m[ADB]e[39m /usr/local/share/android-sdk/build-tools/17.0.0
e[35m[ADB]e[39m Using build tools at ‘/usr/local/share/android-sdk/build-tools/29.0.3’
e[35m[ADB]e[39m Using ‘adb’ from ‘/usr/local/share/android-sdk/platform-tools/adb’
[debug] e[35m[ADB]e[39m Running ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 start-server’
[debug] e[35m[ADB]e[39m Trying to find ‘emulator’ emulator
[debug] e[35m[ADB]e[39m Getting connected emulators
[debug] e[35m[ADB]e[39m Getting connected devices
[debug] e[35m[ADB]e[39m Connected devices: [{“udid”:“emulator-5554”,“state”:“device”}]
[debug] e[35m[ADB]e[39m 1 emulator connected
[debug] e[35m[ADB]e[39m Overriding /Users/vagrant/.emulator_console_auth_token with an empty string to avoid telnet authentication for emulator commands
[debug] e[35m[ADB]e[39m Executing Emulator console command: avd name
[debug] e[35m[ADB]e[39m Found emulator ‘emulator’ on port 5554
[debug] e[35m[ADB]e[39m Setting device id to emulator-5554
[debug] e[35m[AndroidDriver]e[39m Not launching AVD because it is already running.
e[35m[AndroidDriver]e[39m Using device: emulator-5554
e[35m[ADB]e[39m Using build tools at ‘/usr/local/share/android-sdk/build-tools/29.0.3’
e[35m[ADB]e[39m Using ‘adb’ from ‘/usr/local/share/android-sdk/platform-tools/adb’
[debug] e[35m[ADB]e[39m Running ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 start-server’
[debug] e[35m[ADB]e[39m Setting device id to emulator-5554
[debug] e[35m[ADB]e[39m Running ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 shell getprop ro.build.version.sdk’
[debug] e[35m[ADB]e[39m Current device property ‘ro.build.version.sdk’: 29
e[35m[ADB]e[39m Getting device platform version
[debug] e[35m[ADB]e[39m Running ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 shell getprop ro.build.version.release’
[debug] e[35m[ADB]e[39m Current device property ‘ro.build.version.release’: 10
[debug] e[35m[ADB]e[39m Device API level: 29
e[35m[UiAutomator2]e[39m Relaxing hidden api policy
[debug] e[35m[ADB]e[39m Running ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 shell ‘settings put global hidden_api_policy_pre_p_apps 1;settings put global hidden_api_policy_p_apps 1;settings put global hidden_api_policy 1’’
[debug] e[35m[AndroidDriver]e[39m Parsing package and activity from app manifest
e[35m[ADB]e[39m Package name: ‘com.risegardens.care’
e[35m[ADB]e[39m Main activity name: ‘com.risegardens.care.MainActivity’
[debug] e[35m[AndroidDriver]e[39m Parsed package and activity are: com.risegardens.care/com.risegardens.care.MainActivity
[debug] e[35m[ADB]e[39m Running ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 wait-for-device’
[debug] e[35m[ADB]e[39m Running ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 shell echo ping’
[debug] e[35m[AndroidDriver]e[39m Pushing settings apk to device…
[debug] e[35m[ADB]e[39m Getting install status for io.appium.settings
[debug] e[35m[ADB]e[39m Running ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys package io.appium.settings’
[debug] e[35m[ADB]e[39m ‘io.appium.settings’ is not installed
[debug] e[35m[ADB]e[39m App ‘/usr/local/lib/node_modules/appium/node_modules/io.appium.settings/apks/settings_apk-debug.apk’ is not installed
[debug] e[35m[ADB]e[39m Installing ‘/usr/local/lib/node_modules/appium/node_modules/io.appium.settings/apks/settings_apk-debug.apk’
[debug] e[35m[ADB]e[39m Running ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 help’
[debug] e[35m[ADB]e[39m Running ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 features’
e[35m[ADB]e[39m The application at ‘/usr/local/lib/node_modules/appium/node_modules/io.appium.settings/apks/settings_apk-debug.apk’ will not be cached, because the device under test has confirmed the support of streamed installs
[debug] e[35m[ADB]e[39m Running ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 install -g /usr/local/lib/node_modules/appium/node_modules/io.appium.settings/apks/settings_apk-debug.apk’
e[35m[ADB]e[39m The installation of ‘settings_apk-debug.apk’ took 10830ms
[debug] e[35m[ADB]e[39m Install command stdout: Performing Streamed Install
[debug] e[35m[ADB]e[39m Success
[debug] e[35m[ADB]e[39m Getting IDs of all ‘io.appium.settings’ processes
[debug] e[35m[ADB]e[39m Running ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 shell ‘pgrep --help; echo $?’’
[debug] e[35m[ADB]e[39m Running ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 shell pgrep -f ([[:blank:]]|^)io.appium.settings([[:blank:]]|$)’
[debug] e[35m[ADB]e[39m Getting IDs of all ‘io.appium.settings’ processes
[debug] e[35m[ADB]e[39m Running ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 shell pgrep -f ([[:blank:]]|^)io.appium.settings([[:blank:]]|$)’
[debug] e[35m[ADB]e[39m Starting Appium Settings app
[debug] e[35m[ADB]e[39m Running ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 shell am start -n io.appium.settings/.Settings -a android.intent.action.MAIN -c android.intent.category.LAUNCHER’
[debug] e[35m[ADB]e[39m Getting IDs of all ‘io.appium.settings’ processes
[debug] e[35m[ADB]e[39m Running ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 shell pgrep -f ([[:blank:]]|^)io.appium.settings([[:blank:]]|$)’
[debug] e[35m[ADB]e[39m Getting IDs of all ‘io.appium.settings’ processes
[debug] e[35m[ADB]e[39m Running ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 shell pgrep -f ([[:blank:]]|^)io.appium.settings([[:blank:]]|$)’
[debug] e[35m[ADB]e[39m Getting IDs of all ‘io.appium.settings’ processes
[debug] e[35m[ADB]e[39m Running ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 shell pgrep -f ([[:blank:]]|^)io.appium.settings([[:blank:]]|$)’
[debug] e[35m[Logcat]e[39m Starting logs capture with command: /usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 logcat -v threadtime
[debug] e[35m[UiAutomator2]e[39m Forwarding UiAutomator2 Server port 6790 to local port 8200
[debug] e[35m[ADB]e[39m Forwarding system: 8200 to device: 6790
[debug] e[35m[ADB]e[39m Running ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 forward tcp:8200 tcp:6790’
e[35m[UiAutomator2]e[39m ‘skipServerInstallation’ is set. Skipping UIAutomator2 server installation.
[debug] e[35m[ADB]e[39m Checking app cert for /users/vagrant/deploy/app-release.apk
e[35m[ADB]e[39m Using build tools at ‘/usr/local/share/android-sdk/build-tools/29.0.3’
e[35m[ADB]e[39m Using ‘apksigner.jar’ from ‘/usr/local/share/android-sdk/build-tools/29.0.3/lib/apksigner.jar’
[debug] e[35m[ADB]e[39m Starting apksigner: /Users/vagrant/.jenv/versions/1.8/bin/java -Xmx1024M -Xss1m -jar /usr/local/share/android-sdk/build-tools/29.0.3/lib/apksigner.jar verify --print-certs /users/vagrant/deploy/app-release.apk
[debug] e[35m[ADB]e[39m apksigner stdout: Signer #1 certificate DN: CN=Android Debug, OU=Android, O=Unknown, L=Unknown, ST=Unknown, C=US
[debug] e[35m[ADB]e[39m Signer #1 certificate SHA-256 digest: fac61745dc0903786fb9ede62a962b399f7348f0bb6f899b8332667591033b9c
[debug] e[35m[ADB]e[39m Signer #1 certificate SHA-1 digest: 5e8f16062ea3cd2c4a0d547876baa6f38cabf625
[debug] e[35m[ADB]e[39m Signer #1 certificate MD5 digest: 20f46148b72d8e5e5ca23d37a4f41490
[debug] e[35m[ADB]e[39m
e[35m[ADB]e[39m ‘/users/vagrant/deploy/app-release.apk’ is signed with a non-default certificate
[debug] e[35m[ADB]e[39m Getting install status for com.risegardens.care
[debug] e[35m[ADB]e[39m Running ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys package com.risegardens.care’
[debug] e[35m[ADB]e[39m ‘com.risegardens.care’ is not installed
[debug] e[35m[ADB]e[39m App ‘/users/vagrant/deploy/app-release.apk’ is not installed
[debug] e[35m[ADB]e[39m Installing ‘/users/vagrant/deploy/app-release.apk’
e[35m[ADB]e[39m The application at ‘/users/vagrant/deploy/app-release.apk’ will not be cached, because the device under test has confirmed the support of streamed installs
[debug] e[35m[ADB]e[39m Running ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 install /users/vagrant/deploy/app-release.apk’
[debug] e[35m[UiAutomator2]e[39m Deleting UiAutomator2 session
[debug] e[35m[UiAutomator2]e[39m Deleting UiAutomator2 server session
[debug] e[35m[WD Proxy]e[39m Matched ‘/’ to command name ‘deleteSession’
e[35m[UiAutomator2]e[39m Did not get confirmation UiAutomator2 deleteSession worked; Error was: UnknownError: An unknown server-side error occurred while processing the command. Original error: Trying to proxy a session command without session id
[debug] e[35m[ADB]e[39m Running ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 shell am force-stop com.risegardens.care’
[debug] e[35m[Logcat]e[39m Stopping logcat capture
[debug] e[35m[ADB]e[39m Removing forwarded port socket connection: 8200
[debug] e[35m[ADB]e[39m Running ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 forward --remove tcp:8200’
e[35m[UiAutomator2]e[39m Restoring hidden api policy to the device default configuration
[debug] e[35m[ADB]e[39m Running ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 shell ‘settings delete global hidden_api_policy_pre_p_apps;settings delete global hidden_api_policy_p_apps;settings delete global hidden_api_policy’’
[debug] e[35m[BaseDriver]e[39m Event ‘newSessionStarted’ logged at 1614211902160 (00:11:42 GMT+0000 (Coordinated Universal Time))
[debug] e[35m[W3C]e[39m Encountered internal error running command: Error executing adbExec. Original error: ‘Command ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 install /users/vagrant/deploy/app-release.apk’ timed out after 90000ms’. Try to increase the 90000ms adb execution timeout represented by ‘androidInstallTimeout’ capability
[debug] e[35m[W3C]e[39m Error: Command ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 install /users/vagrant/deploy/app-release.apk’ timed out after 90000ms
[debug] e[35m[W3C]e[39m at Timeout._onTimeout (/usr/local/lib/node_modules/appium/node_modules/teen_process/lib/exec.js:125:19)
[debug] e[35m[W3C]e[39m at listOnTimeout (internal/timers.js:549:17)
[debug] e[35m[W3C]e[39m at processTimers (internal/timers.js:492:7)
e[35m[HTTP]e[39m e[37m<-- POST /wd/hub/session e[39me[31m500e[39m e[90m122884 ms - 1089e[39m
e[35m[HTTP]e[39m e[90me[39m
[ERROR] Tests run: 25, Failures: 1, Errors: 0, Skipped: 24, Time elapsed: 128.894 s <<< FAILURE! - in TestSuite
[ERROR] testui.AppStartUpFlow.setupClass Time elapsed: 127.908 s <<< FAILURE!
org.openqa.selenium.SessionNotCreatedException:
Unable to create a new remote session. Please check the server log for more details. Original error: An unknown server-side error occurred while processing the command. Original error: Error executing adbExec. Original error: ‘Command ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 install /users/vagrant/deploy/app-release.apk’ timed out after 90000ms’. Try to increase the 90000ms adb execution timeout represented by ‘androidInstallTimeout’ capability
Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:17:03’
System info: host: ‘prd-veg-std-g-xcode-11-7-210224232433-jSpurj5RHcADMFBS4NLKLf.local’, ip: ‘fe80:0:0:0:1cec:30fc:6de7:34ba%en0’, os.name: ‘Mac OS X’, os.arch: ‘x86_64’, os.version: ‘10.15.5’, java.version: ‘1.8.0_282’
Driver info: driver.version: AndroidDriver
remote stacktrace: UnknownError: An unknown server-side error occurred while processing the command. Original error: Error executing adbExec. Original error: ‘Command ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 install /users/vagrant/deploy/app-release.apk’ timed out after 90000ms’. Try to increase the 90000ms adb execution timeout represented by ‘androidInstallTimeout’ capability
at getResponseForW3CError (/usr/local/lib/node_modules/appium/node_modules/appium-base-driver/lib/protocol/errors.js:804:9)
at asyncHandler (/usr/local/lib/node_modules/appium/node_modules/appium-base-driver/lib/protocol/protocol.js:380:37)
Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:17:03’
System info: host: ‘prd-veg-std-g-xcode-11-7-210224232433-jSpurj5RHcADMFBS4NLKLf.local’, ip: ‘fe80:0:0:0:1cec:30fc:6de7:34ba%en0’, os.name: ‘Mac OS X’, os.arch: ‘x86_64’, os.version: ‘10.15.5’, java.version: ‘1.8.0_282’
Driver info: driver.version: AndroidDriver
at testui.AppStartUpFlow.setupClass(AppStartUpFlow.java:21)
Caused by: java.lang.reflect.InvocationTargetException
at testui.AppStartUpFlow.setupClass(AppStartUpFlow.java:21)
Caused by: org.openqa.selenium.WebDriverException:
An unknown server-side error occurred while processing the command. Original error: Error executing adbExec. Original error: ‘Command ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 install /users/vagrant/deploy/app-release.apk’ timed out after 90000ms’. Try to increase the 90000ms adb execution timeout represented by ‘androidInstallTimeout’ capability
Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:17:03’
System info: host: ‘prd-veg-std-g-xcode-11-7-210224232433-jSpurj5RHcADMFBS4NLKLf.local’, ip: ‘fe80:0:0:0:1cec:30fc:6de7:34ba%en0’, os.name: ‘Mac OS X’, os.arch: ‘x86_64’, os.version: ‘10.15.5’, java.version: ‘1.8.0_282’
Driver info: driver.version: AndroidDriver
remote stacktrace: UnknownError: An unknown server-side error occurred while processing the command. Original error: Error executing adbExec. Original error: ‘Command ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 install /users/vagrant/deploy/app-release.apk’ timed out after 90000ms’. Try to increase the 90000ms adb execution timeout represented by ‘androidInstallTimeout’ capability
at getResponseForW3CError (/usr/local/lib/node_modules/appium/node_modules/appium-base-driver/lib/protocol/errors.js:804:9)
at asyncHandler (/usr/local/lib/node_modules/appium/node_modules/appium-base-driver/lib/protocol/protocol.js:380:37)
at testui.AppStartUpFlow.setupClass(AppStartUpFlow.java:21)

[debug] e[35m[W3C]e[39m Encountered internal error running command: Error executing adbExec. Original error: ‘Command ‘/usr/local/share/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 install /users/vagrant/deploy/app-release.apk’ timed out after 90000ms’. Try to increase the 90000ms adb execution timeout represented by ‘androidInstallTimeout’ capability

Did you try to increase this timeout?

Yes. I have caps.setCapability("androidInstallTimeout", 180000); set already. I increased the time from 90000ms to give it more time as well.

Perhaps the CI there is really slow and needs even more time. I would try to test this command manually if it was a local machine. Although, it makes sense to create a support ticket if this is happening in a cloud.