Able to launch the app but after that it closed automatically

Dutta · June 4, 2023, 12:06pm

Hi Team
need an help, i am able to launch the app but after that it close immediately without clicking on locators. Not sure what is wrong.
java -version

java version “20.0.1” 2023-04-18

Java™ SE Runtime Environment (build 20.0.1+9-29)

Java HotSpot™ 64-Bit Server VM (build 20.0.1+9-29, mixed mode, sharing)

appium -version :

2.0.0-beta.71
appium driver list
Listing available drivers

[email protected] [installed (npm)]
[email protected] [installed (npm)]
[email protected] [installed (npm)]
mac2 [not installed]
espresso [not installed]
safari [not installed]
chromium [not installed]

/Library/Java/JavaVirtualMachines/jdk-18.0.2.1.jdk/Contents/Home/bin/java -ea -Didea.test.cyclic.buffer.size=1048576 -javaagent:/Applications/IntelliJ IDEA CE.app/Contents/lib/idea_rt.jar=49158:/Applications/IntelliJ IDEA CE.app/Contents/bin -Dfile.encoding=UTF-8 -Dsun.stdout.encoding=UTF-8 -Dsun.stderr.encoding=UTF-8 -classpath /Applications/IntelliJ IDEA CE.app/Contents/lib/idea_rt.jar:/Applications/IntelliJ IDEA CE.app/Contents/plugins/testng/lib/testng-rt.jar:/Users/xxxxx/IdeaProjects/Test/target/test-classes:/Users/xxxxx/.m2/repository/org/apache/maven/maven-core/3.9.2/maven-core-3.9.2.jar:/Users/xxxxx/.m2/repository/org/apache/maven/maven-model/3.9.2/maven-model-3.9.2.jar:/Users/xxxxx/.m2/repository/org/apache/maven/maven-settings/3.9.2/maven-settings-3.9.2.jar:/Users/xxxxx/.m2/repository/org/apache/maven/maven-settings-builder/3.9.2/maven-settings-builder-3.9.2.jar:/Users/xxxxx/.m2/repository/org/codehaus/plexus/plexus-sec-dispatcher/2.0/plexus-sec-dispatcher-2.0.jar:/Users/xxxxx/.m2/repository/org/codehaus/plexus/plexus-cipher/2.0/plexus-cipher-2.0.jar:/Users/xxxxx/.m2/repository/org/apache/maven/maven-builder-support/3.9.2/maven-builder-support-3.9.2.jar:/Users/xxxxx/.m2/repository/org/apache/maven/maven-repository-metadata/3.9.2/maven-repository-metadata-3.9.2.jar:/Users/xxxxx/.m2/repository/org/apache/maven/maven-artifact/3.9.2/maven-artifact-3.9.2.jar:/Users/xxxxx/.m2/repository/org/apache/maven/maven-plugin-api/3.9.2/maven-plugin-api-3.9.2.jar:/Users/xxxxx/.m2/repository/org/apache/maven/maven-model-builder/3.9.2/maven-model-builder-3.9.2.jar:/Users/xxxxx/.m2/repository/org/apache/maven/maven-resolver-provider/3.9.2/maven-resolver-provider-3.9.2.jar:/Users/xxxxx/.m2/repository/org/apache/maven/resolver/maven-resolver-impl/1.9.10/maven-resolver-impl-1.9.10.jar:/Users/xxxxx/.m2/repository/org/apache/maven/resolver/maven-resolver-named-locks/1.9.10/maven-resolver-named-locks-1.9.10.jar:/Users/xxxxx/.m2/repository/org/apache/maven/resolver/maven-resolver-api/1.9.10/maven-resolver-api-1.9.10.jar:/Users/xxxxx/.m2/repository/org/apache/maven/resolver/maven-resolver-spi/1.9.10/maven-resolver-spi-1.9.10.jar:/Users/xxxxx/.m2/repository/org/apache/maven/resolver/maven-resolver-util/1.9.10/maven-resolver-util-1.9.10.jar:/Users/xxxxx/.m2/repository/org/apache/maven/shared/maven-shared-utils/3.3.4/maven-shared-utils-3.3.4.jar:/Users/xxxxx/.m2/repository/org/eclipse/sisu/org.eclipse.sisu.plexus/0.3.5/org.eclipse.sisu.plexus-0.3.5.jar:/Users/xxxxx/.m2/repository/javax/annotation/javax.annotation-api/1.2/javax.annotation-api-1.2.jar:/Users/xxxxx/.m2/repository/org/eclipse/sisu/org.eclipse.sisu.inject/0.3.5/org.eclipse.sisu.inject-0.3.5.jar:/Users/xxxxx/.m2/repository/com/google/inject/guice/5.1.0/guice-5.1.0.jar:/Users/xxxxx/.m2/repository/aopalliance/aopalliance/1.0/aopalliance-1.0.jar:/Users/xxxxx/.m2/repository/com/google/guava/guava/31.1-jre/guava-31.1-jre.jar:/Users/xxxxx/.m2/repository/com/google/guava/failureaccess/1.0.1/failureaccess-1.0.1.jar:/Users/xxxxx/.m2/repository/javax/inject/javax.inject/1/javax.inject-1.jar:/Users/xxxxx/.m2/repository/org/codehaus/plexus/plexus-utils/3.5.1/plexus-utils-3.5.1.jar:/Users/xxxxx/.m2/repository/org/codehaus/plexus/plexus-classworlds/2.7.0/plexus-classworlds-2.7.0.jar:/Users/xxxxx/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.26/plexus-interpolation-1.26.jar:/Users/xxxxx/.m2/repository/org/codehaus/plexus/plexus-component-annotations/2.1.0/plexus-component-annotations-2.1.0.jar:/Users/xxxxx/.m2/repository/org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar:/Users/xxxxx/.m2/repository/org/slf4j/slf4j-api/1.7.36/slf4j-api-1.7.36.jar:/Users/xxxxx/.m2/repository/org/testng/testng/7.8.0/testng-7.8.0.jar:/Users/xxxxx/.m2/repository/com/beust/jcommander/1.82/jcommander-1.82.jar:/Users/xxxxx/.m2/repository/org/webjars/jquery/3.6.1/jquery-3.6.1.jar:/Users/xxxxx/.m2/repository/io/appium/java-client/8.5.0/java-client-8.5.0.jar:/Users/xxxxx/.m2/repository/org/seleniumhq/selenium/selenium-api/4.9.1/selenium-api-4.9.1.jar:/Users/xxxxx/.m2/repository/org/seleniumhq/selenium/selenium-remote-driver/4.9.1/selenium-remote-driver-4.9.1.jar:/Users/xxxxx/.m2/repository/com/google/auto/service/auto-service-annotations/1.0.1/auto-service-annotations-1.0.1.jar:/Users/xxxxx/.m2/repository/com/google/auto/service/auto-service/1.0.1/auto-service-1.0.1.jar:/Users/xxxxx/.m2/repository/com/google/auto/auto-common/1.2/auto-common-1.2.jar:/Users/xxxxx/.m2/repository/io/netty/netty-buffer/4.1.91.Final/netty-buffer-4.1.91.Final.jar:/Users/xxxxx/.m2/repository/io/netty/netty-codec-http/4.1.91.Final/netty-codec-http-4.1.91.Final.jar:/Users/xxxxx/.m2/repository/io/netty/netty-codec/4.1.91.Final/netty-codec-4.1.91.Final.jar:/Users/xxxxx/.m2/repository/io/netty/netty-handler/4.1.91.Final/netty-handler-4.1.91.Final.jar:/Users/xxxxx/.m2/repository/io/netty/netty-common/4.1.91.Final/netty-common-4.1.91.Final.jar:/Users/xxxxx/.m2/repository/io/netty/netty-transport-classes-epoll/4.1.91.Final/netty-transport-classes-epoll-4.1.91.Final.jar:/Users/xxxxx/.m2/repository/io/netty/netty-transport-classes-kqueue/4.1.91.Final/netty-transport-classes-kqueue-4.1.91.Final.jar:/Users/xxxxx/.m2/repository/io/netty/netty-transport-native-epoll/4.1.91.Final/netty-transport-native-epoll-4.1.91.Final.jar:/Users/xxxxx/.m2/repository/io/netty/netty-transport-native-kqueue/4.1.91.Final/netty-transport-native-kqueue-4.1.91.Final.jar:/Users/xxxxx/.m2/repository/io/netty/netty-transport-native-unix-common/4.1.91.Final/netty-transport-native-unix-common-4.1.91.Final.jar:/Users/xxxxx/.m2/repository/io/netty/netty-transport/4.1.91.Final/netty-transport-4.1.91.Final.jar:/Users/xxxxx/.m2/repository/io/netty/netty-resolver/4.1.91.Final/netty-resolver-4.1.91.Final.jar:/Users/xxxxx/.m2/repository/io/opentelemetry/opentelemetry-api/1.25.0/opentelemetry-api-1.25.0.jar:/Users/xxxxx/.m2/repository/io/opentelemetry/opentelemetry-context/1.25.0/opentelemetry-context-1.25.0.jar:/Users/xxxxx/.m2/repository/io/opentelemetry/opentelemetry-exporter-logging/1.25.0/opentelemetry-exporter-logging-1.25.0.jar:/Users/xxxxx/.m2/repository/io/opentelemetry/opentelemetry-sdk-metrics/1.25.0/opentelemetry-sdk-metrics-1.25.0.jar:/Users/xxxxx/.m2/repository/io/opentelemetry/opentelemetry-sdk-logs/1.25.0-alpha/opentelemetry-sdk-logs-1.25.0-alpha.jar:/Users/xxxxx/.m2/repository/io/opentelemetry/opentelemetry-api-logs/1.25.0-alpha/opentelemetry-api-logs-1.25.0-alpha.jar:/Users/xxxxx/.m2/repository/io/opentelemetry/opentelemetry-api-events/1.25.0-alpha/opentelemetry-api-events-1.25.0-alpha.jar:/Users/xxxxx/.m2/repository/io/opentelemetry/opentelemetry-sdk-common/1.25.0/opentelemetry-sdk-common-1.25.0.jar:/Users/xxxxx/.m2/repository/io/opentelemetry/opentelemetry-sdk-extension-autoconfigure-spi/1.25.0/opentelemetry-sdk-extension-autoconfigure-spi-1.25.0.jar:/Users/xxxxx/.m2/repository/io/opentelemetry/opentelemetry-sdk-extension-autoconfigure/1.25.0-alpha/opentelemetry-sdk-extension-autoconfigure-1.25.0-alpha.jar:/Users/xxxxx/.m2/repository/io/opentelemetry/opentelemetry-sdk-trace/1.25.0/opentelemetry-sdk-trace-1.25.0.jar:/Users/xxxxx/.m2/repository/io/opentelemetry/opentelemetry-sdk/1.25.0/opentelemetry-sdk-1.25.0.jar:/Users/xxxxx/.m2/repository/io/opentelemetry/opentelemetry-semconv/1.25.0-alpha/opentelemetry-semconv-1.25.0-alpha.jar:/Users/xxxxx/.m2/repository/io/ous/jtoml/2.0.0/jtoml-2.0.0.jar:/Users/xxxxx/.m2/repository/net/bytebuddy/byte-buddy/1.14.4/byte-buddy-1.14.4.jar:/Users/xxxxx/.m2/repository/org/apache/commons/commons-exec/1.3/commons-exec-1.3.jar:/Users/xxxxx/.m2/repository/org/asynchttpclient/async-http-client/2.12.3/async-http-client-2.12.3.jar:/Users/xxxxx/.m2/repository/org/asynchttpclient/async-http-client-netty-utils/2.12.3/async-http-client-netty-utils-2.12.3.jar:/Users/xxxxx/.m2/repository/io/netty/netty-codec-socks/4.1.60.Final/netty-codec-socks-4.1.60.Final.jar:/Users/xxxxx/.m2/repository/io/netty/netty-handler-proxy/4.1.60.Final/netty-handler-proxy-4.1.60.Final.jar:/Users/xxxxx/.m2/repository/io/netty/netty-transport-native-epoll/4.1.60.Final/netty-transport-native-epoll-4.1.60.Final-linux-x86_64.jar:/Users/xxxxx/.m2/repository/io/netty/netty-transport-native-kqueue/4.1.60.Final/netty-transport-native-kqueue-4.1.60.Final-osx-x86_64.jar:/Users/xxxxx/.m2/repository/org/reactivestreams/reactive-streams/1.0.3/reactive-streams-1.0.3.jar:/Users/xxxxx/.m2/repository/com/typesafe/netty/netty-reactive-streams/2.0.4/netty-reactive-streams-2.0.4.jar:/Users/xxxxx/.m2/repository/com/sun/activation/jakarta.activation/1.2.2/jakarta.activation-1.2.2.jar:/Users/xxxxx/.m2/repository/org/seleniumhq/selenium/selenium-http/4.9.1/selenium-http-4.9.1.jar:/Users/xxxxx/.m2/repository/dev/failsafe/failsafe/3.3.1/failsafe-3.3.1.jar:/Users/xxxxx/.m2/repository/org/seleniumhq/selenium/selenium-json/4.9.1/selenium-json-4.9.1.jar:/Users/xxxxx/.m2/repository/org/seleniumhq/selenium/selenium-manager/4.9.1/selenium-manager-4.9.1.jar:/Users/xxxxx/.m2/repository/org/seleniumhq/selenium/selenium-support/4.9.1/selenium-support-4.9.1.jar:/Users/xxxxx/.m2/repository/com/google/code/gson/gson/2.10.1/gson-2.10.1.jar:/Users/xxxxx/.m2/repository/cglib/cglib/3.3.0/cglib-3.3.0.jar:/Users/xxxxx/.m2/repository/org/ow2/asm/asm/7.1/asm-7.1.jar:/Users/xxxxx/.m2/repository/commons-validator/commons-validator/1.7/commons-validator-1.7.jar:/Users/xxxxx/.m2/repository/commons-beanutils/commons-beanutils/1.9.4/commons-beanutils-1.9.4.jar:/Users/xxxxx/.m2/repository/commons-digester/commons-digester/2.1/commons-digester-2.1.jar:/Users/xxxxx/.m2/repository/commons-logging/commons-logging/1.2/commons-logging-1.2.jar:/Users/xxxxx/.m2/repository/commons-collections/commons-collections/3.2.2/commons-collections-3.2.2.jar:/Users/xxxxx/.m2/repository/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar com.intellij.rt.testng.RemoteTestNGStarter -usedefaultlisteners false -socket49157 @w@/private/var/folders/zf/szvqh30s50g5f_hwrqxz8c740000gn/T/idea_working_dirs_testng.tmp -temp /private/var/folders/zf/szvqh30s50g5f_hwrqxz8c740000gn/T/idea_testng.tmp

SLF4J: Failed to load class “org.slf4j.impl.StaticLoggerBinder”.

SLF4J: Defaulting to no-operation (NOP) logger implementation

SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

[Appium] Welcome to Appium v2.0.0-beta.71

[Appium] Non-default server args:

[Appium] { address: ‘127.0.0.1’ }

[Appium] Attempting to load driver uiautomator2…

[debug] [Appium] Requiring driver at /Users/xxxxx/.appium/node_modules/appium-uiautomator2-driver

[Appium] Attempting to load driver xcuitest…

[debug] [Appium] Requiring driver at /Users/xxxxx/.appium/node_modules/appium-xcuitest-driver

[Appium] Attempting to load driver gecko…

[debug] [Appium] Requiring driver at /Users/xxxxx/.appium/node_modules/appium-geckodriver

[Appium] Appium REST http interface listener started on 127.0.0.1:4723

[Appium] Available drivers:

[Appium] - [email protected] (automationName ‘UiAutomator2’)

[Appium] - [email protected] (automationName ‘XCUITest’)

[Appium] - [email protected] (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@b8b5] Calling AppiumDriver.getStatus() with args: []

[debug] [AppiumDriver@b8b5] Responding to client with driver.getStatus() result: {“build”:{“version”:“2.0.0-beta.71”}}

[HTTP] <-- GET /status 200 6 ms - 47

[HTTP]

---------check test------

---------apk test------

[debug] [HTTP] Request idempotency key: 17aaad63-46db-47d5-aa80-56e2e9a0f0ac

[HTTP] --> POST /session

[HTTP] {“capabilities”:{“firstMatch”:[{}],“alwaysMatch”:{“appium:app”:"//Users//xxxxx//IdeaProjects//Test//src//test//utils//xxxxx.apk",“appium:automationName”:“UIAutomator2”,“appium:deviceName”:“Pixel5_S”,“platformName”:“ANDROID”}}}

[debug] [AppiumDriver@b8b5] Calling AppiumDriver.createSession() with args: [null,null,{“firstMatch”:[{}],“alwaysMatch”:{“appium:app”:"//Users//xxxxx//IdeaProjects//Test//src//test//utils//xxxxx.apk",“appium:automationName”:“UIAutomator2”,“appium:deviceName”:“Pixel5_S”,“platformName”:“ANDROID”}}]

[debug] [AppiumDriver@b8b5] Event ‘newSessionRequested’ logged at 1685877388204 (13:16:28 GMT+0200 (Central European Summer 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 /Users/xxxxx/.appium/node_modules/appium-uiautomator2-driver

[debug] [Appium] Requiring driver at /Users/xxxxx/.appium/node_modules/appium-uiautomator2-driver

[AppiumDriver@b8b5] Appium v2.0.0-beta.71 creating new AndroidUiautomator2Driver (v2.25.1) session

[AppiumDriver@b8b5] Checking BaseDriver versions for Appium and AndroidUiautomator2Driver

[AppiumDriver@b8b5] Appium’s BaseDriver version is 9.3.10

[AppiumDriver@b8b5] AndroidUiautomator2Driver’s BaseDriver version is 9.3.10

[debug] [AndroidUiautomator2Driver@a633] Creating session with W3C capabilities: {

[debug] [AndroidUiautomator2Driver@a633] “alwaysMatch”: {

[debug] [AndroidUiautomator2Driver@a633] “platformName”: “ANDROID”,

[debug] [AndroidUiautomator2Driver@a633] “appium:app”: “//Users//xxxxx//IdeaProjects//Test//src//test//utils//xxxxx.apk”,

[debug] [AndroidUiautomator2Driver@a633] “appium:automationName”: “UIAutomator2”,

[debug] [AndroidUiautomator2Driver@a633] “appium:deviceName”: “Pixel5_S”

[debug] [AndroidUiautomator2Driver@a633] },

[debug] [AndroidUiautomator2Driver@a633] “firstMatch”: [

[debug] [AndroidUiautomator2Driver@a633] {}

[debug] [AndroidUiautomator2Driver@a633] ]

[debug] [AndroidUiautomator2Driver@a633] }

[AndroidUiautomator2Driver@a633 (1c8cd596)] Session created with session id: 1c8cd596-edc7-4b07-9846-490af1081fd6

[BaseDriver] Using local app ‘//Users//xxxxx//IdeaProjects//Test//src//test//utils//xxxxx.apk’

[debug] [AndroidUiautomator2Driver@a633 (1c8cd596)] Checking whether app is actually present

[ADB] Found 2 ‘build-tools’ folders under ‘/Users/xxxxx/Library/Android/sdk’ (newest first):

[ADB] /Users/xxxxx/Library/Android/sdk/build-tools/33.0.2

[ADB] /Users/xxxxx/Library/Android/sdk/build-tools/30.0.3

[ADB] Using ‘adb’ from ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb’

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -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’ from ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb’

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 start-server’

[debug] [ADB] Setting device id to emulator-5554

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell getprop ro.build.version.sdk’

[debug] [ADB] Current device property ‘ro.build.version.sdk’: 31

[ADB] Getting device platform version

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell getprop ro.build.version.release’

[debug] [ADB] Current device property ‘ro.build.version.release’: 12

[debug] [ADB] Device API level: 31

[AndroidUiautomator2Driver@a633 (1c8cd596)] Relaxing hidden api policy

[debug] [ADB] Running ‘/Users/xxxxx/Library/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] [AndroidDriver] Parsing package and activity from app manifest

[ADB] Package name: ‘xxxxx.’

[ADB] Main activity name: ‘crc64d9778aefdd3ea714.SplashActivity’

[debug] [AndroidDriver] Parsed package and activity are: xxxxx./crc64d9778aefdd3ea714.SplashActivity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 wait-for-device’

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -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 ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -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 ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -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 (‘5.0.3’ >= ‘5.0.3’)

[debug] [ADB] There is no need to install/upgrade ‘/Users/xxxxx/.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 ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell ‘pgrep --help; echo $?’’

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -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: /Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 logcat -v threadtime

[debug] [AndroidUiautomator2Driver@a633 (1c8cd596)] Forwarding UiAutomator2 Server port 6790 to local port 8200

[debug] [ADB] Forwarding system: 8200 to device: 6790

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 forward tcp:8200 tcp:6790’

[AndroidUiautomator2Driver@a633 (1c8cd596)] Server package at ‘/Users/xxxxx/.appium/node_modules/appium-uiautomator2-driver/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-v5.8.2.apk’ is not writeable. Will copy it into the temporary location at ‘/var/folders/zf/szvqh30s50g5f_hwrqxz8c740000gn/T/202354-17966-x87ait.rbl5’ as a workaround. Consider making this file writeable manually in order to improve the performance of session startup.

[AndroidUiautomator2Driver@a633 (1c8cd596)] Server package at ‘/Users/xxxxx/.appium/node_modules/appium-uiautomator2-driver/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-debug-androidTest.apk’ is not writeable. Will copy it into the temporary location at ‘/var/folders/zf/szvqh30s50g5f_hwrqxz8c740000gn/T/202354-17966-x87ait.rbl5’ as a workaround. Consider making this file writeable manually in order to improve the performance of session startup.

[debug] [ADB] Getting install status for io.appium.uiautomator2.server

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -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 ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -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.8.2’ >= ‘5.8.2’)

[debug] [AndroidUiautomator2Driver@a633 (1c8cd596)] io.appium.uiautomator2.server installation state: sameVersionInstalled

[debug] [ADB] Checking app cert for /var/folders/zf/szvqh30s50g5f_hwrqxz8c740000gn/T/202354-17966-x87ait.rbl5/appium-uiautomator2-server-v5.8.2.apk

[ADB] Using ‘apksigner.jar’ from ‘/Users/xxxxx/Library/Android/sdk/build-tools/33.0.2/lib/apksigner.jar’

[debug] [ADB] Starting apksigner: /Library/Java/JavaVirtualMachines/jdk-20.jdk/Contents/Home/bin/java -Xmx1024M -Xss1m -jar /Users/xxxxx/Library/Android/sdk/build-tools/33.0.2/lib/apksigner.jar verify --print-certs /var/folders/zf/szvqh30s50g5f_hwrqxz8c740000gn/T/202354-17966-x87ait.rbl5/appium-uiautomator2-server-v5.8.2.apk

[debug] [ADB] apksigner stdout: Signer #1 certificate DN: [email protected], 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.8.2.apk’

[ADB] ‘/var/folders/zf/szvqh30s50g5f_hwrqxz8c740000gn/T/202354-17966-x87ait.rbl5/appium-uiautomator2-server-v5.8.2.apk’ is signed with the default certificate

[debug] [ADB] Getting install status for io.appium.uiautomator2.server.test

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -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 /var/folders/zf/szvqh30s50g5f_hwrqxz8c740000gn/T/202354-17966-x87ait.rbl5/appium-uiautomator2-server-debug-androidTest.apk

[debug] [ADB] Starting apksigner: /Library/Java/JavaVirtualMachines/jdk-20.jdk/Contents/Home/bin/java -Xmx1024M -Xss1m -jar /Users/xxxxx/Library/Android/sdk/build-tools/33.0.2/lib/apksigner.jar verify --print-certs /var/folders/zf/szvqh30s50g5f_hwrqxz8c740000gn/T/202354-17966-x87ait.rbl5/appium-uiautomator2-server-debug-androidTest.apk

[debug] [ADB] apksigner stdout: Signer #1 certificate DN: [email protected], 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] ‘/var/folders/zf/szvqh30s50g5f_hwrqxz8c740000gn/T/202354-17966-x87ait.rbl5/appium-uiautomator2-server-debug-androidTest.apk’ is signed with the default certificate

[AndroidUiautomator2Driver@a633 (1c8cd596)] Server packages are not going to be (re)installed

[debug] [AndroidUiautomator2Driver@a633 (1c8cd596)] Waiting up to 30000ms for services to be available

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell pm list instrumentation’

[debug] [AndroidUiautomator2Driver@a633 (1c8cd596)] 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 ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -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 //Users//xxxxx//IdeaProjects//Test//src//test//utils//xxxxx.apk

[debug] [ADB] Starting apksigner: /Library/Java/JavaVirtualMachines/jdk-20.jdk/Contents/Home/bin/java -Xmx1024M -Xss1m -jar /Users/xxxxx/Library/Android/sdk/build-tools/33.0.2/lib/apksigner.jar verify --print-certs //Users//xxxxx//IdeaProjects//Test//src//test//utils//xxxxx.apk

[debug] [ADB] apksigner stdout: Signer #1 certificate DN: CN=Android Debug, O=Android, C=US

[debug] [ADB] Signer #1 certificate SHA-256 digest: 1c581f7b9a58c511e3f23c8c2635a967c90fef1791ddecdbdea8993f5db6d9c1

[debug] [ADB] Signer #1 certificate SHA-1 digest: a8b7da645295f1ad50ee1380f4245b47faa0e5e6

[debug] [ADB] Signer #1 certificate MD5 digest: 4a899ed10ae3e954046c868f25ca18d8

[debug] [ADB]

[ADB] ‘//Users//xxxxx//IdeaProjects//Test//src//test//utils//xxxxx.apk’ is signed with a non-default certificate

[debug] [ADB] Getting install status for xxxxx.

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys package xxxxx.’

[debug] [ADB] ‘xxxxx.’ is installed

[debug] [ADB] Getting package info for ‘xxxxx.’

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys package xxxxx.’

[debug] [ADB] The version name of the installed ‘xxxxx.’ is greater or equal to the application version name (‘2.52.0’ >= ‘2.52.0’)

[debug] [ADB] There is no need to install/upgrade ‘//Users//xxxxx//IdeaProjects//Test//src//test//utils//xxxxx.apk’

[AndroidDriver] Performing fast reset on ‘xxxxx.’

[debug] [ADB] Getting install status for xxxxx.

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys package xxxxx.’

[debug] [ADB] ‘xxxxx.’ is installed

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell am force-stop xxxxx.’

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell pm clear xxxxx.’

[debug] [AndroidDriver] Performed fast reset on the installed ‘xxxxx.’ application (stop and clear)

[debug] [AndroidUiautomator2Driver@a633 (1c8cd596)] Performing shallow cleanup of automation leftovers

[debug] [AndroidUiautomator2Driver@a633 (1c8cd596)] No obsolete sessions have been detected

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell am force-stop io.appium.uiautomator2.server.test’

[AndroidUiautomator2Driver@a633 (1c8cd596)] Starting UIAutomator2 server 5.8.2

[AndroidUiautomator2Driver@a633 (1c8cd596)] Using UIAutomator2 server from ‘/Users/xxxxx/.appium/node_modules/appium-uiautomator2-driver/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-v5.8.2.apk’ and test from ‘/Users/xxxxx/.appium/node_modules/appium-uiautomator2-driver/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-debug-androidTest.apk’

[AndroidUiautomator2Driver@a633 (1c8cd596)] 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@a633 (1c8cd596)] Matched ‘/status’ to command name ‘getStatus’

[debug] [AndroidUiautomator2Driver@a633 (1c8cd596)] Proxying [GET /status] to [GET http://127.0.0.1:8200/status] with no body

[debug] [AndroidUiautomator2Driver@a633 (1c8cd596)] Got response with status 200: {“sessionId”:“None”,“value”:{“message”:“UiAutomator2 Server is ready to accept commands”,“ready”:true}}

[debug] [AndroidUiautomator2Driver@a633 (1c8cd596)] The initialization of the instrumentation process took 49ms

[debug] [AndroidUiautomator2Driver@a633 (1c8cd596)] Matched ‘/session’ to command name ‘createSession’

[debug] [AndroidUiautomator2Driver@a633 (1c8cd596)] 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”:"//Users//xxxxx//IdeaProjects//Test//src//test//utils//xxxxx.apk",“automationName”:“UIAutomator2”,“deviceName”:“Pixel5_S”},“platformName”:“ANDROID”,“app”:"//Users//xxxxx//IdeaProjects//Test//src//test//utils//xxxxx.apk",“automationName”:“UIAutomator2”,“deviceName”:“emulator-5554”,“deviceUDID”:“emulator-5554”,“appPackage”:“xxxxx.”}],“alwaysMatch”:{}}}

[debug] [AndroidUiautomator2Driver@a633 (1c8cd596)] Got response with status 200: {“sessionId”:“fe94d369-189e-4231-b729-bbd756dcf29b”,“value”:{“capabilities”:{“firstMatch”:[{“platform”:“LINUX”,“webStorageEnabled”:false,“takesScreenshot”:true,“javascriptEnabled”:true,“databaseEnabled”:false,“networkConnectionEnabled”:true,“locationContextEnabled”:false,“warnings”:{},“desired”:{“platformName”:“ANDROID”,“app”:"//Users//xxxxx//IdeaProjects//Test//src//test//utils//xxxxx.apk",“automationName”:“UIAutomator2”,“deviceName”:“Pixel5_S”},“platformName”:“ANDROID”,“app”:"//Users//xxxxx//IdeaProjects//Test//src//test//utils//xxxxx.apk",“automationName”:“UIAutomator2”,“deviceName”:“emulator-5554”,“deviceUDID”:“emulator-5554”,“appPackage”:“xxxxx.”}],“alwaysMatch”:{}},“sessionId”:“fe94d369-189e-4231-b729-bbd756dcf29b”}}

[AndroidUiautomator2Driver@a633 (1c8cd596)] Determined the downstream protocol as ‘W3C’

[debug] [AndroidUiautomator2Driver@a633 (1c8cd596)] Proxying [GET /appium/device/info] to [GET http://127.0.0.1:8200/session/fe94d369-189e-4231-b729-bbd756dcf29b/appium/device/info] with no body

[debug] [AndroidUiautomator2Driver@a633 (1c8cd596)] Got response with status 200: {“sessionId”:“fe94d369-189e-4231-b729-bbd756dcf29b”,“value”:{“androidId”:“5768b89f66f1cfb7”,“apiVersion”:“31”,“bluetooth”:{“state”:“ON”},“brand”:“google”,“carrierName”:“T-Mobile”,“displayDensity”:440,“locale”:“en_US”,“manufacturer”:“Google”,“model”:“sdk_gphone64_x86_64”,“networks”:[{“capabilities”:{“SSID”:null,“linkDownBandwidthKbps”:4300,“linkUpstreamBandwidthKbps”:1800,“networkCapabilities”:“NET_CAPABILITY_MMS,NET_CAPABILITY_SUPL,NET_CAPABILITY_DUN,NET_CAPABILITY_FOTA,NET_CAPABILITY_IMS,NET_CAPABILITY_CBS,NET_CAPABILITY_INTERNET,NET_CAPABILITY_NOT_RESTRICTED,NET_CAPABILITY_TRUSTED,NET_CAPABILITY_NOT_VPN,NET_CAPABILITY_VALIDATED,NET_CAPABILITY_NOT_ROAMING,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”:10,“subtypeName”:“HSPA”,“type”:0,“typeName”:“MOBILE”},{"capabiliti…

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window’

[AndroidDriver] Screen already unlocked, doing nothing

[AndroidUiautomator2Driver@a633 (1c8cd596)] Starting 'xxxxx./crc64d9778aefdd3ea714.SplashActivity and waiting for ‘xxxxx./crc64d9778aefdd3ea714.SplashActivity’

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell am start -W -n xxxxx./crc64d9778aefdd3ea714.SplashActivity -S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000’

[debug] [Instrumentation] io.appium.uiautomator2.server.test.AppiumUiAutomator2Server:

[debug] [ADB] Waiting up to 20000ms for activity matching pkg: ‘xxxxx.’ and activity: ‘crc64d9778aefdd3ea714.SplashActivity’ to be focused

[debug] [ADB] Possible activities, to be checked: ‘crc64d9778aefdd3ea714.SplashActivity’, ‘xxxxx…crc64d9778aefdd3ea714.SplashActivity’

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [ADB] Getting focused package and activity

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys window displays’

[debug] [ADB] Found package: ‘xxxxx.’ and fully qualified activity name : ‘crc64d9778aefdd3ea714.MainActivity’

[debug] [ADB] Incorrect package and activity. Retrying.

[debug] [AndroidUiautomator2Driver@a633 (1c8cd596)] Deleting UiAutomator2 session

[debug] [AndroidUiautomator2Driver@a633 (1c8cd596)] Deleting UiAutomator2 server session

[debug] [AndroidUiautomator2Driver@a633 (1c8cd596)] Matched ‘/’ to command name ‘deleteSession’

[debug] [AndroidUiautomator2Driver@a633 (1c8cd596)] Proxying [DELETE /] to [DELETE http://127.0.0.1:8200/session/fe94d369-189e-4231-b729-bbd756dcf29b] with no body

[AndroidUiautomator2Driver@a633 (1c8cd596)] Got response with status 404: {“sessionId”:“fe94d369-189e-4231-b729-bbd756dcf29b”,“value”:{“error”:“invalid session id”,“message”:“The session identified by fe94d369-189e-4231-b729-bbd756dcf29b is not known”,“stacktrace”:"io.appium.uiautomator2.common.exceptions.NoSuchDriverException: The session identified by fe94d369-189e-4231-b729-bbd756dcf29b is not known\n\tat io.appium.uiautomator2.handler.request.SafeRequestHandler.handle(SafeRequestHandler.java:54)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleRequest(AppiumServlet.java:270)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleHttpRequest(AppiumServlet.java:264)\n\tat io.appium.uiautomator2.http.ServerHandler.channelRead(ServerHandler.java:68)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:366)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:352)\n\tat io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:3…

[debug] [W3C] Matched W3C error code ‘invalid session id’ to NoSuchDriverError

[AndroidUiautomator2Driver@a633 (1c8cd596)] Did not get confirmation UiAutomator2 deleteSession worked; Error was: NoSuchDriverError: The session identified by fe94d369-189e-4231-b729-bbd756dcf29b is not known

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell dumpsys activity services io.appium.settings/.recorder.RecorderService’

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 shell am force-stop xxxxx.’

[debug] [Logcat] Stopping logcat capture

[debug] [ADB] Removing forwarded port socket connection: 8200

[debug] [ADB] Running ‘/Users/xxxxx/Library/Android/sdk/platform-tools/adb -P 5037 -s emulator-5554 forward --remove tcp:8200’

[AndroidUiautomator2Driver@a633 (1c8cd596)] Restoring hidden api policy to the device default configuration

[debug] [ADB] Running ‘/Users/xxxxx/Library/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] [AppiumDriver@b8b5] Event ‘newSessionStarted’ logged at 1685877430311 (13:17:10 GMT+0200 (Central European Summer Time))

[debug] [AppiumDriver@b8b5] Encountered internal error running command: Error: Cannot start the ‘xxxxx.’ application. Consider checking the driver’s troubleshooting documentation. Original error: ‘crc64d9778aefdd3ea714.SplashActivity’ or ‘xxxxx…crc64d9778aefdd3ea714.SplashActivity’ never started. Consider checking the driver’s troubleshooting documentation.

[debug] [AppiumDriver@b8b5] at ADB.startApp (/Users/xxxxx/.appium/node_modules/appium-uiautomator2-driver/node_modules/appium-adb/lib/tools/apk-utils.js:177:11)

[debug] [AppiumDriver@b8b5] at AndroidUiautomator2Driver.ensureAppStarts (/Users/xxxxx/.appium/node_modules/appium-uiautomator2-driver/lib/driver.js:587:5)

[debug] [AppiumDriver@b8b5] at AndroidUiautomator2Driver.startUiAutomator2Session (/Users/xxxxx/.appium/node_modules/appium-uiautomator2-driver/lib/driver.js:442:7)

[debug] [AppiumDriver@b8b5] at AndroidUiautomator2Driver.createSession (/Users/xxxxx/.appium/node_modules/appium-uiautomator2-driver/lib/driver.js:240:7)

[debug] [AppiumDriver@b8b5] at AppiumDriver.createSession (/usr/local/lib/node_modules/appium/lib/appium.js:346:35)

[HTTP] <-- POST /session 500 42200 ms - 1158

[HTTP]

org.openqa.selenium.SessionNotCreatedException: 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 ‘xxxxx.’ application. Consider checking the driver’s troubleshooting documentation. Original error: ‘crc64d9778aefdd3ea714.SplashActivity’ or ‘xxxxx…crc64d9778aefdd3ea714.SplashActivity’ never started. Consider checking the driver’s troubleshooting documentation.

Host info: host: ‘xxxxxxxxx’, ip: ‘fe80:0:0:0:c13:71c0:3537:4443%en0’

Build info: version: ‘4.9.1’, revision: ‘eb2032df7f’

System info: os.name: ‘Mac OS X’, os.arch: ‘x86_64’, os.version: ‘13.4’, java.version: ‘18.0.2.1’

Driver info: io.appium.java_client.android.AndroidDriver

Command: [null, newSession {capabilities=[{appium:deviceName=Pixel5_S, platformName=ANDROID, appium:automationName=UIAutomator2, appium:app=//Users//xxxxx//IdeaProjects//Test//src//test//utils//xxxxx.apk}], desiredCapabilities=Capabilities {appium:app: //Users//xxxxx//Idea…, appium:automationName: UIAutomator2, appium:deviceName: Pixel5_S, platformName: ANDROID}}]

Capabilities {appium:app: //Users//xxxxx//Idea…, appium:automationName: UIAutomator2, appium:deviceName: Pixel5_S, platformName: ANDROID}

at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:136)

at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)

at java.base/java.lang.reflect.Method.invoke(Method.java:577)

at io.appium.java_client.remote.AppiumProtocolHandshake.createSession(AppiumProtocolHandshake.java:133)

at io.appium.java_client.remote.AppiumProtocolHandshake.createSession(AppiumProtocolHandshake.java:102)

at io.appium.java_client.remote.AppiumCommandExecutor.createSession(AppiumCommandExecutor.java:182)

at io.appium.java_client.remote.AppiumCommandExecutor.execute(AppiumCommandExecutor.java:250)

at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:543)

at io.appium.java_client.AppiumDriver.startSession(AppiumDriver.java:274)

at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:157)

at io.appium.java_client.AppiumDriver.(AppiumDriver.java:89)

at io.appium.java_client.AppiumDriver.(AppiumDriver.java:101)

at io.appium.java_client.android.AndroidDriver.(AndroidDriver.java:113)

at xxxx.connectionTest(oneSprayerConnection.java:37)

at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)

at java.base/java.lang.reflect.Method.invoke(Method.java:577)

at org.testng.internal.invokers.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:139)

at org.testng.internal.invokers.TestInvoker.invokeMethod(TestInvoker.java:664)

at org.testng.internal.invokers.TestInvoker.invokeTestMethod(TestInvoker.java:227)

at org.testng.internal.invokers.MethodRunner.runInSequence(MethodRunner.java:50)

at org.testng.internal.invokers.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:957)

at org.testng.internal.invokers.TestInvoker.invokeTestMethods(TestInvoker.java:200)

at org.testng.internal.invokers.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:148)

at org.testng.internal.invokers.TestMethodWorker.run(TestMethodWorker.java:128)

at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)

at org.testng.TestRunner.privateRun(TestRunner.java:848)

at org.testng.TestRunner.run(TestRunner.java:621)

at org.testng.SuiteRunner.runTest(SuiteRunner.java:443)

at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:437)

at org.testng.SuiteRunner.privateRun(SuiteRunner.java:397)

at org.testng.SuiteRunner.run(SuiteRunner.java:336)

at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)

at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:95)

at org.testng.TestNG.runSuitesSequentially(TestNG.java:1280)

at org.testng.TestNG.runSuitesLocally(TestNG.java:1200)

at org.testng.TestNG.runSuites(TestNG.java:1114)

at org.testng.TestNG.run(TestNG.java:1082)

at com.intellij.rt.testng.IDEARemoteTestNG.run(IDEARemoteTestNG.java:66)

at com.intellij.rt.testng.RemoteTestNGStarter.main(RemoteTestNGStarter.java:109)

===============================================

Default Suite

Total tests run: 1, Passes: 0, Failures: 1, Skips: 0

===============================================

Process finished with exit code 0Hi Team
need an help, i am able to launch the app but after that it close immediately without clicking on locators. Not sure what is wrong.
java -version

java version “20.0.1” 2023-04-18

Java™ SE Runtime Environment (build 20.0.1+9-29)

Java HotSpot™ 64-Bit Server VM (build 20.0.1+9-29, mixed mode, sharing)

appium -version :

2.0.0-beta.71
appium driver list
Listing available drivers

[email protected] [installed (npm)]
[email protected] [installed (npm)]
[email protected] [installed (npm)]
mac2 [not installed]
espresso [not installed]
safari [not installed]
chromium [not installed]

Appium-doctor

WARN AppiumDoctor [Deprecated] Please use appium-doctor installed with “npm install @appium/doctor --location=global”

info AppiumDoctor Appium Doctor v.1.16.2

info AppiumDoctor ### Diagnostic for necessary dependencies starting ###

info AppiumDoctor The Node.js binary was found at: /usr/local/bin/node

info AppiumDoctor Node version is 14.21.3

WARN AppiumDoctor Error running xcrun simctl

info AppiumDoctor Xcode Command Line Tools are installed in: /Applications/Xcode.app/Contents/Developer

info AppiumDoctor DevToolsSecurity is enabled.

info AppiumDoctor The Authorization DB is set up properly.

WARN AppiumDoctor Carthage was NOT found!

info AppiumDoctor HOME is set to: /Users/xxxxxx

info AppiumDoctor ANDROID_HOME is set to: /Users/xxxxxx/Library/Android/sdk

info AppiumDoctor JAVA_HOME is set to: /Library/Java/JavaVirtualMachines/jdk-20.jdk/Contents/Home

info AppiumDoctor Checking adb, android, emulator, apkanalyzer

info AppiumDoctor ‘adb’ is in /Users/xxxxxx/Library/Android/sdk/platform-tools/adb

info AppiumDoctor ‘android’ is in /Users/xxxxxx/Library/Android/sdk/tools/android

info AppiumDoctor ‘emulator’ is in /Users/xxxxxx/Library/Android/sdk/emulator/emulator

info AppiumDoctor ‘apkanalyzer’ is in /Users/xxxxxx/Library/Android/sdk/tools/bin/apkanalyzer

info AppiumDoctor adb, android, emulator, apkanalyzer exist: /Users/xxxxxx/Library/Android/sdk

info AppiumDoctor ‘bin’ subfolder exists under ‘/Library/Java/JavaVirtualMachines/jdk-20.jdk/Contents/Home’

info AppiumDoctor ### Diagnostic for necessary dependencies completed, 2 fixes needed. ###

info AppiumDoctor

info AppiumDoctor ### Diagnostic for optional dependencies starting ###

WARN AppiumDoctor opencv4nodejs cannot be found.

WARN AppiumDoctor ffmpeg cannot be found

WARN AppiumDoctor mjpeg-consumer cannot be found.

WARN AppiumDoctor set-simulator-location is not installed

WARN AppiumDoctor idb and idb_companion are not installed

WARN AppiumDoctor applesimutils cannot be found

WARN AppiumDoctor ios-deploy cannot be found

WARN AppiumDoctor bundletool.jar cannot be found

WARN AppiumDoctor gst-launch-1.0 and/or gst-inspect-1.0 cannot be found

info AppiumDoctor ### Diagnostic for optional dependencies completed, 9 fixes possible. ###

info AppiumDoctor

info AppiumDoctor ### Manual Fixes Needed ###

info AppiumDoctor The configuration cannot be automatically fixed, please do the following first:

WARN AppiumDoctor ➜ Manually install Xcode , and make sure ‘xcode-select -p’ command shows proper path like ‘/Applications/Xcode.app/Contents/Developer’

WARN AppiumDoctor ➜ [For lower than Appium 1.20.0] Please install Carthage . Visit https://github.com/Carthage/Carthage#installing-carthage for more information.

info AppiumDoctor

info AppiumDoctor ### Optional Manual Fixes ###

info AppiumDoctor The configuration can install optionally. Please do the following manually:

WARN AppiumDoctor ➜ Why opencv4nodejs is needed and how to install it: http://appium.io/docs/en/writing-running-appium/image-comparison/

WARN AppiumDoctor ➜ ffmpeg is needed to record screen features. Please read https://www.ffmpeg.org/ to install it

WARN AppiumDoctor ➜ mjpeg-consumer module is required to use MJPEG-over-HTTP features. Please install it with ‘npm i -g mjpeg-consumer’.

WARN AppiumDoctor ➜ set-simulator-location is needed to set location for Simulator. Please read https://github.com/lyft/set-simulator-location to install it

WARN AppiumDoctor ➜ Why idb is needed and how to install it: https://github.com/appium/appium-idb

WARN AppiumDoctor ➜ Why applesimutils is needed and how to install it: http://appium.io/docs/en/drivers/ios-xcuitest/

WARN AppiumDoctor ➜ ios-deploy is used as a fallback command to install iOS applications to real device. Please read https://github.com/ios-control/ios-deploy/ to install it

WARN AppiumDoctor ➜ bundletool.jar is used to handle Android App Bundle. Please read http://appium.io/docs/en/writing-running-appium/android/android-appbundle/ to install it

WARN AppiumDoctor ➜ gst-launch-1.0 and gst-inspect-1.0 are used to stream the screen of the device under test. Please read https://appium.io/docs/en/writing-running-appium/android/android-screen-streaming/ to install them and for more details

info AppiumDoctor

info AppiumDoctor ###

info AppiumDoctor

info AppiumDoctor Bye! Run appium-doctor again when all manual fixes have been applied!