how to navigation mobile splash screen to home screen?

Product Forums Katalon Studio
1

how to navigation mobile splash screen to home screen in katalon studio??

2

Hi pranesh,

It seems that your issue is in a specific ca)se. So could you please send us a support ticket with your application for further investigation (via https://support.katalon.com/hc/en-us/requests/new).

Thanks.

3

Hi,

Mobile Tap keyword is not working in katalon i also tried for so many application facing this same issue.Still now i am not succussfully completed one single project in this tool.

4

Could you share your code by modifying sensitive information in it. What happens when you TAP on the splash screen?

5

Hi,

The time span of my splash screen 5000ms.

It shows splash page correctly the only problem is it just stopped in splash screen not move to home screen,it just stay stopped.

Note:The splash page doesn’t contain any link to click to navigate home screen,it just display and load navigate.

6

May I know the time span of your splash screen (in seconds).
I’ve an app which has splash screen, I don’t have anything to do with it. Only scenario is to check whether splash screen has expected logo. So after launch, Katalon has checked for that mobile element successfully.

May I know your scenario?

7

Hi,

I need to know whether katalon studio is capable to navigate splash page?

8

Hi,

I have mentioned appWaitActivity in project settings.
I have refreshed my project.
I have Plug out and restarted my device
I have Uninstalled my application and reinstalled it.
I have closed all adb.exe and node.exe process.

but im still facing the same issue.

Find my appium log file below,

[Appium] Welcome to Appium v1.6.4
[Appium] Non-default server args:
[Appium] port: 53783
[Appium] chromeDriverPort: 53960
[Appium] tmpDir: C:\Users\PRANES~1.AUG\AppData\Local\Temp\\Katalon\Appium\Temp1495005125282
[Appium] Appium REST http interface listener started on 0.0.0.0:53783
[HTTP] –> GET /wd/hub/status {}
[debug] [MJSONWP] Calling AppiumDriver.getStatus() with args: []
[debug] [MJSONWP] Responding to client with driver.getStatus() result: {“build”:{“version”:"1.6.4″,“revision”:null}}
[HTTP] <– GET /wd/hub/status 200 49 ms – 83
[HTTP] –> GET /wd/hub/status {}
[debug] [MJSONWP] Calling AppiumDriver.getStatus() with args: []
[debug] [MJSONWP] Responding to client with driver.getStatus() result: {“build”:{“version”:“1.6.4″,“revision”:null}}
[HTTP] <– GET /wd/hub/status 200 51 ms – 83
[HTTP] –> POST /wd/hub/session {“desiredCapabilities”:{“app”:“C:\\Users\\pranesh.AUGUSTAHITECH\\Downloads\\RippleJump_Dev_v37_4.1.apk”,“noReset”:true,“newCommandTimeout”:1800,“udid”:“6464f034″,“platformName”:“Android”,“deviceName”:“adb server is out of date. killing… “,“fullReset”:false,“platform”:“ANDROID”}}
[debug] [MJSONWP] Calling AppiumDriver.createSession() with args: [{“app”:“C:\\Users\\pranesh.AUGUSTAHITECH\\Downloads\\RippleJump_Dev_v37_4.1.apk”,“noReset”:true,“newCommandTimeout”:1800,“udid”:“6464f034″,“platformName”:“Android”,“deviceName”:“adb server is out of date. killing… “,“fullReset”:false,“platform”:“ANDROID”},null,null,null,null]
[debug] [BaseDriver] Event ‘newSessionRequested’ logged at 1495005214919 (12:43:34 GMT+0530 (India Standard Time))
[Appium] Creating new AndroidDriver (v1.17.1) session
[Appium] Capabilities:
[Appium] app: ‘C:\\Users\\pranesh.AUGUSTAHITECH\\Downloads\\RippleJump_Dev_v37_4.1.apk’
[Appium] noReset: true
[Appium] newCommandTimeout: 1800
[Appium] udid: ‘6464f034’
[Appium] platformName: ‘Android’
[Appium] deviceName: 'adb server is out of date. killing… ’
[Appium] fullReset: false
[Appium] platform: ‘ANDROID’
[debug] [AndroidDriver] AndroidDriver version: 1.17.1
[BaseDriver] The following capabilities were provided, but are not recognized by appium: platform.
[BaseDriver] Session created with session id: 8d7c358d-73f0-45a2-9a29-e7c950f1803c
[debug] [AndroidDriver] Getting Java version
[AndroidDriver] Java version is: 1.8.0_102
[ADB] Checking whether adb is present
[ADB] Using adb.exe from D:\katalon\configuration\resources\tools\android_sdk\platform-tools\adb.exe
[AndroidDriver] Retrieving device list
[debug] [ADB] Trying to find a connected android device
[debug] [ADB] Getting connected devices…
[debug] [ADB] Could not find devices, restarting adb server…
[debug] [ADB] Restarting adb
[debug] [ADB] Getting connected devices…
[debug] [ADB] 1 device(s) connected
[AndroidDriver] Using device: 6464f034
[ADB] Checking whether adb is present
[ADB] Using adb.exe from D:\katalon\configuration\resources\tools\android_sdk\platform-tools\adb.exe
[debug] [ADB] Setting device id to 6464f034
[BaseDriver] Using local app ‘C:\Users\pranesh.AUGUSTAHITECH\Downloads\RippleJump_Dev_v37_4.1.apk’
[debug] [AndroidDriver] Checking whether app is actually present
[AndroidDriver] Starting Android session
[debug] [ADB] Running ‘D:\katalon\configuration\resources\tools\android_sdk\platform-tools\adb.exe’ with args: [”-P”,5037,”-s”,“6464f034″,“wait-for-device”]
[debug] [ADB] Getting connected devices…
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running ‘D:\katalon\configuration\resources\tools\android_sdk\platform-tools\adb.exe’ with args: [”-P”,5037,”-s”,"6464f034″,“shell”,“echo”,“ping”]
[debug] [ADB] Restarting adb
[debug] [ADB] Getting connected devices…
[debug] [ADB] 1 device(s) connected

9

Hi pranesh,

As can be seen in the log, the desired capability appWaitActivity is not set. Please make sure you set it in Project Settings. In case you already did it, please try to refresh your environment:

Plug out and restart your device
Uninstall your application under test
On your computer, open Task Manager and close process “adb.exe” and “node.exe”
Plug in your device and try again

Please contact us again if you still meet this issue. Thanks.

10

Hi,

Find my appium log file below,

[Appium] Welcome to Appium v1.6.4
[Appium] Non-default server args:
[Appium] port: 53783
[Appium] chromeDriverPort: 53960
[Appium] tmpDir: C:\Users\PRANES~1.AUG\AppData\Local\Temp\\Katalon\Appium\Temp1495005125282
[Appium] Appium REST http interface listener started on 0.0.0.0:53783
[HTTP] --> GET /wd/hub/status {}
[debug] [MJSONWP] Calling AppiumDriver.getStatus() with args: []
[debug] [MJSONWP] Responding to client with driver.getStatus() result: {“build”:{“version”:“1.6.4”,“revision”:null}}
[HTTP] <-- GET /wd/hub/status 200 49 ms - 83
[HTTP] --> GET /wd/hub/status {}
[debug] [MJSONWP] Calling AppiumDriver.getStatus() with args: []
[debug] [MJSONWP] Responding to client with driver.getStatus() result: {“build”:{“version”:“1.6.4”,“revision”:null}}
[HTTP] <-- GET /wd/hub/status 200 51 ms - 83
[HTTP] --> POST /wd/hub/session {“desiredCapabilities”:{“app”:“C:\\Users\\pranesh.AUGUSTAHITECH\\Downloads\\RippleJump_Dev_v37_4.1.apk”,“noReset”:true,“newCommandTimeout”:1800,“udid”:“6464f034”,“platformName”:“Android”,“deviceName”:“adb server is out of date. killing… “,“fullReset”:false,“platform”:“ANDROID”}}
[debug] [MJSONWP] Calling AppiumDriver.createSession() with args: [{“app”:“C:\\Users\\pranesh.AUGUSTAHITECH\\Downloads\\RippleJump_Dev_v37_4.1.apk”,“noReset”:true,“newCommandTimeout”:1800,“udid”:“6464f034”,“platformName”:“Android”,“deviceName”:“adb server is out of date. killing… “,“fullReset”:false,“platform”:“ANDROID”},null,null,null,null]
[debug] [BaseDriver] Event ‘newSessionRequested’ logged at 1495005214919 (12:43:34 GMT+0530 (India Standard Time))
[Appium] Creating new AndroidDriver (v1.17.1) session
[Appium] Capabilities:
[Appium] app: ‘C:\\Users\\pranesh.AUGUSTAHITECH\\Downloads\\RippleJump_Dev_v37_4.1.apk’
[Appium] noReset: true
[Appium] newCommandTimeout: 1800
[Appium] udid: ‘6464f034’
[Appium] platformName: ‘Android’
[Appium] deviceName: 'adb server is out of date. killing… ’
[Appium] fullReset: false
[Appium] platform: ‘ANDROID’
[debug] [AndroidDriver] AndroidDriver version: 1.17.1
[BaseDriver] The following capabilities were provided, but are not recognized by appium: platform.
[BaseDriver] Session created with session id: 8d7c358d-73f0-45a2-9a29-e7c950f1803c
[debug] [AndroidDriver] Getting Java version
[AndroidDriver] Java version is: 1.8.0_102
[ADB] Checking whether adb is present
[ADB] Using adb.exe from D:\katalon\configuration\resources\tools\android_sdk\platform-tools\adb.exe
[AndroidDriver] Retrieving device list
[debug] [ADB] Trying to find a connected android device
[debug] [ADB] Getting connected devices…
[debug] [ADB] Could not find devices, restarting adb server…
[debug] [ADB] Restarting adb
[debug] [ADB] Getting connected devices…
[debug] [ADB] 1 device(s) connected
[AndroidDriver] Using device: 6464f034
[ADB] Checking whether adb is present
[ADB] Using adb.exe from D:\katalon\configuration\resources\tools\android_sdk\platform-tools\adb.exe
[debug] [ADB] Setting device id to 6464f034
[BaseDriver] Using local app ‘C:\Users\pranesh.AUGUSTAHITECH\Downloads\RippleJump_Dev_v37_4.1.apk’
[debug] [AndroidDriver] Checking whether app is actually present
[AndroidDriver] Starting Android session
[debug] [ADB] Running ‘D:\katalon\configuration\resources\tools\android_sdk\platform-tools\adb.exe’ with args: [”-P”,5037,”-s”,“6464f034”,“wait-for-device”]
[debug] [ADB] Getting connected devices…
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running ‘D:\katalon\configuration\resources\tools\android_sdk\platform-tools\adb.exe’ with args: ["-P",5037,"-s",“6464f034”,“shell”,“echo”,“ping”]
[debug] [ADB] Restarting adb
[debug] [ADB] Getting connected devices…
[debug] [ADB] 1 device(s) connected

11

Hi pranesh,

We need the appium.log file while execution for further investigation. Could you please add your test case to a test suite, then execute this suite. You can find appium.log file inside the report folder of your execution.

Thanks.

12

Hi,

I am using updated tool only,same issue is facing still

Splash page is not navigating to home screen.

find my console out

05-17-2017 11:13:19 AM - [START] - Start Test Case : Test Cases/New Test Case
05-17-2017 11:13:19 AM - [INFO] - Evaluating variables for test case
05-17-2017 11:13:19 AM - [START] - Start action : startApplication
05-17-2017 11:13:19 AM - [INFO] - Starting app at: ‘C:\Users\pranesh.AUGUSTAHITECH\Downloads\RippleJump_Dev_v37_4.1.apk’
05-17-2017 11:13:19 AM - [INFO] - User set preference: [‘appWaitActivity’, ‘com.ripplejump.activities.RippleBaseActivity’]
05-17-2017 11:13:19 AM - [INFO] - User set preference: [‘deviceId’, ‘6464f034’]
05-17-2017 11:13:23 AM - [INFO] - Appium server started on port 63,767

after this keep on loading

13

Hi there,

Could you please download Katalon Studio and try again since we updated a hotfix in April and we have no idea whether you’re using that build? As can be seen in the log you’ve sent, the appWaitActivity capability is not set.

Thanks.

14

Hi,

I have mentioned my home screen name http://prntscr.com/f6vy6w,but still the application is not navigating to home screen its keep on loading an hour.

15

Hi there,

Please try to add a desired capability as below to see if it works.

Go to Project Settings: Project > Settings > Execution > Default > Mobile > Android
Add a key: name = appWaitActivity, value = the full name of your home screen activity (for example: com.ripplejump.activities.HomeScreenActivity)

If it does not work either, please contact me again.

Thanks.

16

Hi there,

Thanks for that information, we will try to take a look at it soon.

Regards

17

Hi pranesh,

Unfortunately, this is not the log we need to investigate your case.

Please keep the Debug level log, then open Mobile Object Spy and start your application (you may be stuck at the splash screen). After that, send me the appium.log file located in your project directory (https://i.imgur.com/WbvCVWe.png).

Thanks.

18

Hi,

I also changed Appium log level.

http://prntscr.com/f6h2oz

19

Hi

Please find my log file below,

05-11-2017 10:57:11 AM - [START] - Start Test Case : Test Cases/Ripple_Jump
05-11-2017 10:57:11 AM - [INFO] - Evaluating variables for test case
05-11-2017 10:57:11 AM - [START] - Start action : startApplication
05-11-2017 10:57:11 AM - [INFO] - Starting app at: ‘C:\Users\pranesh.AUGUSTAHITECH\Downloads\RippleJump_Dev_v37_4.1.apk’
05-11-2017 10:57:11 AM - [INFO] - User set preference: [‘property’, ‘true’]
05-11-2017 10:57:11 AM - [INFO] - User set preference: [‘deviceId’, ‘6464f034’]
05-11-2017 10:57:15 AM - [INFO] - Appium server started on port 50,644
05-11-2017 10:57:26 AM - [RUN_DATA] - Logging run data ‘appiumVersion’ with value '1.6.4’
05-11-2017 10:57:26 AM - [PASSED] - Started app at: ‘C:\Users\pranesh.AUGUSTAHITECH\Downloads\RippleJump_Dev_v37_4.1.apk’
05-11-2017 10:57:26 AM - [END] - End action : startApplication
05-11-2017 10:57:26 AM - [START] - Start action : pressHome
05-11-2017 10:57:27 AM - [FAILED] - Cannot press Home button (Root cause: org.openqa.selenium.WebDriverException: An unknown server-side error occurred while processing the command. (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 51 milliseconds
Build info: version: ‘2.53.0’, revision: ‘35ae25b’, time: '2016-03-15 17:00:58’
System info: host: ‘Pranesh-PC’, ip: ‘169.254.147.85’, os.name: ‘Windows 7’, os.arch: ‘amd64’, os.version: ‘6.1’, java.version: '1.8.0_102’
Driver info: com.kms.katalon.core.appium.driver.SwipeableAndroidDriver
Capabilities [{appPackage=com.ripplejump, noReset=true, deviceId=6464f034, deviceName=6464f034, fullReset=false, platform=ANDROID, deviceUDID=6464f034, desired={app=C:\Users\pranesh.AUGUSTAHITECH\Downloads\RippleJump_Dev_v37_4.1.apk, noReset=true, newCommandTimeout=1800, property=true, udid=6464f034, platformName=Android, deviceId=6464f034, deviceName=Xiaomi Redmi Note 3 6.0.1, fullReset=false, platform=ANDROID}, newCommandTimeout=1800, platformVersion=6.0.1, webStorageEnabled=false, property=true, takesScreenshot=true, javascriptEnabled=true, udid=6464f034, platformName=Android, deviceManufacturer=Xiaomi, app=C:\Users\pranesh.AUGUSTAHITECH\Downloads\RippleJump_Dev_v37_4.1.apk, deviceScreenSize=1080x1920, networkConnectionEnabled=true, warnings={}, appWaitPackage=com.ripplejump, appWaitActivity=com.ripplejump.activities.SplashScreenActivity, databaseEnabled=false, appActivity=com.ripplejump.activities.SplashScreenActivity, locationContextEnabled=false, deviceModel=Redmi Note 3}]
Session ID: 7415cb2e-1251-43f7-aede-14bdc5c50b85)
05-11-2017 10:57:27 AM - [END] - End action : pressHome
05-11-2017 10:57:27 AM - [FAILED] - Test Cases/Ripple_Jump FAILED because (of) Cannot press Home button (Root cause: org.openqa.selenium.WebDriverException: An unknown server-side error occurred while processing the command. (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 51 milliseconds
Build info: version: ‘2.53.0’, revision: ‘35ae25b’, time: '2016-03-15 17:00:58’
System info: host: ‘Pranesh-PC’, ip: ‘169.254.147.85’, os.name: ‘Windows 7’, os.arch: ‘amd64’, os.version: ‘6.1’, java.version: '1.8.0_102’
Driver info: com.kms.katalon.core.appium.driver.SwipeableAndroidDriver
Capabilities [{appPackage=com.ripplejump, noReset=true, deviceId=6464f034, deviceName=6464f034, fullReset=false, platform=ANDROID, deviceUDID=6464f034, desired={app=C:\Users\pranesh.AUGUSTAHITECH\Downloads\RippleJump_Dev_v37_4.1.apk, noReset=true, newCommandTimeout=1800, property=true, udid=6464f034, platformName=Android, deviceId=6464f034, deviceName=Xiaomi Redmi Note 3 6.0.1, fullReset=false, platform=ANDROID}, newCommandTimeout=1800, platformVersion=6.0.1, webStorageEnabled=false, property=true, takesScreenshot=true, javascriptEnabled=true, udid=6464f034, platformName=Android, deviceManufacturer=Xiaomi, app=C:\Users\pranesh.AUGUSTAHITECH\Downloads\RippleJump_Dev_v37_4.1.apk, deviceScreenSize=1080x1920, networkConnectionEnabled=true, warnings={}, appWaitPackage=com.ripplejump, appWaitActivity=com.ripplejump.activities.SplashScreenActivity, databaseEnabled=false, appActivity=com.ripplejump.activities.SplashScreenActivity, locationContextEnabled=false, deviceModel=Redmi Note 3}]
Session ID: 7415cb2e-1251-43f7-aede-14bdc5c50b85)
05-11-2017 10:57:27 AM - [END] - End Test Case : Test Cases/Ripple_Jump

20

Hi there,

Can you do us another favor: Please set your Appium Log Level to “Debug” (You can find this option in Windows > Katalon Studio Preferences > Katalon > Mobile), then retry with your execution and send us the appium.log file again for further investigation. You can send this file through our Zendesk support’s ticket :slight_smile:

Thanks