Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: Cannot start the 'com.syscocorp.mss.enterprise.qa' application #11714

Closed
jayanathkarunarathna opened this issue Nov 21, 2018 · 14 comments
Closed
Labels
Android related to Android-native driver(s) Needs Info typically non-actionable; needs author to respond

Comments

@jayanathkarunarathna
Copy link

jayanathkarunarathna commented Nov 21, 2018

The problem

When I start my application using Appium above error comes. Sometimes opening the app and inspect elements get success but couldn't identify the exact way to resolve.

Environment

  • Appium version 1.9.1
  • Desktop OS/version used to run Appium: Mac High Sierra
  • Mobile platform/version under test: Android 8.1.0
  • Real device or emulator/simulator: Xiaomi MI A2 / SGS 8
  • Appium CLI or Appium.app|exe: 1.8.2

Details

I am trying to run my automation in an android device. For the device I used (MOTO G android 6.0.0), automation was running without any issue. But when I try the same code in a new device, I end up with the given error. I have attached logs I got when I try to open the app using Appium desktop for convenience. (Got the same error when executing automation )

Link to Appium logs

Log when the issue occurred
https://gist.github.com/jayanathkarunarathna/2341d01479643aa83d8dcad02823bc99

Log when success
https://gist.github.com/jayanathkarunarathna/042cc6c950b044ecce0ac3c712fccfe6

Desired Capabilities

{
"app": "/Users/jayanath/Downloads/app-prod-release.apk",
"platformName": "android",
"deviceName": "24d47e4",
"platformVersion": "8.1.0",
"automationName": "UiAutomator2"
}

@imurchie
Copy link
Contributor

Try increasing the timeout by setting the desired capability adbExecTimeout to something larger than 20000 (which is the default).

@mykola-mokhnach mykola-mokhnach changed the title [debug] [MJSONWP] Encountered internal error running command: Error: Cannot start the 'com.syscocorp.mss.enterprise.qa' application. Visit https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/android/activity-startup.md for troubleshooting. Original error: Error executing adbExec. Original error: 'Command '/Users/jayanath/Library/Android/sdk/platform-tools/adb -P 5037 -s 24d47e4 shell am start -W -n com.syscocorp.mss.enterprise.qa/host.exp.exponent.MainActivity -S' timed out after 20000ms'; Stderr: ''; Code: 'null' Error: Cannot start the 'com.syscocorp.mss.enterprise.qa' application Nov 21, 2018
@mykola-mokhnach
Copy link
Collaborator

Did you try to visit the link mentioned in the error message?

@mykola-mokhnach mykola-mokhnach added the Needs Info typically non-actionable; needs author to respond label Nov 21, 2018
@jayanathkarunarathna
Copy link
Author

Try increasing the timeout by setting the desired capability adbExecTimeout to something larger than 20000 (which is the default).

{
"appPackage": "com.syscocorp.mss.enterprise.qa",
"appActivity": "host.exp.exponent.MainActivity",
"platformName": "android",
"deviceName": "24d47e4",
"platformVersion": "8.1.0",
"automationName": "UiAutomator2",
"adbExecTimeout": 40000
}

Tried increasing to 40000 with adbExecTimeout capability. But Still same error comes with same timeout
[MJSONWP] Encountered internal error running command: Error: Cannot start the 'com.syscocorp.mss.enterprise.qa' application. Visit https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/android/activity-startup.md for troubleshooting. Original error: Error executing adbExec. Original error: 'Command '/Users/jayanath/Library/Android/sdk/platform-tools/adb -P 5037 -s 24d47e4 shell am start -W -n com.syscocorp.mss.enterprise.qa/host.exp.exponent.MainActivity -S' timed out after 20000ms'; Stderr: ''; Code: 'null'

Seems adbExecTimeout capability is not applying.

@jayanathkarunarathna
Copy link
Author

Did you try to visit the link mentioned in the error message?

Yes. Set capabilities by following that link.

@imurchie
Copy link
Contributor

Hmm. Perhaps that capability is only available in the latest pre-release beta. It doesn't seem to have taken effect in your logs.

@mykola-mokhnach
Copy link
Collaborator

Did you try to increase appWaitDuration?

@jayanathkarunarathna
Copy link
Author

Did you try to increase appWaitDuration?

Yes. Result is the same.

@mykola-mokhnach
Copy link
Collaborator

Then I second @imurchie - try appium@beta

@mykola-mokhnach
Copy link
Collaborator

mykola-mokhnach commented Nov 22, 2018

btw, how the device does behave if the same command is executed manually from the terminal?

@mykola-mokhnach mykola-mokhnach added the Android related to Android-native driver(s) label Nov 22, 2018
@jayanathkarunarathna
Copy link
Author

Sorry for the late reply as I did not get a chance to try above solution. Moving to appium beta and increasing adbExecTimeout did not solve the problem. Still getting the same error.

JayanathSyscoLabs:~ jayanath$ appium -p 4732
[Appium] Welcome to Appium v1.10.0-beta.6
[Appium] Non-default server args:
[Appium] port: 4732
[Appium] Appium REST http interface listener started on 0.0.0.0:4732
[HTTP] --> GET /wd/hub/status
[HTTP] {}
[debug] [GENERIC] Calling AppiumDriver.getStatus() with args: []
[debug] [GENERIC] Responding to client with driver.getStatus() result: {"build":{"version":"1.10.0-beta.6"}}
[HTTP] <-- GET /wd/hub/status 200 10 ms - 75
[HTTP]
[HTTP] --> POST /wd/hub/session
[HTTP] {"capabilities":{"desiredCapabilities":{"appPackage":"com.syscocorp.mss.enterprise.stag","appActivity":"host.exp.exponent.MainActivity","noReset":true,"platformVersion":"8.1.0","adbExecTimeout":120000,"automationName":"UiAutomator2","platformName":"Android","deviceName":"24d47e4"},"requiredCapabilities":{}},"desiredCapabilities":{"appPackage":"com.syscocorp.mss.enterprise.stag","appActivity":"host.exp.exponent.MainActivity","noReset":true,"platformVersion":"8.1.0","adbExecTimeout":120000,"automationName":"UiAutomator2","platformName":"Android","deviceName":"24d47e4"},"requiredCapabilities":{}}
[debug] [W3C] Calling AppiumDriver.createSession() with args: [{"appPackage":"com.syscocorp.mss.enterprise.stag","appActivity":"host.exp.exponent.MainActivity","noReset":true,"platformVersion":"8.1.0","adbExecTimeout":120000,"automationName":"UiAutomator2","platformName":"Android","deviceName":"24d47e4"},{},{"desiredCapabilities":{"appPackage":"com.syscocorp.mss.enterprise.stag","appActivity":"host.exp.exponent.MainActivity","noReset":true,"platformVersion":"8.1.0","adbExecTimeout":120000,"automationName":"UiAutomator2","platformName":"Android","deviceName":"24d47e4"},"requiredCapabilities":{}}]
[debug] [BaseDriver] Event 'newSessionRequested' logged at 1543298275388 (11:27:55 GMT+0530 (+0530))
[Appium] Creating new AndroidUiautomator2Driver (v1.24.0) session
[Appium] Capabilities:
[Appium] appPackage: com.syscocorp.mss.enterprise.stag
[Appium] appActivity: host.exp.exponent.MainActivity
[Appium] noReset: true
[Appium] platformVersion: 8.1.0
[Appium] adbExecTimeout: 120000
[Appium] automationName: UiAutomator2
[Appium] platformName: Android
[Appium] deviceName: 24d47e4
[debug] [BaseDriver] Creating session with MJSONWP desired capabilities: {"appPackage":"com.syscocor...
[BaseDriver] Session created with session id: 1590994c-bd3f-4f2e-bb68-ae8eeaa4a956
[AndroidDriver] Java version is: 1.8.0_144
[ADB] Checking whether adb is present
[ADB] Found 2 'build-tools' folders under '/Users/jayanath/Library/Android/sdk' (newest first):
[ADB] /Users/jayanath/Library/Android/sdk/build-tools/26.0.2
[ADB] /Users/jayanath/Library/Android/sdk/build-tools/26.0.1
[ADB] Using adb from /Users/jayanath/Library/Android/sdk/platform-tools/adb
[AndroidDriver] Retrieving device list
[debug] [ADB] Trying to find a connected android device
[debug] [ADB] Getting connected devices...
[debug] [ADB] 1 device(s) connected
[AndroidDriver] Looking for a device with Android '8.1.0'
[debug] [ADB] Setting device id to 24d47e4
[ADB] Getting device platform version
[debug] [ADB] Running '/Users/jayanath/Library/Android/sdk/platform-tools/adb -P 5037 -s 24d47e4 shell getprop ro.build.version.release'
[debug] [ADB] Current device property 'ro.build.version.release': 8.1.0
[AndroidDriver] Using device: 24d47e4
[debug] [ADB] Setting device id to 24d47e4
[debug] [ADB] Running '/Users/jayanath/Library/Android/sdk/platform-tools/adb -P 5037 -s 24d47e4 shell getprop ro.build.version.sdk'
[debug] [ADB] Current device property 'ro.build.version.sdk': 27
[debug] [ADB] Device API level: 27
[AndroidDriver] No app sent in, not parsing package/activity
[debug] [ADB] Getting all processes with uiautomator
[debug] [ADB] Running '/Users/jayanath/Library/Android/sdk/platform-tools/adb -P 5037 -s 24d47e4 shell ps'
[debug] [ADB] Running '/Users/jayanath/Library/Android/sdk/platform-tools/adb -P 5037 -s 24d47e4 shell am force-stop io.appium.uiautomator2.server'
[debug] [ADB] Checking app cert for /usr/local/lib/node_modules/appium/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-v2.7.0.apk
[ADB] Using apksigner from /Users/jayanath/Library/Android/sdk/build-tools/26.0.2/apksigner
[debug] [ADB] Starting '/Users/jayanath/Library/Android/sdk/build-tools/26.0.2/apksigner' with args '["verify","--print-certs","/usr/local/lib/node_modules/appium/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-v2.7.0.apk"]'
[debug] [ADB] apksigner stdout: Signer #1 certificate DN: EMAILADDRESS=android@android.com, CN=Android, OU=Android, O=Android, L=Mountain View, ST=California, C=US
[debug] [ADB] Signer #1 certificate SHA-256 digest: a40da80a59d170caa950cf15c18c454d47a39b26989d8b640ecd745ba71bf5dc
[debug] [ADB] Signer #1 certificate SHA-1 digest: 61ed377e85d386a8dfee6b864bd85b0bfaa5af81
[debug] [ADB] Signer #1 certificate MD5 digest: e89b158e4bcf988ebd09eb83f5378e87
[debug] [ADB]
[debug] [ADB] '/usr/local/lib/node_modules/appium/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-v2.7.0.apk' is already signed.
[debug] [ADB] Checking app cert for /usr/local/lib/node_modules/appium/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-debug-androidTest.apk
[debug] [ADB] Starting '/Users/jayanath/Library/Android/sdk/build-tools/26.0.2/apksigner' with args '["verify","--print-certs","/usr/local/lib/node_modules/appium/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-debug-androidTest.apk"]'
[debug] [ADB] apksigner stdout: Signer #1 certificate DN: EMAILADDRESS=android@android.com, CN=Android, OU=Android, O=Android, L=Mountain View, ST=California, C=US
[debug] [ADB] Signer #1 certificate SHA-256 digest: a40da80a59d170caa950cf15c18c454d47a39b26989d8b640ecd745ba71bf5dc
[debug] [ADB] Signer #1 certificate SHA-1 digest: 61ed377e85d386a8dfee6b864bd85b0bfaa5af81
[debug] [ADB] Signer #1 certificate MD5 digest: e89b158e4bcf988ebd09eb83f5378e87
[debug] [ADB]
[debug] [ADB] '/usr/local/lib/node_modules/appium/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-debug-androidTest.apk' is already signed.
[debug] [ADB] Getting install status for io.appium.uiautomator2.server
[debug] [ADB] Running '/Users/jayanath/Library/Android/sdk/platform-tools/adb -P 5037 -s 24d47e4 shell dumpsys package io.appium.uiautomator2.server'
[debug] [ADB] 'io.appium.uiautomator2.server' is installed
[debug] [ADB] Getting package info for 'io.appium.uiautomator2.server'
[debug] [ADB] Running '/Users/jayanath/Library/Android/sdk/platform-tools/adb -P 5037 -s 24d47e4 shell dumpsys package io.appium.uiautomator2.server'
[ADB] Checking whether aapt is present
[ADB] Using aapt from /Users/jayanath/Library/Android/sdk/build-tools/26.0.2/aapt
[debug] [ADB] The installed 'io.appium.uiautomator2.server' package does not require upgrade ('2.7.0' >= '2.7.0')
[debug] [ADB] Getting install status for io.appium.uiautomator2.server.test
[debug] [ADB] Running '/Users/jayanath/Library/Android/sdk/platform-tools/adb -P 5037 -s 24d47e4 shell dumpsys package io.appium.uiautomator2.server.test'
[debug] [ADB] 'io.appium.uiautomator2.server.test' is installed
[debug] [ADB] Getting package info for 'io.appium.uiautomator2.server.test'
[debug] [ADB] Running '/Users/jayanath/Library/Android/sdk/platform-tools/adb -P 5037 -s 24d47e4 shell dumpsys package io.appium.uiautomator2.server.test'
[ADB] Cannot read version codes of '/usr/local/lib/node_modules/appium/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-debug-androidTest.apk' and/or 'io.appium.uiautomator2.server.test'
[ADB] Cannot read version names of '/usr/local/lib/node_modules/appium/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-debug-androidTest.apk' and/or 'io.appium.uiautomator2.server.test'. Assuming correct app version is already installed
[debug] [UiAutomator2] Waiting up to 20000ms for instrumentation 'io.appium.uiautomator2.server.test/android.support.test.runner.AndroidJUnitRunner' to be available
[debug] [ADB] Running '/Users/jayanath/Library/Android/sdk/platform-tools/adb -P 5037 -s 24d47e4 shell pm list instrumentation'
[debug] [UiAutomator2] Instrumentation 'io.appium.uiautomator2.server.test/android.support.test.runner.AndroidJUnitRunner' available
[debug] [ADB] Running '/Users/jayanath/Library/Android/sdk/platform-tools/adb -P 5037 -s 24d47e4 wait-for-device'
[debug] [ADB] Running '/Users/jayanath/Library/Android/sdk/platform-tools/adb -P 5037 -s 24d47e4 shell echo ping'
[debug] [AndroidDriver] Pushing settings apk to device...
[debug] [ADB] Getting install status for io.appium.settings
[debug] [ADB] Running '/Users/jayanath/Library/Android/sdk/platform-tools/adb -P 5037 -s 24d47e4 shell dumpsys package io.appium.settings'
[debug] [ADB] 'io.appium.settings' is installed
[debug] [ADB] Getting package info for 'io.appium.settings'
[debug] [ADB] Running '/Users/jayanath/Library/Android/sdk/platform-tools/adb -P 5037 -s 24d47e4 shell dumpsys package io.appium.settings'
[debug] [ADB] The installed 'io.appium.settings' package does not require upgrade ('2.10.0' >= '2.10.0')
[debug] [ADB] Running '/Users/jayanath/Library/Android/sdk/platform-tools/adb -P 5037 -s 24d47e4 shell ps'
[debug] [AndroidDriver] io.appium.settings is already running. There is no need to reset its permissions.
[debug] [ADB] Device API level: 27
[debug] [ADB] Running '/Users/jayanath/Library/Android/sdk/platform-tools/adb -P 5037 -s 24d47e4 shell appops set io.appium.settings android:mock_location allow'
[AndroidDriver] setDeviceLanguageCountry requires language or country.
[AndroidDriver] Got language: 'null' and country: 'null'
[debug] [Logcat] Starting logcat capture
[debug] [UiAutomator2] Forwarding UiAutomator2 Server port 6790 to 8200
[debug] [ADB] Forwarding system: 8200 to device: 6790
[debug] [ADB] Running '/Users/jayanath/Library/Android/sdk/platform-tools/adb -P 5037 -s 24d47e4 forward tcp:8200 tcp:6790'
[debug] [UiAutomator2] No app capability. Assuming it is already on the device
[debug] [ADB] Checking app cert for null
[debug] [ADB] 'null' does not exist
[debug] [ADB] Getting all processes with uiautomator
[debug] [ADB] Running '/Users/jayanath/Library/Android/sdk/platform-tools/adb -P 5037 -s 24d47e4 shell ps'
[debug] [ADB] Running '/Users/jayanath/Library/Android/sdk/platform-tools/adb -P 5037 -s 24d47e4 shell am force-stop io.appium.uiautomator2.server'
[UiAutomator2] Starting uiautomator2 server 2.7.0
[UiAutomator2] Using UIAutomator2 server from '/usr/local/lib/node_modules/appium/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-v2.7.0.apk' and test from '/usr/local/lib/node_modules/appium/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-debug-androidTest.apk'
[UiAutomator2] Running command: 'adb -s 24d47e4 shell am instrument -w io.appium.uiautomator2.server.test/android.support.test.runner.AndroidJUnitRunner'
[UiAutomator2] Waiting up to 20000ms for UiAutomator2 to be online...
[debug] [JSONWP Proxy] Matched '/status' to command name 'getStatus'
[debug] [JSONWP Proxy] Proxying [GET /status] to [GET http://localhost:8200/wd/hub/status] with no body
[JSONWP Proxy] Got an unexpected response: {"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"}
[debug] [JSONWP Proxy] Matched '/status' to command name 'getStatus'
[debug] [JSONWP Proxy] Proxying [GET /status] to [GET http://localhost:8200/wd/hub/status] with no body
[JSONWP Proxy] Got an unexpected response: {"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"}
[debug] [JSONWP Proxy] Matched '/status' to command name 'getStatus'
[debug] [JSONWP Proxy] Proxying [GET /status] to [GET http://localhost:8200/wd/hub/status] with no body
[JSONWP Proxy] Got an unexpected response: {"errno":"ECONNRESET","code":"ECONNRESET","syscall":"read"}
[debug] [JSONWP Proxy] Matched '/status' to command name 'getStatus'
[debug] [JSONWP Proxy] Proxying [GET /status] to [GET http://localhost:8200/wd/hub/status] with no body
[debug] [JSONWP Proxy] Got response with status 200: "{"sessionId":"SESSIONID","status":0,"value":"Status Invoked"}"
[debug] [JSONWP Proxy] Matched '/session' to command name 'createSession'
[debug] [JSONWP Proxy] Proxying [POST /session] to [POST http://localhost:8200/wd/hub/session] with body: {"desiredCapabilities":{"platform":"LINUX","webStorageEnabled":false,"takesScreenshot":true,"javascriptEnabled":true,"databaseEnabled":false,"networkConnectionEnabled":true,"locationContextEnabled":false,"warnings":{},"desired":{"appPackage":"com.syscocorp.mss.enterprise.stag","appActivity":"host.exp.exponent.MainActivity","noReset":true,"platformVersion":"8.1.0","adbExecTimeout":120000,"automationName":"UiAutomator2","platformName":"Android","deviceName":"24d47e4"},"appPackage":"com.syscocorp.mss.enterprise.stag","appActivity":"host.exp.exponent.MainActivity","noReset":true,"platformVersion":"8.1.0","adbExecTimeout":120000,"automationName":"UiAutomator2","platformName":"Android","deviceName":"24d47e4","deviceUDID":"24d47e4"}}
[debug] [JSONWP Proxy] Got response with status 200: {"sessionId":"1d562816-4ad5-4b38-af4b-f11f2d1fde39","status":0,"value":"Created Session"}
[debug] [JSONWP Proxy] Proxying [GET /appium/device/info] to [GET http://localhost:8200/wd/hub/session/1d562816-4ad5-4b38-af4b-f11f2d1fde39/appium/device/info] with no body
[debug] [JSONWP Proxy] Got response with status 200: "{"sessionId":"1d562816-4ad5-4b38-af4b-f11f2d1fde39","status":0,"value":{"androidId":"b9eae63e7f1de21f","manufacturer":"Xiaomi","model":"Mi A2","brand":"xiaomi","apiVersion":"27","platformVersion":"8.1.0","carrierName":"Mobitel","realDisplaySize":"1080x2160","displayDensity":408}}"
[debug] [ADB] Running '/Users/jayanath/Library/Android/sdk/platform-tools/adb -P 5037 -s 24d47e4 shell dumpsys window'
[AndroidDriver] Screen already unlocked, doing nothing
[UiAutomator2] UiAutomator2 did not start the activity we were waiting for, 'com.syscocorp.mss.enterprise.stag/host.exp.exponent.MainActivity'. Starting it ourselves
[debug] [ADB] Device API level: 27
[debug] [ADB] Running '/Users/jayanath/Library/Android/sdk/platform-tools/adb -P 5037 -s 24d47e4 shell am start -W -n com.syscocorp.mss.enterprise.stag/host.exp.exponent.MainActivity -S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000'
[debug] [ADB] Running '/Users/jayanath/Library/Android/sdk/platform-tools/adb -P 5037 -s 24d47e4 shell am start -W -n com.syscocorp.mss.enterprise.stag/host.exp.exponent.MainActivity -S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000'
[debug] [UiAutomator2] Deleting UiAutomator2 session
[debug] [UiAutomator2] Deleting UiAutomator2 server session
[debug] [JSONWP Proxy] Matched '/' to command name 'deleteSession'
[debug] [JSONWP Proxy] Proxying [DELETE /] to [DELETE http://localhost:8200/wd/hub/session/1d562816-4ad5-4b38-af4b-f11f2d1fde39] with no body
[debug] [JSONWP Proxy] Got response with status 200: "{"sessionId":"1d562816-4ad5-4b38-af4b-f11f2d1fde39","status":0,"value":"Session deleted"}"
[debug] [ADB] Running '/Users/jayanath/Library/Android/sdk/platform-tools/adb -P 5037 -s 24d47e4 shell am force-stop com.syscocorp.mss.enterprise.stag'
[debug] [Logcat] Stopping logcat capture
[debug] [ADB] Removing forwarded port socket connection: 8200
[debug] [ADB] Running '/Users/jayanath/Library/Android/sdk/platform-tools/adb -P 5037 -s 24d47e4 forward --remove tcp:8200'
[debug] [ADB] Device API level: 27
[debug] [BaseDriver] Event 'newSessionStarted' logged at 1543298521520 (11:32:01 GMT+0530 (+0530))
[debug] [MJSONWP] Encountered internal error running command: Error: Cannot start the 'com.syscocorp.mss.enterprise.stag' application. Visit https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/android/activity-startup.md for troubleshooting. Original error: Error executing adbExec. Original error: 'Command '/Users/jayanath/Library/Android/sdk/platform-tools/adb -P 5037 -s 24d47e4 shell am start -W -n com.syscocorp.mss.enterprise.stag/host.exp.exponent.MainActivity -S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000' timed out after 120000ms'; Stderr: ''; Code: 'null'
[debug] [MJSONWP] at ADB.apkUtilsMethods.startApp (/usr/local/lib/node_modules/appium/node_modules/appium-adb/lib/tools/apk-utils.js:137:11)
[debug] [MJSONWP] at

@jayanathkarunarathna
Copy link
Author

btw, how the device does behave if the same command is executed manually from the terminal?

When executing adb command from terminal, App was started in mobile device but no out put was returned to the terminal. Please refer to this video https://drive.google.com/file/d/1eM2RG29tZTf7gfqy0s6z5MpD90XI2RSy/view?usp=sharing

@mykola-mokhnach
Copy link
Collaborator

I think it is a problem with the application itself. It should return the control after this command is executed

@jayanathkarunarathna
Copy link
Author

jayanathkarunarathna commented Nov 27, 2018

I think it is a problem with the application itself. It should return the control after this command is executed

Thanks. I'll check with application developers and update.

@lock
Copy link

lock bot commented Nov 27, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Nov 27, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Android related to Android-native driver(s) Needs Info typically non-actionable; needs author to respond
Projects
None yet
Development

No branches or pull requests

3 participants