Please assist me learn to establish issues in Appium cellular automation: I do not know the place to look to establish the error.
I constructed a take a look at app with android-sdk on my bodily cell phone.
I took somewhat Appium take a look at in java simply to launch the take a look at app on a linked bodily Android machine – a Huawei P30Pro.
- this take a look at is from an excellent tutorial with no errors in eclipse. It certain must be superb, the pom.xml too.
- Appium server v1.22.3 is working in a single occasion
- in Eclipse, I press the take a look at Button
Run as Java Utility - the server window begins writing many strains prefer it’s working
Drawback is:
1.) The Server writes many strains when working (is that this the Server log (What/the place is a stack hint?))
However abruptly comes the final line:
[HTTP] <-- POST /wd/hub/session 500 4111 ms - 637
[HTTP]
1.b) at this second the Eclipse console writes:
Server-side error occurred whereas processing Appium-server
Driver information: driver.model: AppiumDriver
org.openqa.selenium.SessionNotCreatedException: Unable to create a brand new distant session. Please verify the server log for extra particulars.
Unique error: An unknown server-side error occurred whereas processing the command. Unique error: 'app' possibility is required for reinstall
... 12 extra
2.) The Take a look at-App shouldn’t be launching at cellular machine
However I’ve Android-Notification from Appium Settings ‘Preserve this service working, so Appium for Android can work with system APIs’
My query is:
How can I discover why <– POST /wd/hub/session has State=500
And why does this error come so late; why not at starting
The server is working
The server is working
[Appium] Welcome to Appium v1.22.3
[Appium] Non-default server args:
[Appium] relaxedSecurityEnabled: true
[Appium] allowInsecure: {
[Appium] }
[Appium] denyInsecure: {
[Appium] }
[Appium] Appium REST http interface listener began on 0.0.0.0:4723
[HTTP] --> POST /wd/hub/session
[HTTP] {"desiredCapabilities":{"appActivity":"com.instance.yeshasprabhakar.todo.MainActivity","appPackage":"com.instance.yeshasprabhakar.todo1.0","platformName":"Android","udid":"22X0220428007340","platformVersion":"10.0"},"capabilities":{"firstMatch":[{"appium:appActivity":"com.example.yeshasprabhakar.todo.MainActivity","appium:appPackage":"com.example.yeshasprabhakar.todo1.0","platformName":"android","appium:platformVersion":"10.0","appium:udid":"22X0220428007340"}]}}
[W3C] Calling AppiumDriver.createSession() with args: [{"appActivity":"com.example.yeshasprabhakar.todo.MainActivity","appPackage":"com.example.yeshasprabhakar.todo1.0","platformName":"Android","udid":"22X0220428007340","platformVersion":"10.0"},null,{"firstMatch":[{"appium:appActivity":"com.example.yeshasprabhakar.todo.MainActivity","appium:appPackage":"com.example.yeshasprabhakar.todo1.0","platformName":"android","appium:platformVersion":"10.0","appium:udid":"22X0220428007340"}]}]
[BaseDriver] Occasion 'newSessionRequested' logged at 1665348795592 (22:53:15 GMT+0200 (Mitteleuropäische Sommerzeit))
[Appium]
[Appium] ======================================================================
[Appium] DEPRECATION WARNING:
[Appium]
[Appium] The 'automationName' functionality was not offered within the desired
[Appium] capabilities for this Android session
[Appium]
[Appium] Setting 'automationName=UiAutomator2' by default and utilizing the
[Appium] UiAutomator2 Driver
[Appium]
[Appium] The subsequent main model of Appium (2.x) will **require** the
[Appium] 'automationName' functionality to be set for all periods on all
[Appium] platforms
[Appium]
[Appium] In earlier variations (Appium <= 1.13.x), the default was
[Appium] 'automationName=UiAutomator1'
[Appium]
[Appium] When you want to use that automation as an alternative of UiAutomator2, please
[Appium] add 'automationName=UiAutomator1' to your required capabilities
[Appium]
[Appium] For extra details about drivers, please go to
[Appium] http://appium.io/docs/en/about-appium/intro/ and discover the
[Appium] 'Drivers' menu
[Appium]
[Appium] ======================================================================
[Appium]
[Appium] Appium v1.22.3 creating new AndroidUiautomator2Driver (v1.70.1) session
[Appium] Making use of relaxed safety to 'AndroidUiautomator2Driver' as per server command line argument. All insecure options will probably be enabled except explicitly disabled by --deny-insecure
[BaseDriver] W3C capabilities and MJSONWP desired capabilities had been offered
[BaseDriver] Creating session with W3C capabilities: {
[BaseDriver] "alwaysMatch": {
[BaseDriver] "platformName": "android",
[BaseDriver] "appium:appActivity": "com.instance.yeshasprabhakar.todo.MainActivity",
[BaseDriver] "appium:appPackage": "com.instance.yeshasprabhakar.todo1.0",
[BaseDriver] "appium:platformVersion": "10.0",
[BaseDriver] "appium:udid": "22X0220428007340"
[BaseDriver] },
[BaseDriver] "firstMatch": [
[BaseDriver] {}
[BaseDriver] ]
[BaseDriver] }
[BaseDriver] Session created with session id: cf0a35b0-da66-4fa9-a6c7-b4aca880f564
[UiAutomator2] Beginning 'com.instance.yeshasprabhakar.todo1.0' instantly on the machine
[ADB] Discovered 3 'build-tools' folders beneath 'C:UserscauseAppDataLocalAndroidSdk' (latest first):
[ADB] C:/Customers/trigger/AppData/Native/Android/Sdk/build-tools/33.0.0
[ADB] C:/Customers/trigger/AppData/Native/Android/Sdk/build-tools/30.0.3
[ADB] C:/Customers/trigger/AppData/Native/Android/Sdk/build-tools/29.0.3
[ADB] Utilizing 'adb.exe' from 'C:UserscauseAppDataLocalAndroidSdkplatform-toolsadb.exe'
[ADB] Working 'C:UserscauseAppDataLocalAndroidSdkplatform-toolsadb.exe -P 5037 start-server'
[AndroidDriver] Retrieving machine record
[ADB] Looking for a linked android machine
[ADB] Getting linked gadgets
[ADB] Related gadgets: [{"udid":"22X0220428007340","state":"device"}]
[AndroidDriver] Utilizing machine: 22X0220428007340
[ADB] Utilizing 'adb.exe' from 'C:UserscauseAppDataLocalAndroidSdkplatform-toolsadb.exe'
[ADB] Working 'C:UserscauseAppDataLocalAndroidSdkplatform-toolsadb.exe -P 5037 start-server'
[ADB] Setting machine id to 22X0220428007340
[ADB] Working 'C:UserscauseAppDataLocalAndroidSdkplatform-toolsadb.exe -P 5037 -s 22X0220428007340 shell getprop ro.construct.model.sdk'
[ADB] Present machine property 'ro.construct.model.sdk': 29
[ADB] Getting machine platform model
[ADB] Working 'C:UserscauseAppDataLocalAndroidSdkplatform-toolsadb.exe -P 5037 -s 22X0220428007340 shell getprop ro.construct.model.launch'
[ADB] Present machine property 'ro.construct.model.launch': 10
[ADB] System API stage: 29
[UiAutomator2] Enjoyable hidden api coverage
[ADB] Working 'C:UserscauseAppDataLocalAndroidSdkplatform-toolsadb.exe -P 5037 -s 22X0220428007340 shell 'settings put international hidden_api_policy_pre_p_apps 1;settings put international hidden_api_policy_p_apps 1;settings put international hidden_api_policy 1''
[AndroidDriver] No app despatched in, not parsing bundle/exercise
[ADB] Working 'C:UserscauseAppDataLocalAndroidSdkplatform-toolsadb.exe -P 5037 -s 22X0220428007340 wait-for-device'
[ADB] Working 'C:UserscauseAppDataLocalAndroidSdkplatform-toolsadb.exe -P 5037 -s 22X0220428007340 shell echo ping'
[AndroidDriver] Pushing settings apk to machine...
[ADB] Getting set up standing for io.appium.settings
[ADB] Working 'C:UserscauseAppDataLocalAndroidSdkplatform-toolsadb.exe -P 5037 -s 22X0220428007340 shell dumpsys bundle io.appium.settings'
[ADB] 'io.appium.settings' is put in
[ADB] Getting bundle information for 'io.appium.settings'
[ADB] Working 'C:UserscauseAppDataLocalAndroidSdkplatform-toolsadb.exe -P 5037 -s 22X0220428007340 shell dumpsys bundle io.appium.settings'
[ADB] The model title of the put in 'io.appium.settings' is larger or equal to the applying model title ('3.4.0' >= '3.4.0')
[ADB] There is no such thing as a want to put in/improve 'C:Program FilesAppium Server GUIresourcesappnode_modulesappiumnode_modulesio.appium.settingsapkssettings_apk-debug.apk'
[ADB] Getting IDs of all 'io.appium.settings' processes
[ADB] Working 'C:UserscauseAppDataLocalAndroidSdkplatform-toolsadb.exe -P 5037 -s 22X0220428007340 shell 'pgrep --help; echo $?''
[ADB] Working 'C:UserscauseAppDataLocalAndroidSdkplatform-toolsadb.exe -P 5037 -s 22X0220428007340 shell pgrep -f ([[:blank:]]|^)io.appium.settings([[:blank:]]|$)'
[AndroidDriver] io.appium.settings is already working. There is no such thing as a have to reset its permissions.
[ADB] Working 'C:UserscauseAppDataLocalAndroidSdkplatform-toolsadb.exe -P 5037 -s 22X0220428007340 shell appops set io.appium.settings android:mock_location enable'
[Logcat] Beginning logs seize with command: C:CustomerstriggerAppDataNativeAndroidSdkplatform-toolsadb.exe -P 5037 -s 22X0220428007340 logcat -v threadtime
[UiAutomator2] Forwarding UiAutomator2 Server port 6790 to native port 8200
[ADB] Forwarding system: 8200 to machine: 6790
[ADB] Working 'C:UserscauseAppDataLocalAndroidSdkplatform-toolsadb.exe -P 5037 -s 22X0220428007340 ahead tcp:8200 tcp:6790'
[UiAutomator2] Server bundle at 'C:Program FilesAppium Server GUIresourcesappnode_modulesappiumnode_modulesappium-uiautomator2-serverapksappium-uiautomator2-server-v4.27.0.apk' shouldn't be writeable. Will copy it into the non permanent location at 'C:UserscauseAppDataLocalTemp202299-19828-1p2wn9i.yjgq' as a workaround. Take into account making this file writeable manually with a view to enhance the efficiency of session startup.
[UiAutomator2] Server bundle at 'C:Program FilesAppium Server GUIresourcesappnode_modulesappiumnode_modulesappium-uiautomator2-serverapksappium-uiautomator2-server-debug-androidTest.apk' shouldn't be writeable. Will copy it into the non permanent location at 'C:UserscauseAppDataLocalTemp202299-19828-1p2wn9i.yjgq' as a workaround. Take into account making this file writeable manually with a view to enhance the efficiency of session startup.
[ADB] Getting set up standing for io.appium.uiautomator2.server
[ADB] Working 'C:UserscauseAppDataLocalAndroidSdkplatform-toolsadb.exe -P 5037 -s 22X0220428007340 shell dumpsys bundle io.appium.uiautomator2.server'
[ADB] 'io.appium.uiautomator2.server' is put in
[ADB] Getting bundle information for 'io.appium.uiautomator2.server'
[ADB] Working 'C:UserscauseAppDataLocalAndroidSdkplatform-toolsadb.exe -P 5037 -s 22X0220428007340 shell dumpsys bundle io.appium.uiautomator2.server'
[ADB] The model title of the put in 'io.appium.uiautomator2.server' is larger or equal to the applying model title ('4.27.0' >= '4.27.0')
[UiAutomator2] io.appium.uiautomator2.server set up state: sameVersionInstalled
[ADB] Checking app cert for C:UserscauseAppDataLocalTemp202299-19828-1p2wn9i.yjgqappium-uiautomator2-server-v4.27.0.apk
[ADB] Utilizing 'apksigner.jar' from 'C:UserscauseAppDataLocalAndroidSdkbuild-tools33.0.0libapksigner.jar'
[ADB] Beginning apksigner: 'C:Program InformationJavajdk-19binjava.exe' -Xmx1024M -Xss1m -jar C:CustomerstriggerAppDataNativeAndroidSdkbuild-tools33.0.0libapksigner.jar confirm --print-certs C:CustomerstriggerAppDataNativeTemp202299-19828-1p2wn9i.yjgqappium-uiautomator2-server-v4.27.0.apk
[ADB] apksigner stdout: Signer #1 certificates DN: [email protected], CN=Android, OU=Android, O=Android, L=Mountain View, ST=California, C=US
[ADB] Signer #1 certificates SHA-256 digest: a40da80a59d170caa950cf15c18c454d47a39b26989d8b640ecd745ba71bf5dc
[ADB] Signer #1 certificates SHA-1 digest: 61ed377e85d386a8dfee6b864bd85b0bfaa5af81
[ADB] Signer #1 certificates MD5 digest: e89b158e4bcf988ebd09eb83f5378e87
[ADB]
[ADB] sha256 hash did match for 'appium-uiautomator2-server-v4.27.0.apk'
[ADB] 'C:UserscauseAppDataLocalTemp202299-19828-1p2wn9i.yjgqappium-uiautomator2-server-v4.27.0.apk' is signed with the default certificates
[ADB] Getting set up standing for io.appium.uiautomator2.server.take a look at
[ADB] Working 'C:UserscauseAppDataLocalAndroidSdkplatform-toolsadb.exe -P 5037 -s 22X0220428007340 shell dumpsys bundle io.appium.uiautomator2.server.take a look at'
[ADB] 'io.appium.uiautomator2.server.take a look at' is put in
[ADB] Checking app cert for C:UserscauseAppDataLocalTemp202299-19828-1p2wn9i.yjgqappium-uiautomator2-server-debug-androidTest.apk
[ADB] Beginning apksigner: 'C:Program InformationJavajdk-19binjava.exe' -Xmx1024M -Xss1m -jar C:CustomerstriggerAppDataNativeAndroidSdkbuild-tools33.0.0libapksigner.jar confirm --print-certs C:CustomerstriggerAppDataNativeTemp202299-19828-1p2wn9i.yjgqappium-uiautomator2-server-debug-androidTest.apk
[ADB] apksigner stdout: Signer #1 certificates DN: [email protected], CN=Android, OU=Android, O=Android, L=Mountain View, ST=California, C=US
[ADB] Signer #1 certificates SHA-256 digest: a40da80a59d170caa950cf15c18c454d47a39b26989d8b640ecd745ba71bf5dc
[ADB] Signer #1 certificates SHA-1 digest: 61ed377e85d386a8dfee6b864bd85b0bfaa5af81
[ADB] Signer #1 certificates MD5 digest: e89b158e4bcf988ebd09eb83f5378e87
[ADB]
[ADB] sha256 hash did match for 'appium-uiautomator2-server-debug-androidTest.apk'
[ADB] 'C:UserscauseAppDataLocalTemp202299-19828-1p2wn9i.yjgqappium-uiautomator2-server-debug-androidTest.apk' is signed with the default certificates
[UiAutomator2] Server packages should not going to be (re)put in
[UiAutomator2] Ready as much as 30000ms for companies to be out there
[ADB] Working 'C:UserscauseAppDataLocalAndroidSdkplatform-toolsadb.exe -P 5037 -s 22X0220428007340 shell pm record instrumentation'
[UiAutomator2] Instrumentation goal 'io.appium.uiautomator2.server.take a look at/androidx.take a look at.runner.AndroidJUnitRunner' is accessible
[ADB] Including packages ["io.appium.settings","io.appium.uiautomator2.server","io.appium.uiautomator2.server.test"] to Doze whitelist
[ADB] Bought the next 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",";"]]
[ADB] Working 'C:UserscauseAppDataLocalAndroidSdkplatform-toolsadb.exe -P 5037 -s 22X0220428007340 shell dumpsys deviceidle whitelist +io.appium.settings ; dumpsys deviceidle whitelist +io.appium.uiautomator2.server ; dumpsys deviceidle whitelist +io.appium.uiautomator2.server.take a look at ;'
[UiAutomator2] No app functionality. Assuming it's already on the machine
[ADB] Getting set up standing for com.instance.yeshasprabhakar.todo1.0
[ADB] Working 'C:UserscauseAppDataLocalAndroidSdkplatform-toolsadb.exe -P 5037 -s 22X0220428007340 shell dumpsys bundle com.instance.yeshasprabhakar.todo1.0'
[ADB] 'com.instance.yeshasprabhakar.todo1.0' shouldn't be put in
[UiAutomator2] Deleting UiAutomator2 session
[UiAutomator2] Deleting UiAutomator2 server session
[WD Proxy] Matched "https://sqa.stackexchange.com/" to command title 'deleteSession'
[UiAutomator2] Didn't get affirmation UiAutomator2 deleteSession labored; Error was: UnknownError: An unknown server-side error occurred whereas processing the command. Unique error: Attempting to proxy a session command with out session id
[ADB] Working 'C:UserscauseAppDataLocalAndroidSdkplatform-toolsadb.exe -P 5037 -s 22X0220428007340 shell am force-stop com.instance.yeshasprabhakar.todo1.0'
[Logcat] Stopping logcat seize
[ADB] Eradicating forwarded port socket connection: 8200
[ADB] Working 'C:UserscauseAppDataLocalAndroidSdkplatform-toolsadb.exe -P 5037 -s 22X0220428007340 ahead --remove tcp:8200'
[UiAutomator2] Restoring hidden api coverage to the machine default configuration
[ADB] Working 'C:UserscauseAppDataLocalAndroidSdkplatform-toolsadb.exe -P 5037 -s 22X0220428007340 shell 'settings delete international hidden_api_policy_pre_p_apps;settings delete international hidden_api_policy_p_apps;settings delete international hidden_api_policy''
[BaseDriver] Occasion 'newSessionStarted' logged at 1665348801035 (22:53:21 GMT+0200 (Mitteleuropäische Sommerzeit))
[W3C] Encountered inside error working command: Error: 'app' possibility is required for reinstall
[W3C] at Object.resetApp (C:Program FilesAppium Server GUIresourcesappnode_modulesappiumnode_modulesappium-android-driverlibandroid-helpers.js:405:11)
[W3C] at AndroidUiautomator2Driver.initAUT (C:Program FilesAppium Server GUIresourcesappnode_modulesappiumnode_modulesappium-uiautomator2-driverlibdriver.js:546:9)
[W3C] at AndroidUiautomator2Driver.startUiAutomator2Session (C:Program FilesAppium Server GUIresourcesappnode_modulesappiumnode_modulesappium-uiautomator2-driverlibdriver.js:408:5)
[W3C] at AndroidUiautomator2Driver.createSession (C:Program FilesAppium Server GUIresourcesappnode_modulesappiumnode_modulesappium-uiautomator2-driverlibdriver.js:229:7)
[W3C] at AppiumDriver.createSession (C:Program FilesAppium Server GUIresourcesappnode_modulesappiumlibappium.js:387:35)
[HTTP] <-- POST /wd/hub/session 500 5562 ms - 663
[HTTP]
