Not Able to set up mobile device View

I am not able to get the Device View on catalog view. It show NullPointException. Any Leads who can help me with this?

image.png

Please help to post Katalon Studio logs:

1 Like
  • Appium version : v1.9.0

  • Mobile platform/version under test: Oreo (8.1.0)

  • Real device or emulator/simulator: OnePlus One

  • Appium Logs:

e[35m[Appium]e[39m Welcome to Appium v1.9.0

e[35m[Appium]e[39m Non-default server args:

e[35m[Appium]e[39m port: 54807

e[35m[Appium]e[39m loglevel: info

e[35m[Appium]e[39m chromeDriverPort: 54808

e[35m[Appium]e[39m tmpDir: C:\Users\cinesoft\AppData\Local\Temp\\Katalon\Appium\Temp1536557329402

e[35m[Appium]e[39m Appium REST http interface listener started on 0.0.0.0:54807

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[90m67 ms - 67e[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[90m80 ms - 67e[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\\cinesoft\\Desktop\\anand_media_testV2.3.apk”,“autoGrantPermissions”:true,“automationName”:“uiautomator2”,“deviceName”:“OnePlus A0001 (Android 8.1.0)”,“fullReset”:false,“newCommandTimeout”:1800,“noReset”:true,“platform”:“ANDROID”,“platformName”:“Android”,“udid”:“d95b2fd3”},“capabilities”:{“desiredCapabilities”:{“app”:“C:\\Users\\cinesoft\\Desktop\\anand_media_testV2.3.apk”,“autoGrantPermissions”:true,“automationName”:“uiautomator2”,“deviceName”:“OnePlus A0001 (Android 8.1.0)”,“fullReset”:false,“newCommandTimeout”:1800,“noReset”:true,“platform”:“ANDROID”,“platformName”:“Android”,“udid”:“d95b2fd3”},“firstMatch”:[{“platformName”:“android”}]}}e[39m

e[35m[Appium]e[39m Could not parse W3C capabilities: ‘deviceName’ can’t be blank

e[35m[Appium]e[39m Trying to fix W3C capabilities by merging them with JSONWP caps

e[35m[BaseDriver]e[39m The capabilities [“app”,“autoGrantPermissions”,“automationName”,“deviceName”,“fullReset”,“newCommandTimeout”,“noReset”,“platform”,“udid”] are not standard capabilities and should have an extension prefix

e[35m[Appium]e[39m Creating new AndroidUiautomator2Driver (v1.16.0) session

e[35m[Appium]e[39m Capabilities:

e[35m[Appium]e[39m app: C:\Users\cinesoft\Desktop\anand_media_testV2.3.apk

e[35m[Appium]e[39m autoGrantPermissions: true

e[35m[Appium]e[39m automationName: uiautomator2

e[35m[Appium]e[39m deviceName: OnePlus A0001 (Android 8.1.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 udid: d95b2fd3

e[35m[Appium]e[39m platformName: android

e[35m[BaseDriver]e[39m The following capabilities were provided, but are not recognized by appium: platform.

e[35m[BaseDriver]e[39m Session created with session id: 13b110e9-f3f6-442f-92ee-d59fdabca3da

e[35m[BaseDriver]e[39m Using local app 'C:\Users\cinesoft\Desktop\anand_media_testV2.3.apk’

e[35m[AndroidDriver]e[39m Java version is: 1.8.0_102

e[35m[ADB]e[39m Checking whether adb is present

e[35m[ADB]e[39m Found 1 ‘build-tools’ folders under ‘C:\Users\cinesoft\.katalon\tools\android_sdk’ (newest first):

e[35m[ADB]e[39m C:/Users/cinesoft/.katalon/tools/android_sdk/build-tools/28.0.2

e[35m[ADB]e[39m Using adb.exe from C:\Users\cinesoft\.katalon\tools\android_sdk\platform-tools\adb.exe

e[35m[AndroidDriver]e[39m Retrieving device list

e[35m[AndroidDriver]e[39m Using device: d95b2fd3

e[35m[ADB]e[39m Using the alternative activity name detection method because of: Could not find apkanalyzer.bat in C:\Users\cinesoft\.katalon\tools\android_sdk\platform-tools\apkanalyzer.bat,C:\Users\cinesoft\.katalon\tools\android_sdk\emulator\apkanalyzer.bat,C:\Users\cinesoft\.katalon\tools\android_sdk\tools\apkanalyzer.bat,C:\Users\cinesoft\.katalon\tools\android_sdk\tools\bin\apkanalyzer.bat,C:\Users\cinesoft\.katalon\tools\android_sdk\build-tools\28.0.2\apkanalyzer.bat. Do you have the Android SDK installed at ‘C:\Users\cinesoft\.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\cinesoft\.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.cinesoft.anandmedia.mobile’

e[35m[ADB]e[39m Main activity name: 'com.mobile.root.anandmediamobile.view.activity.SplashActivity’

e[35m[ADB]e[39m Getting device platform version

e[35m[ADB]e[39m Using apksigner.bat from C:\Users\cinesoft\.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\cinesoft\.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 123 strings from ‘C:\Users\cinesoft\Desktop\anand_media_testV2.3.apk’ resources for ‘(default)’ configuration

e[35m[UiAutomator2]e[39m Starting uiautomator2 server 1.15.1

e[35m[UiAutomator2]e[39m Using UIAutomator2 server from ‘C:\Users\cinesoft\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v1.15.1.apk’ and test from 'C:\Users\cinesoft\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 d95b2fd3 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[Appium]e[39m Welcome to Appium v1.9.0

e[35m[Appium]e[39m Non-default server args:

e[35m[Appium]e[39m port: 55495

e[35m[Appium]e[39m loglevel: info

e[35m[Appium]e[39m chromeDriverPort: 55496

e[35m[Appium]e[39m tmpDir: C:\Users\cinesoft\AppData\Local\Temp\\Katalon\Appium\Temp1536558028422

e[35m[Appium]e[39m Appium REST http interface listener started on 0.0.0.0:55495

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[90m99 ms - 67e[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[90m59 ms - 67e[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\\cinesoft\\Desktop\\anand_media_testV2.3.apk”,“autoGrantPermissions”:true,“automationName”:“uiautomator2”,“deviceName”:“OnePlus A0001 (Android 8.1.0)”,“fullReset”:false,“newCommandTimeout”:1800,“noReset”:true,“platform”:“ANDROID”,“platformName”:“Android”,“udid”:“d95b2fd3”},“capabilities”:{“desiredCapabilities”:{“app”:“C:\\Users\\cinesoft\\Desktop\\anand_media_testV2.3.apk”,“autoGrantPermissions”:true,“automationName”:“uiautomator2”,“deviceName”:“OnePlus A0001 (Android 8.1.0)”,“fullReset”:false,“newCommandTimeout”:1800,“noReset”:true,“platform”:“ANDROID”,“platformName”:“Android”,“udid”:“d95b2fd3”},“firstMatch”:[{“platformName”:“android”}]}}e[39m

e[35m[Appium]e[39m Could not parse W3C capabilities: ‘deviceName’ can’t be blank

e[35m[Appium]e[39m Trying to fix W3C capabilities by merging them with JSONWP caps

e[35m[BaseDriver]e[39m The capabilities [“app”,“autoGrantPermissions”,“automationName”,“deviceName”,“fullReset”,“newCommandTimeout”,“noReset”,“platform”,“udid”] are not standard capabilities and should have an extension prefix

e[35m[Appium]e[39m Creating new AndroidUiautomator2Driver (v1.16.0) session

e[35m[Appium]e[39m Capabilities:

e[35m[Appium]e[39m app: C:\Users\cinesoft\Desktop\anand_media_testV2.3.apk

e[35m[Appium]e[39m autoGrantPermissions: true

e[35m[Appium]e[39m automationName: uiautomator2

e[35m[Appium]e[39m deviceName: OnePlus A0001 (Android 8.1.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 udid: d95b2fd3

e[35m[Appium]e[39m platformName: android

e[35m[BaseDriver]e[39m The following capabilities were provided, but are not recognized by appium: platform.

e[35m[BaseDriver]e[39m Session created with session id: d4b96fb3-070c-44f1-9afe-aa607d92e4d1

e[35m[BaseDriver]e[39m Using local app ‘C:\Users\cinesoft\Desktop\anand_media_testV2.3.apk’

e[35m[AndroidDriver]e[39m Java version is: 1.8.0_102

e[35m[ADB]e[39m Checking whether adb is present

e[35m[ADB]e[39m Found 1 ‘build-tools’ folders under ‘C:\Users\cinesoft\.katalon\tools\android_sdk’ (newest first):

e[35m[ADB]e[39m C:/Users/cinesoft/.katalon/tools/android_sdk/build-tools/28.0.2

e[35m[ADB]e[39m Using adb.exe from C:\Users\cinesoft\.katalon\tools\android_sdk\platform-tools\adb.exe

e[35m[AndroidDriver]e[39m Retrieving device list

e[35m[AndroidDriver]e[39m Using device: d95b2fd3

e[35m[ADB]e[39m Using the alternative activity name detection method because of: Could not find apkanalyzer.bat in C:\Users\cinesoft\.katalon\tools\android_sdk\platform-tools\apkanalyzer.bat,C:\Users\cinesoft\.katalon\tools\android_sdk\emulator\apkanalyzer.bat,C:\Users\cinesoft\.katalon\tools\android_sdk\tools\apkanalyzer.bat,C:\Users\cinesoft\.katalon\tools\android_sdk\tools\bin\apkanalyzer.bat,C:\Users\cinesoft\.katalon\tools\android_sdk\build-tools\28.0.2\apkanalyzer.bat. Do you have the Android SDK installed at ‘C:\Users\cinesoft\.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\cinesoft\.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.cinesoft.anandmedia.mobile’

e[35m[ADB]e[39m Main activity name: ‘com.mobile.root.anandmediamobile.view.activity.SplashActivity’

e[35m[ADB]e[39m Getting device platform version

e[35m[ADB]e[39m Using apksigner.bat from C:\Users\cinesoft\.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\cinesoft\.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 123 strings from ‘C:\Users\cinesoft\Desktop\anand_media_testV2.3.apk’ resources for ‘(default)’ configuration

e[35m[UiAutomator2]e[39m Starting uiautomator2 server 1.15.1

e[35m[UiAutomator2]e[39m Using UIAutomator2 server from ‘C:\Users\cinesoft\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v1.15.1.apk’ and test from ‘C:\Users\cinesoft\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 d95b2fd3 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.cinesoft.anandmedia.mobile/com.mobile.root.anandmediamobile.view.activity.SplashActivity’. Starting it ourselves