Hi. After I start mobile spy, my app loads and shown in Device View screen. But when I click Login Button its not going to next screen. Nothing happens. Below is the trace before my app loads:
e[35m[Appium]e[39m Welcome to Appium v1.8.1
e[35m[Appium]e[39m Non-default server args:
e[35m[Appium]e[39m port: 50793
e[35m[Appium]e[39m loglevel: info
e[35m[Appium]e[39m chromeDriverPort: 50796
e[35m[Appium]e[39m tmpDir: C:\Users\NoName\AppData\Local\Temp\\Katalon\Appium\Temp1533789530464
e[35m[Appium]e[39m Appium REST http interface listener started on 0.0.0.0:50793
e[35m[HTTP]e[39m e[37m–>e[39m e[37mGETe[39m e[37m/wd/hub/statuse[39m
e[35m[HTTP]e[39m e[90m{}e[39m
e[35m[HTTP]e[39m e[37m<-- GET /wd/hub/status e[39me[32m200e[39m e[90m28 ms - 83e[39m
e[35m[HTTP]e[39m e[90me[39m
e[35m[HTTP]e[39m e[37m–>e[39m e[37mGETe[39m e[37m/wd/hub/statuse[39m
e[35m[HTTP]e[39m e[90m{}e[39m
e[35m[HTTP]e[39m e[37m<-- GET /wd/hub/status e[39me[32m200e[39m e[90m23 ms - 83e[39m
e[35m[HTTP]e[39m e[90me[39m
e[35m[HTTP]e[39m e[37m–>e[39m e[37mPOSTe[39m e[37m/wd/hub/sessione[39m
e[35m[HTTP]e[39m e[90m{“desiredCapabilities”:{“app”:“C:\\Users\\NoName\\Documents\\P\\Digital\\Android App\\ABC_SIT_V1.0.apk”,“autoGrantPermissions”:true,“automationName”:“uiautomator2”,“deviceId”:“90ecfe83”,“deviceName”:“samsung SM-T825Y (Android 7.0)”,“fullReset”:false,“newCommandTimeout”:1800,“noReset”:true,“platform”:“ANDROID”,“platformName”:“Android”,“udid”:“90ecfe83”},“capabilities”:{“desiredCapabilities”:{“app”:“C:\\Users\\NoName\\Documents\\P\\Digital\\Android App\\ABC_SIT_V1.0.apk”,“autoGrantPermissions”:true,“automationName”:“uiautomator2”,“deviceId”:“90ecfe83”,“deviceName”:“samsung SM-T825Y (Android 7.0)”,“fullReset”:false,“newCommandTimeout”:1800,“noReset”:true,“platform”:“ANDROID”,“platformName”:“Android”,“udid”:“90ecfe83”},“firstMatch”:[{“platformName”:“android”}]}}e[39m
e[35m[Appium]e[39m Could not parse W3C capabilities: ‘deviceName’ can’t be blank. Falling back to JSONWP protocol.
e[35m[Appium]e[39m The following capabilities were provided in the JSONWP desired capabilities that are missing in W3C capabilities: [“app”,“autoGrantPermissions”,“automationName”,“deviceId”,“deviceName”,“fullReset”,“newCommandTimeout”,“noReset”,“platform”,“platformName”,“udid”]. Falling back to JSONWP protocol.
e[35m[Appium]e[39m Creating new AndroidUiautomator2Driver (v1.12.0) session
e[35m[Appium]e[39m Capabilities:
e[35m[Appium]e[39m app: C:\Users\NoName\Documents\P\Digital\Android App\ABC_SIT_V1.0.apk
e[35m[Appium]e[39m autoGrantPermissions: true
e[35m[Appium]e[39m automationName: uiautomator2
e[35m[Appium]e[39m deviceId: 90ecfe83
e[35m[Appium]e[39m deviceName: samsung SM-T825Y (Android 7.0)
e[35m[Appium]e[39m fullReset: false
e[35m[Appium]e[39m newCommandTimeout: 1800
e[35m[Appium]e[39m noReset: true
e[35m[Appium]e[39m platform: ANDROID
e[35m[Appium]e[39m platformName: Android
e[35m[Appium]e[39m udid: 90ecfe83
e[35m[BaseDriver]e[39m The following capabilities were provided, but are not recognized by appium: deviceId, platform.
e[35m[BaseDriver]e[39m Session created with session id: 8172706f-c1d0-4b4f-91b8-6dcddb2725fd
e[35m[BaseDriver]e[39m Using local app ‘C:\Users\NoName\Documents\P\Digital\Android App\ABC_SIT_V1.0.apk’
e[35m[AndroidDriver]e[39m Java version is: 1.8.0_181
e[35m[ADB]e[39m Checking whether adb is present
e[35m[ADB]e[39m Found 2 ‘build-tools’ folders under ‘C:\Users\NoName\.katalon\tools\android_sdk’ (newest first):
e[35m[ADB]e[39m C:/Users/NoName/.katalon/tools/android_sdk/build-tools/28.0.2
e[35m[ADB]e[39m C:/Users/NoName/.katalon/tools/android_sdk/build-tools/27.0.3
e[35m[ADB]e[39m Using adb.exe from C:\Users\NoName\.katalon\tools\android_sdk\platform-tools\adb.exe
e[35m[AndroidDriver]e[39m Retrieving device list
e[35m[AndroidDriver]e[39m Using device: 90ecfe83
e[35m[ADB]e[39m Using the alternative activity name detection method because of: Could not find apkanalyzer.bat in C:\Users\NoName\.katalon\tools\android_sdk\platform-tools\apkanalyzer.bat,C:\Users\NoName\.katalon\tools\android_sdk\emulator\apkanalyzer.bat,C:\Users\NoName\.katalon\tools\android_sdk\tools\apkanalyzer.bat,C:\Users\NoName\.katalon\tools\android_sdk\tools\bin\apkanalyzer.bat,C:\Users\NoName\.katalon\tools\android_sdk\build-tools\28.0.2\apkanalyzer.bat,C:\Users\NoName\.katalon\tools\android_sdk\build-tools\27.0.3\apkanalyzer.bat. Do you have the Android SDK installed at ‘C:\Users\NoName\.katalon\tools\android_sdk’?
e[35m[ADB]e[39m Checking whether aapt is present
e[35m[ADB]e[39m Using aapt.exe from C:\Users\NoName\.katalon\tools\android_sdk\build-tools\28.0.2\aapt.exe
e[35m[ADB]e[39m Extracting package and launch activity from manifest
e[35m[ADB]e[39m Package name: ‘com.abc.mobile’
e[35m[ADB]e[39m Main activity name: ‘com.abc.mobile.MainActivity’
e[35m[ADB]e[39m Getting device platform version
e[35m[ADB]e[39m Using apksigner.bat from C:\Users\NoName\.katalon\tools\android_sdk\build-tools\28.0.2\apksigner.bat
e[35m[ADB]e[39m Checking whether zipalign is present
e[35m[ADB]e[39m Using zipalign.exe from C:\Users\NoName\.katalon\tools\android_sdk\build-tools\28.0.2\zipalign.exe
e[35m[ADB]e[39m io.appium.uiautomator2.server was successfully uninstalled
e[35m[ADB]e[39m io.appium.uiautomator2.server.test was successfully uninstalled
e[35m[AndroidDriver]e[39m setDeviceLanguageCountry requires language or country.
e[35m[AndroidDriver]e[39m Got language: ‘null’ and country: ‘null’
e[35m[ADB]e[39m Successfully extracted 99 strings from ‘C:\Users\NoName\Documents\P\Digital\Android App\ABC_SIT_V1.0.apk’ resources for ‘(default)’ configuration
e[35m[UiAutomator2]e[39m Starting uiautomator2 server 1.12.0
e[35m[UiAutomator2]e[39m Using UIAutomator2 server from ‘C:\Users\NoName\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v1.12.0.apk’ and test from ‘C:\Users\NoName\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-debug-androidTest.apk’
e[35m[UiAutomator2]e[39m Running command: ‘adb -s 90ecfe83 shell am instrument -w io.appium.uiautomator2.server.test/android.support.test.runner.AndroidJUnitRunner’
e[35m[UiAutomator2]e[39m Waiting up to 20000ms for UiAutomator2 to be online…
e[35m[AndroidDriver]e[39m Screen already unlocked, doing nothing
e[35m[UiAutomator2]e[39m UiAutomator2 did not start the activity we were waiting for, ‘com.abc.mobile/com.abc.mobile.MainActivity’. Starting it ourselves