Getting error message as "Could not start a new session. Response code 500. Message: An unknown server-side error occurred while processing the command. Original error: Cannot start the 'riotinto.metal.provenance' application. Consider checking the driver's troubleshooting documentation" #17809

shubhambajad · 2022-11-21T11:11:17Z

shubhambajad
Nov 21, 2022

Hi,
Actually while executing an appium script getting below error.
So script opening an application and quickly getting close.

Could not start a new session. Response code 500. Message: An unknown server-side error occurred while processing the command. Original error: Cannot start the 'andoridapk' application. Consider checking the driver's troubleshooting documentation. Original error: 'crc64188153237d53579e.SplashActivity' or 'andoridapk.crc64188153237d53579e.SplashActivity' never started. Consider checking the driver's troubleshooting documentation.
Host info: host: 'INDELWL00102', ip: '192.168.112.1'
Build info: version: '4.6.0', revision: '79f1c02ae20'
System info: os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_341'
Driver info: io.appium.java_client.android.AndroidDriver
Command: [null, newSession {capabilities=[{appium:appium.appWaitActivity=crc64188153237d53579e.MainActivity, platformName=ANDROID, appium:deviceName=Nexus, appium:automationName=UIAutomator2, appium:app=C:\Users\shubham.bajad\eclipse-workspace\appiumtest\src\test\java\resources\andoridapk.apk}], desiredCapabilities=Capabilities {appium:app: C:\Users\shubham.bajad\ecli..., appium:appium.appWaitActivity: crc64188153237d53579e.MainA..., appium:automationName: UIAutomator2, appium:deviceName: ShubhamPhone9, platformName: ANDROID}}]
Capabilities {}
at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:146)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at io.appium.java_client.remote.AppiumProtocolHandshake.createSession(AppiumProtocolHandshake.java:126)
at io.appium.java_client.remote.AppiumProtocolHandshake.createSession(AppiumProtocolHandshake.java:102)
at io.appium.java_client.remote.AppiumCommandExecutor.createSession(AppiumCommandExecutor.java:155)
at io.appium.java_client.remote.AppiumCommandExecutor.execute(AppiumCommandExecutor.java:189)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:541)
at io.appium.java_client.AppiumDriver.startSession(AppiumDriver.java:229)
at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:157)
at io.appium.java_client.AppiumDriver.(AppiumDriver.java:80)
at io.appium.java_client.AppiumDriver.(AppiumDriver.java:92)
at io.appium.java_client.android.AndroidDriver.(AndroidDriver.java:117)
at appiumtest.appiumtest.RioFirstTest.AppiumTest(RioFirstTest.java:36)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:715)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
at org.testng.TestRunner.privateRun(TestRunner.java:767)
at org.testng.TestRunner.run(TestRunner.java:617)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:51)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:85)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1197)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1122)
at org.testng.TestNG.run(TestNG.java:1030)
at org.testng.remote.AbstractRemoteTestNG.run(AbstractRemoteTestNG.java:115)
at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:251)
at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:77)

jlipps · 2022-11-21T19:49:08Z

jlipps
Nov 21, 2022
Maintainer

Did you follow the instructions and read the driver troubleshooting information? Also it's impossible to tell what's going on without the Appium server log.

7 replies

shubhambajad Nov 22, 2022
Author

@KazuCocoa @jlipps

[Appium] Welcome to Appium v2.0.0-beta.46
[Appium] Attempting to load driver uiautomator2...
[debug] [Appium] Requiring driver at C:\Users\shubham.bajad.appium\node_modules\appium-uiautomator2-driver
[Appium] Attempting to load driver xcuitest...
[debug] [Appium] Requiring driver at C:\Users\shubham.bajad.appium\node_modules\appium-xcuitest-driver
[Appium] Attempting to load driver gecko...
[debug] [Appium] Requiring driver at C:\Users\shubham.bajad.appium\node_modules\appium-geckodriver
[Appium] Appium REST http interface listener started on 0.0.0.0:4723
[Appium] Available drivers:
[Appium] - uiautomator2@2.10.2 (automationName 'UiAutomator2')
[Appium] - xcuitest@4.12.2 (automationName 'XCUITest')
[Appium] - gecko@1.1.3 (automationName 'Gecko')
[Appium] No plugins have been installed. Use the "appium plugin" command to install the one(s) you want to use.
[HTTP] --> GET /status
[HTTP] {}
[debug] [AppiumDriver@fb8b] Calling AppiumDriver.getStatus() with args: []
[debug] [AppiumDriver@fb8b] Responding to client with driver.getStatus() result: {"build":{"version":"2.0.0-beta.46"}}
[HTTP] <-- GET /status 200 13 ms - 47
[HTTP]
[debug] [HTTP] Request idempotency key: 66003215-b1ee-4dc3-82d5-c6cc58eff2ae
[HTTP] --> POST /session
[HTTP] {"capabilities":{"firstMatch":[{}],"alwaysMatch":{"appium:app":"C:\Users\shubham.bajad\eclipse-workspace\appiumtest\src\test\java\resources\provenance_v2.3.8.apk","appium:appPackage":"provenance","appium:appWaitActivity":"SplashActivity","appium:appWaitDuration":"20000","appium:appWaitPackage":"20000","appium:automationName":"UiAutomator2","appium:deviceName":"ShubhamPhone9","platformName":"android"}}}
[debug] [AppiumDriver@fb8b] Calling AppiumDriver.createSession() with args: [null,null,{"firstMatch":[{}],"alwaysMatch":{"appium:app":"C:\Users\shubham.bajad\eclipse-workspace\appiumtest\src\test\java\resources\provenance_v2.3.8.apk","appium:appPackage":"provenance","appium:appWaitActivity":"SplashActivity","appium:appWaitDuration":"20000","appium:appWaitPackage":"20000","appium:automationName":"UiAutomator2","appium:deviceName":"ShubhamPhone9","platformName":"android"}}]
[debug] [AppiumDriver@fb8b] Event 'newSessionRequested' logged at 1669109765806 (15:06:05 GMT+0530 (India Standard Time))
[Appium] Attempting to find matching driver for automationName 'UiAutomator2' and platformName 'android'
[Appium] The 'uiautomator2' driver was installed and matched caps.
[Appium] Will require it at C:\Users\shubham.bajad.appium\node_modules\appium-uiautomator2-driver
[debug] [Appium] Requiring driver at C:\Users\shubham.bajad.appium\node_modules\appium-uiautomator2-driver
[AppiumDriver@fb8b] Appium v2.0.0-beta.46 creating new AndroidUiautomator2Driver (v2.10.2) session
[AppiumDriver@fb8b] Checking BaseDriver versions for Appium and AndroidUiautomator2Driver
[AppiumDriver@fb8b] Appium's BaseDriver version is 8.7.3
[AppiumDriver@fb8b] AndroidUiautomator2Driver's BaseDriver version is 8.7.3
[debug] [AndroidUiautomator2Driver@8809] Creating session with W3C capabilities: {
[debug] [AndroidUiautomator2Driver@8809] "alwaysMatch": {
[debug] [AndroidUiautomator2Driver@8809] "platformName": "android",
[debug] [AndroidUiautomator2Driver@8809] "appium:app": "C:\Users\shubham.bajad\eclipse-workspace\appiumtest\src\test\java\resources\provenance_v2.3.8.apk",
[debug] [AndroidUiautomator2Driver@8809] "appium:appPackage": "provenance",
[debug] [AndroidUiautomator2Driver@8809] "appium:appWaitActivity": "SplashActivity",
[debug] [AndroidUiautomator2Driver@8809] "appium:appWaitDuration": "20000",
[debug] [AndroidUiautomator2Driver@8809] "appium:appWaitPackage": "20000",
[debug] [AndroidUiautomator2Driver@8809] "appium:automationName": "UiAutomator2",
[debug] [AndroidUiautomator2Driver@8809] "appium:deviceName": "ShubhamPhone9"
[debug] [AndroidUiautomator2Driver@8809] },
[debug] [AndroidUiautomator2Driver@8809] "firstMatch": [
[debug] [AndroidUiautomator2Driver@8809] {}
[debug] [AndroidUiautomator2Driver@8809] ]
[debug] [AndroidUiautomator2Driver@8809] }
[BaseDriver] Number capability passed in as string. Functionality may be compromised.
[AndroidUiautomator2Driver@8809] Capability 'appWaitDuration' changed from string ('20000') to integer (20000). This may cause unexpected behavior
[AndroidUiautomator2Driver@8809 (b0af58ca)] Session created with session id: b0af58ca-c5e2-47b7-b843-cfe180a0184a
[BaseDriver] Using local app 'C:\Users\shubham.bajad\eclipse-workspace\appiumtest\src\test\java\resources\provenance_v2.3.8.apk'
[debug] [AndroidUiautomator2Driver@8809 (b0af58ca)] Checking whether app is actually present
[ADB] Found 2 'build-tools' folders under 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk' (newest first):
[ADB] C:/Users/shubham.bajad/AppData/Local/Android/Sdk/build-tools/33.0.0
[ADB] C:/Users/shubham.bajad/AppData/Local/Android/Sdk/build-tools/30.0.3
[ADB] Using 'adb.exe' from 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe'
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 start-server'
[AndroidDriver] Retrieving device list
[debug] [ADB] Trying to find a connected android device
[debug] [ADB] Getting connected devices
[debug] [ADB] Connected devices: [{"udid":"emulator-5554","state":"device"}]
[AndroidDriver] Using device: emulator-5554
[ADB] Using 'adb.exe' from 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe'
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 start-server'
[debug] [ADB] Setting device id to emulator-5554
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell getprop ro.build.version.sdk'
[debug] [ADB] Current device property 'ro.build.version.sdk': 28
[ADB] Getting device platform version
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell getprop ro.build.version.release'
[debug] [ADB] Current device property 'ro.build.version.release': 9
[debug] [ADB] Device API level: 28
[AndroidUiautomator2Driver@8809 (b0af58ca)] Relaxing hidden api policy
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -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] [AndroidDriver] Parsing package and activity from app manifest
[ADB] Package name: 'provenance'
[ADB] Main activity name: 'crc64188153237d53579e.SplashActivity'
[debug] [AndroidDriver] Parsed package and activity are: provenance/crc64188153237d53579e.SplashActivity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 wait-for-device'
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell echo ping'
[debug] [AndroidDriver] Pushing settings apk to device...
[debug] [ADB] Getting install status for io.appium.settings
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 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 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys package io.appium.settings'
[debug] [ADB] The version name of the installed 'io.appium.settings' is greater or equal to the application version name ('4.2.3' >= '4.2.3')
[debug] [ADB] There is no need to install/upgrade 'C:\Users\shubham.bajad.appium\node_modules\appium-uiautomator2-driver\node_modules\io.appium.settings\apks\settings_apk-debug.apk'
[debug] [ADB] Getting IDs of all 'io.appium.settings' processes
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell 'pgrep --help; echo $?''
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell pgrep -f ([[:blank:]]|^)io.appium.settings([[:blank:]]|$)'
[debug] [AndroidDriver] io.appium.settings is already running. There is no need to reset its permissions.
[debug] [Logcat] Starting logs capture with command: C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 logcat -v threadtime
[debug] [AndroidUiautomator2Driver@8809 (b0af58ca)] Forwarding UiAutomator2 Server port 6790 to local port 8200
[debug] [ADB] Forwarding system: 8200 to device: 6790
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 forward tcp:8200 tcp:6790'
[debug] [ADB] Getting install status for io.appium.uiautomator2.server
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 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 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys package io.appium.uiautomator2.server'
[debug] [ADB] The version name of the installed 'io.appium.uiautomator2.server' is greater or equal to the application version name ('5.7.4' >= '5.7.4')
[debug] [AndroidUiautomator2Driver@8809 (b0af58ca)] io.appium.uiautomator2.server installation state: sameVersionInstalled
[debug] [ADB] Checking app cert for C:\Users\shubham.bajad.appium\node_modules\appium-uiautomator2-driver\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v5.7.4.apk
[ADB] Using 'apksigner.jar' from 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\build-tools\33.0.0\lib\apksigner.jar'
[debug] [ADB] Starting apksigner: 'C:\Program Files\Java\jdk1.8.0_341\bin\java.exe' -Xmx1024M -Xss1m -jar C:\Users\shubham.bajad\AppData\Local\Android\Sdk\build-tools\33.0.0\lib\apksigner.jar verify --print-certs C:\Users\shubham.bajad\.appium\node_modules\appium-uiautomator2-driver\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v5.7.4.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] sha256 hash did match for 'appium-uiautomator2-server-v5.7.4.apk'
[ADB] 'C:\Users\shubham.bajad.appium\node_modules\appium-uiautomator2-driver\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v5.7.4.apk' is signed with the default certificate
[debug] [ADB] Getting install status for io.appium.uiautomator2.server.test
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys package io.appium.uiautomator2.server.test'
[debug] [ADB] 'io.appium.uiautomator2.server.test' is installed
[debug] [ADB] Checking app cert for C:\Users\shubham.bajad.appium\node_modules\appium-uiautomator2-driver\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk
[debug] [ADB] Starting apksigner: 'C:\Program Files\Java\jdk1.8.0_341\bin\java.exe' -Xmx1024M -Xss1m -jar C:\Users\shubham.bajad\AppData\Local\Android\Sdk\build-tools\33.0.0\lib\apksigner.jar verify --print-certs C:\Users\shubham.bajad\.appium\node_modules\appium-uiautomator2-driver\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] sha256 hash did match for 'appium-uiautomator2-server-debug-androidTest.apk'
[ADB] 'C:\Users\shubham.bajad.appium\node_modules\appium-uiautomator2-driver\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk' is signed with the default certificate
[AndroidUiautomator2Driver@8809 (b0af58ca)] Server packages are not going to be (re)installed
[debug] [AndroidUiautomator2Driver@8809 (b0af58ca)] Waiting up to 30000ms for services to be available
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell pm list instrumentation'
[debug] [AndroidUiautomator2Driver@8809 (b0af58ca)] Instrumentation target 'io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner' is available
[ADB] Adding packages ["io.appium.settings","io.appium.uiautomator2.server","io.appium.uiautomator2.server.test"] to Doze whitelist
[debug] [ADB] Got the following command chunks to execute: [["dumpsys","deviceidle","whitelist","+io.appium.settings",";","dumpsys","deviceidle","whitelist","+io.appium.uiautomator2.server",";","dumpsys","deviceidle","whitelist","+io.appium.uiautomator2.server.test",";"]]
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys deviceidle whitelist +io.appium.settings ; dumpsys deviceidle whitelist +io.appium.uiautomator2.server ; dumpsys deviceidle whitelist +io.appium.uiautomator2.server.test ;'
[debug] [ADB] Checking app cert for C:\Users\shubham.bajad\eclipse-workspace\appiumtest\src\test\java\resources\provenance_v2.3.8.apk
[debug] [ADB] Starting apksigner: 'C:\Program Files\Java\jdk1.8.0_341\bin\java.exe' -Xmx1024M -Xss1m -jar C:\Users\shubham.bajad\AppData\Local\Android\Sdk\build-tools\33.0.0\lib\apksigner.jar verify --print-certs C:\Users\shubham.bajad\eclipse-workspace\appiumtest\src\test\java\resources\provenance_v2.3.8.apk
[debug] [ADB] apksigner stdout: Signer #1 certificate DN: CN=BlockChain
[debug] [ADB] Signer #1 certificate SHA-256 digest: ecf8399aac4ddeb9451b8f79023ec0ccaa28c843905bda685a4428b44f111bf6
[debug] [ADB] Signer #1 certificate SHA-1 digest: c69689c1b85d340fa9a1e18b24392ae008020694
[debug] [ADB] Signer #1 certificate MD5 digest: 1f8c259ee8a68c6fa528932cf60fff81
[debug] [ADB]
[ADB] 'C:\Users\shubham.bajad\eclipse-workspace\appiumtest\src\test\java\resources\provenance_v2.3.8.apk' is signed with a non-default certificate
[debug] [ADB] Getting install status for provenance
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys package provenance'
[debug] [ADB] 'provenance' is installed
[debug] [ADB] Getting package info for 'provenance'
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys package provenance'
[debug] [ADB] The version name of the installed 'provenance' is greater or equal to the application version name ('2.3.8' >= '2.3.8')
[debug] [ADB] There is no need to install/upgrade 'C:\Users\shubham.bajad\eclipse-workspace\appiumtest\src\test\java\resources\provenance_v2.3.8.apk'
[AndroidDriver] Performing fast reset on 'provenance'
[debug] [ADB] Getting install status for provenance
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys package provenance'
[debug] [ADB] 'provenance' is installed
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell am force-stop provenance'
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell pm clear provenance'
[debug] [AndroidDriver] Performed fast reset on the installed 'provenance' application (stop and clear)
[debug] [AndroidUiautomator2Driver@8809 (b0af58ca)] Performing shallow cleanup of automation leftovers
[debug] [AndroidUiautomator2Driver@8809 (b0af58ca)] No obsolete sessions have been detected (socket hang up)
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell am force-stop io.appium.uiautomator2.server.test'
[AndroidUiautomator2Driver@8809 (b0af58ca)] Starting UIAutomator2 server 5.7.4
[AndroidUiautomator2Driver@8809 (b0af58ca)] Using UIAutomator2 server from 'C:\Users\shubham.bajad.appium\node_modules\appium-uiautomator2-driver\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v5.7.4.apk' and test from 'C:\Users\shubham.bajad.appium\node_modules\appium-uiautomator2-driver\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk'
[AndroidUiautomator2Driver@8809 (b0af58ca)] Waiting up to 30000ms for UiAutomator2 to be online...
[debug] [ADB] Creating ADB subprocess with args: ["-P",5037,"-s","emulator-5554","shell","am","instrument","-w","-e","disableAnalytics",true,"io.appium.uiautomator2.server.test/androidx.test.runner.AndroidJUnitRunner"]
[debug] [AndroidUiautomator2Driver@8809 (b0af58ca)] Matched '/status' to command name 'getStatus'
[debug] [AndroidUiautomator2Driver@8809 (b0af58ca)] Proxying [GET /status] to [GET http://127.0.0.1:8200/status] with no body
[AndroidUiautomator2Driver@8809 (b0af58ca)] socket hang up
[debug] [AndroidUiautomator2Driver@8809 (b0af58ca)] Matched '/status' to command name 'getStatus'
[debug] [AndroidUiautomator2Driver@8809 (b0af58ca)] Proxying [GET /status] to [GET http://127.0.0.1:8200/status] with no body
[AndroidUiautomator2Driver@8809 (b0af58ca)] socket hang up
[debug] [Instrumentation] io.appium.uiautomator2.server.test.AppiumUiAutomator2Server:
[debug] [AndroidUiautomator2Driver@8809 (b0af58ca)] Matched '/status' to command name 'getStatus'
[debug] [AndroidUiautomator2Driver@8809 (b0af58ca)] Proxying [GET /status] to [GET http://127.0.0.1:8200/status] with no body
[AndroidUiautomator2Driver@8809 (b0af58ca)] socket hang up
[debug] [AndroidUiautomator2Driver@8809 (b0af58ca)] Matched '/status' to command name 'getStatus'
[debug] [AndroidUiautomator2Driver@8809 (b0af58ca)] Proxying [GET /status] to [GET http://127.0.0.1:8200/status] with no body
[debug] [AndroidUiautomator2Driver@8809 (b0af58ca)] Got response with status 200: {"sessionId":"None","value":{"message":"UiAutomator2 Server is ready to accept commands","ready":true}}
[debug] [AndroidUiautomator2Driver@8809 (b0af58ca)] The initialization of the instrumentation process took 3232ms
[debug] [AndroidUiautomator2Driver@8809 (b0af58ca)] Matched '/session' to command name 'createSession'
[debug] [AndroidUiautomator2Driver@8809 (b0af58ca)] Proxying [POST /session] to [POST http://127.0.0.1:8200/session] with body: {"capabilities":{"firstMatch":[{"platform":"LINUX","webStorageEnabled":false,"takesScreenshot":true,"javascriptEnabled":true,"databaseEnabled":false,"networkConnectionEnabled":true,"locationContextEnabled":false,"warnings":{},"desired":{"platformName":"android","app":"C:\Users\shubham.bajad\eclipse-workspace\appiumtest\src\test\java\resources\provenance_v2.3.8.apk","appPackage":"provenance","appWaitActivity":"SplashActivity","appWaitDuration":20000,"appWaitPackage":"20000","automationName":"UiAutomator2","deviceName":"ShubhamPhone9"},"platformName":"android","app":"C:\Users\shubham.bajad\eclipse-workspace\appiumtest\src\test\java\resources\provenance_v2.3.8.apk","appPackage":"provenance","appWaitActivity":"SplashActivity","appWaitDuration":20000,"appWaitPackage":"20000","automationName":"UiAutomator2","deviceName":"emulator-5554","deviceUDID":"emulator-5554"}],"alwaysMatch":{}}}
[debug] [AndroidUiautomator2Driver@8809 (b0af58ca)] Got response with status 200: {"sessionId":"df49082c-bf75-4996-94f8-3ac30e923062","value":{"capabilities":{"firstMatch":[{"platform":"LINUX","webStorageEnabled":false,"takesScreenshot":true,"javascriptEnabled":true,"databaseEnabled":false,"networkConnectionEnabled":true,"locationContextEnabled":false,"warnings":{},"desired":{"platformName":"android","app":"C:\Users\shubham.bajad\eclipse-workspace\appiumtest\src\test\java\resources\provenance_v2.3.8.apk","appPackage":"provenance","appWaitActivity":"SplashActivity","appWaitDuration":20000,"appWaitPackage":"20000","automationName":"UiAutomator2","deviceName":"ShubhamPhone9"},"platformName":"android","app":"C:\Users\shubham.bajad\eclipse-workspace\appiumtest\src\test\java\resources\provenance_v2.3.8.apk","appPackage":"provenance","appWaitActivity":"SplashActivity","appWaitDuration":20000,"appWaitPackage":"20000","automationName":"UiAutomator2","deviceName":"emulator-5554","deviceUDID":"emulator-5554"}],"alwaysMat...
[AndroidUiautomator2Driver@8809 (b0af58ca)] Determined the downstream protocol as 'W3C'
[debug] [AndroidUiautomator2Driver@8809 (b0af58ca)] Proxying [GET /appium/device/info] to [GET http://127.0.0.1:8200/session/df49082c-bf75-4996-94f8-3ac30e923062/appium/device/info] with no body
[debug] [AndroidUiautomator2Driver@8809 (b0af58ca)] Got response with status 200: {"sessionId":"df49082c-bf75-4996-94f8-3ac30e923062","value":{"androidId":"cbbdd8a479f233fe","apiVersion":"28","bluetooth":null,"brand":"google","carrierName":"Android","displayDensity":320,"locale":"en_US","manufacturer":"Google","model":"AOSP on IA Emulator","networks":[{"capabilities":{"SSID":null,"linkDownBandwidthKbps":102400,"linkUpstreamBandwidthKbps":51200,"networkCapabilities":"NET_CAPABILITY_MMS,NET_CAPABILITY_SUPL,NET_CAPABILITY_DUN,NET_CAPABILITY_FOTA,NET_CAPABILITY_IMS,NET_CAPABILITY_CBS,NET_CAPABILITY_IA,NET_CAPABILITY_INTERNET,NET_CAPABILITY_NOT_RESTRICTED,NET_CAPABILITY_TRUSTED,NET_CAPABILITY_NOT_VPN,NET_CAPABILITY_VALIDATED,NET_CAPABILITY_NOT_ROAMING,NET_CAPABILITY_FOREGROUND,NET_CAPABILITY_NOT_CONGESTED,NET_CAPABILITY_NOT_SUSPENDED","signalStrength":-2147483648,"transportTypes":"TRANSPORT_CELLULAR"},"detailedState":"CONNECTED","extraInfo":"epc.tmobile.com","isAvailable":true,"isConnected":true,"isFailover":false,"isRoaming":false,"state":"CONNECTED","subtype":13,"subtypeName":"LTE","type":...
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window'
[AndroidDriver] Screen already unlocked, doing nothing
[AndroidUiautomator2Driver@8809 (b0af58ca)] Starting 'provenance/crc64188153237d53579e.SplashActivity and waiting for '20000/SplashActivity'
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell am start -W -n provenance/crc64188153237d53579e.SplashActivity -S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000'
[debug] [ADB] Waiting up to 20000ms for activity matching pkg: '20000' and activity: 'SplashActivity' to be focused
[debug] [ADB] Possible activities, to be checked: 'SplashActivity', '20000.SplashActivity'
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [AndroidUiautomator2Driver@8809 (b0af58ca)] Deleting UiAutomator2 session
[debug] [AndroidUiautomator2Driver@8809 (b0af58ca)] Deleting UiAutomator2 server session
[debug] [AndroidUiautomator2Driver@8809 (b0af58ca)] Matched '/' to command name 'deleteSession'
[debug] [AndroidUiautomator2Driver@8809 (b0af58ca)] Proxying [DELETE /] to [DELETE http://127.0.0.1:8200/session/df49082c-bf75-4996-94f8-3ac30e923062] with no body
[debug] [AndroidUiautomator2Driver@8809 (b0af58ca)] Got response with status 200: {"sessionId":"df49082c-bf75-4996-94f8-3ac30e923062","value":null}
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell am force-stop provenance'
[debug] [Logcat] Stopping logcat capture
[debug] [ADB] Removing forwarded port socket connection: 8200
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 forward --remove tcp:8200'
[AndroidUiautomator2Driver@8809 (b0af58ca)] Restoring hidden api policy to the device default configuration
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -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] [AppiumDriver@fb8b] Event 'newSessionStarted' logged at 1669109809127 (15:06:49 GMT+0530 (India Standard Time))
[debug] [AppiumDriver@fb8b] Encountered internal error running command: Error: Cannot start the 'provenance' application. Consider checking the driver's troubleshooting documentation. Original error: 'SplashActivity' or '20000.SplashActivity' never started. Consider checking the driver's troubleshooting documentation.
[debug] [AppiumDriver@fb8b] at ADB.startApp (C:\Users\shubham.bajad.appium\node_modules\appium-uiautomator2-driver\node_modules\appium-adb\lib\tools\apk-utils.js:177:11)
[debug] [AppiumDriver@fb8b] at AndroidUiautomator2Driver.ensureAppStarts (C:\Users\shubham.bajad.appium\node_modules\appium-uiautomator2-driver\lib\driver.js:583:7)
[debug] [AppiumDriver@fb8b] at AndroidUiautomator2Driver.startUiAutomator2Session (C:\Users\shubham.bajad.appium\node_modules\appium-uiautomator2-driver\lib\driver.js:441:7)
[debug] [AppiumDriver@fb8b] at AndroidUiautomator2Driver.createSession (C:\Users\shubham.bajad.appium\node_modules\appium-uiautomator2-driver\lib\driver.js:239:7)
[debug] [AppiumDriver@fb8b] at AppiumDriver.createSession (C:\Users\shubham.bajad\AppData\Roaming\npm\node_modules\appium\lib\appium.js:336:35)
[HTTP] <-- POST /session 500 43481 ms - 1091
[HTTP]
[debug] [Instrumentation] .
[debug] [Instrumentation]
[debug] [Instrumentation] Time: 31.095
[debug] [Instrumentation]
[debug] [Instrumentation] OK (1 test)
[debug] [Instrumentation] The process has exited with code 0

KazuCocoa Nov 22, 2022
Maintainer

The capability had [debug] [AndroidUiautomator2Driver@8809] "appium:appWaitPackage": "20000",, it means Appium wait for the 20000 package name.

[AndroidDriver] Screen already unlocked, doing nothing
[AndroidUiautomator2Driver@8809 (b0af58ca)] Starting 'provenance/crc64188153237d53579e.SplashActivity and waiting for '20000/SplashActivity'
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell am start -W -n provenance/crc64188153237d53579e.SplashActivity -S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000'
[debug] [ADB] Waiting up to 20000ms for activity matching pkg: '20000' and activity: 'SplashActivity' to be focused
[debug] [ADB] Possible activities, to be checked: 'SplashActivity', '20000.SplashActivity'
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\A

You may need to set the expected package name properly for your test app.

shubhambajad Nov 23, 2022
Author

ok. I tried that also by discussing the things with the developer still facing the same issue.
Is my code is correct for setting up the appActivity and appPackage or is it incorrect?

Another thing is like,
[debug] [ADB] Running 'C:\Users\shubham.bajad\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window windows'
[debug] [ADB] Found package: 'riotinto.metal.provenance' and fully qualified activity name : 'crc64188153237d53579e.MainActivity'
[debug] [ADB] Incorrect package and activity. Retrying.

The found package is the correct one still why it is giving response related to Incorrect package and activity?

@KazuCocoa @jlipps

KazuCocoa Nov 23, 2022
Maintainer

What was the appium server log? GitHub GIST is preferred to share such a large log.
Based on your previous comment, Appium should have waited for "appium:appWaitActivity": "SplashActivity", to be the top activity.

KazuCocoa Nov 23, 2022
Maintainer

https://discuss.appium.io/ also may help to ask questions

This comment was marked as spam.

Sign in to view

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Getting error message as "Could not start a new session. Response code 500. Message: An unknown server-side error occurred while processing the command. Original error: Cannot start the 'riotinto.metal.provenance' application. Consider checking the driver's troubleshooting documentation" #17809

Uh oh!

{{title}}

Uh oh!

Replies: 2 comments 7 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

This comment was marked as spam.

Select a reply

Uh oh!

Uh oh!

Getting error message as "Could not start a new session. Response code 500. Message: An unknown server-side error occurred while processing the command. Original error: Cannot start the 'riotinto.metal.provenance' application. Consider checking the driver's troubleshooting documentation" #17809

Uh oh!

shubhambajad Nov 21, 2022

Replies: 2 comments · 7 replies

Uh oh!

jlipps Nov 21, 2022 Maintainer

Uh oh!

Uh oh!

shubhambajad Nov 22, 2022 Author

Uh oh!

KazuCocoa Nov 22, 2022 Maintainer

Uh oh!

shubhambajad Nov 23, 2022 Author

Uh oh!

KazuCocoa Nov 23, 2022 Maintainer

Uh oh!

KazuCocoa Nov 23, 2022 Maintainer

This comment was marked as spam.

shubhambajad
Nov 21, 2022

Replies: 2 comments 7 replies

jlipps
Nov 21, 2022
Maintainer

shubhambajad Nov 22, 2022
Author

KazuCocoa Nov 22, 2022
Maintainer

shubhambajad Nov 23, 2022
Author

KazuCocoa Nov 23, 2022
Maintainer

KazuCocoa Nov 23, 2022
Maintainer