Getting the error "The requested version 1.7.16 by your slf4j binding is not compatible with [1.6]"

Please help me with this…

SLF4J: The requested version 1.7.16 by your slf4j binding is not compatible with [1.6]
SLF4J: See SLF4J Error Codes for further details.

Is this issue affecting your testing ? if not you can ignore it
See this reply by a katalon developer

if your tests are not running it’s probably somethig else

I am also getting “Failed to start Appium server in 30 sec”… what should I do?? @yoyox98

paste the full log please so i can have a look

This is what I have got @yoyox98

SLF4J: The requested version 1.7.16 by your slf4j binding is not compatible with [1.6]
SLF4J: See http://www.slf4j.org/codes.html#version_mismatch for further details.
2019-07-10 21:55:25.386 INFO c.k.katalon.core.main.TestSuiteExecutor - START Test Suites/Regression Tests
2019-07-10 21:55:25.538 INFO c.k.katalon.core.main.TestSuiteExecutor - hostName = Admin - DESKTOP-CG4UR49
2019-07-10 21:55:25.540 INFO c.k.katalon.core.main.TestSuiteExecutor - os = Windows 10 64bit
2019-07-10 21:55:25.541 INFO c.k.katalon.core.main.TestSuiteExecutor - hostAddress = 192.168.225.223
2019-07-10 21:55:25.544 INFO c.k.katalon.core.main.TestSuiteExecutor - katalonVersion = 6.2.1.2
2019-07-10 21:55:26.473 INFO c.k.katalon.core.main.TestCaseExecutor - --------------------
2019-07-10 21:55:26.474 INFO c.k.katalon.core.main.TestCaseExecutor - START Test Cases/Verify Correct Alarm Message
2019-07-10 21:55:27.201 DEBUG testcase.Verify Correct Alarm Message - 1: comment(“Story: Verify correct alarm message”)
2019-07-10 21:55:27.429 INFO c.k.k.c.keyword.builtin.CommentKeyword - Story: Verify correct alarm message
2019-07-10 21:55:27.432 DEBUG testcase.Verify Correct Alarm Message - 2: comment(“Given that user has started an application”)
2019-07-10 21:55:27.449 INFO c.k.k.c.keyword.builtin.CommentKeyword - Given that user has started an application
2019-07-10 21:55:27.467 DEBUG testcase.Verify Correct Alarm Message - 3: appPath = relativeToAbsolutePath(G_AndroidApp, getProjectDir())
2019-07-10 21:55:27.858 DEBUG testcase.Verify Correct Alarm Message - 4: startApplication(appPath, false)
e[35m[Appium]e[39m Welcome to Appium v1.14.0
e[35m[Appium]e[39m Non-default server args:
e[35m[Appium]e[39m port: 62628
e[35m[Appium]e[39m loglevel: info
e[35m[Appium]e[39m chromeDriverPort: 62629
e[35m[Appium]e[39m tmpDir: C:\Users\Admin\AppData\Local\Temp\Katalon\Appium\Temp1562775928301
e[35m[Appium]e[39m Appium REST http interface listener started on 0.0.0.0:62628
2019-07-10 21:55:54.268 INFO c.k.k.c.a.driver.AppiumDriverManager - Appium server started on port 62,628
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 - 68e[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\Admin\Katalon Studio\mobile.prj\androidapp\APIDemos.apk”,“noReset”:true,“newCommandTimeout”:1800,“platformVersion”:“9”,“automationName”:“uiautomator2”,“autoGrantPermissions”:true,“platformName”:“Android”,“udid”:“5200a0aafa5b745f”,“deviceName”:“samsung SM-J701F (Android 9)”,“fullReset”:false,“platform”:“ANDROID”},“capabilities”:{“firstMatch”:[{“appium:app”:“C:\Users\Admin\Katalon Studio\mobile.prj\androidapp\APIDemos.apk”,“appium:autoGrantPermissions”:true,“appium:automationName”:“uiautomator2”,“appium:deviceName”:“samsung SM-J701F (Android 9)”,“appium:fullReset”:false,“appium:newCommandTimeout”:1800,“appium:noReset”:true,“platform”:“ANDROID”,“platformName”:“android”,“appium:platformVersion”:“9”,“appium:udid”:“5200a0aafa5b745f”}]}}e[39m
e[35m[BaseDriver]e[39m The capabilities [“platform”] are not standard capabilities and should have an extension prefix
e[35m[Appium]e[39m Appium v1.14.0 creating new AndroidUiautomator2Driver (v1.33.1) session
e[35m[Appium]e[39m Capabilities:
e[35m[Appium]e[39m platform: ANDROID
e[35m[Appium]e[39m platformName: android
e[35m[Appium]e[39m app: C:\Users\Admin\Katalon Studio\mobile.prj\androidapp\APIDemos.apk
e[35m[Appium]e[39m autoGrantPermissions: true
e[35m[Appium]e[39m automationName: uiautomator2
e[35m[Appium]e[39m deviceName: samsung SM-J701F (Android 9)
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 platformVersion: 9
e[35m[Appium]e[39m udid: 5200a0aafa5b745f
e[35m[BaseDriver]e[39m The following capabilities were provided, but are not recognized by Appium:
e[35m[BaseDriver]e[39m platform
e[35m[BaseDriver]e[39m Session created with session id: 3ba7c9b6-cf08-4ee5-bfef-725f59bfd2d4
e[35m[BaseDriver]e[39m Using local app ‘C:\Users\Admin\Katalon Studio\mobile.prj\androidapp\APIDemos.apk’
e[35m[ADB]e[39m Found 1 ‘build-tools’ folders under ‘C:\Users\Admin.katalon\tools\android_sdk’ (newest first):
e[35m[ADB]e[39m C:/Users/Admin/.katalon/tools/android_sdk/build-tools/29.0.0
e[35m[ADB]e[39m Using ‘adb.exe’ from ‘C:\Users\Admin.katalon\tools\android_sdk\platform-tools\adb.exe’
e[35m[AndroidDriver]e[39m Retrieving device list
e[35m[AndroidDriver]e[39m Using device: 5200a0aafa5b745f
e[35m[ADB]e[39m Using ‘adb.exe’ from ‘C:\Users\Admin.katalon\tools\android_sdk\platform-tools\adb.exe’
e[35m[UiAutomator2]e[39m Relaxing hidden api policy
e[35m[ADB]e[39m Using the alternative activity name detection method because of: Could not find ‘apkanalyzer.bat’ in [“C:\Users\Admin\.katalon\tools\android_sdk\platform-tools\apkanalyzer.bat”,“C:\Users\Admin\.katalon\tools\android_sdk\emulator\apkanalyzer.bat”,“C:\Users\Admin\.katalon\tools\android_sdk\tools\apkanalyzer.bat”,“C:\Users\Admin\.katalon\tools\android_sdk\tools\bin\apkanalyzer.bat”,“C:\Users\Admin\.katalon\tools\android_sdk\build-tools\29.0.0\apkanalyzer.bat”]. Do you have Android Build Tools installed at ‘C:\Users\Admin.katalon\tools\android_sdk’?
e[35m[ADB]e[39m Using ‘aapt.exe’ from ‘C:\Users\Admin.katalon\tools\android_sdk\build-tools\29.0.0\aapt.exe’
e[35m[ADB]e[39m Extracting package and launch activity from manifest
e[35m[ADB]e[39m Package name: ‘com.hmh.api’
e[35m[ADB]e[39m Main activity name: ‘com.hmh.api.ApiDemos’
e[35m[ADB]e[39m Using ‘apksigner.bat’ from ‘C:\Users\Admin.katalon\tools\android_sdk\build-tools\29.0.0\apksigner.bat’
e[35m[ADB]e[39m Using ‘zipalign.exe’ from ‘C:\Users\Admin.katalon\tools\android_sdk\build-tools\29.0.0\zipalign.exe’
e[35m[UiAutomator2]e[39m Server packages are going to be (re)installed
e[35m[UiAutomator2]e[39m Full packages reinstall is going to be performed
e[35m[ADB]e[39m io.appium.uiautomator2.server was successfully uninstalled
e[35m[ADB]e[39m The application at ‘C:\Users\Admin\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-server\apks\appium-uiautomator2-server-v3.7.0.apk’ is already cached to ‘/data/local/tmp/appium_cache/fe3aa6662b6c999cf661d7626a50da395fd786f4.apk’
e[35m[UiAutomator2]e[39m Did not get confirmation UiAutomator2 deleteSession worked; Error was: UnknownError: An unknown server-side error occurred while processing the command. Original error: Trying to proxy a session command without session id
e[35m[UiAutomator2]e[39m Unable to remove port forward ‘Error executing adbExec. Original error: ‘Command ‘C:\Users\Admin\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 5200a0aafa5b745f forward --remove tcp:8200’ exited with code 1’; Stderr: ‘adb.exe: error: listener ‘tcp:8200’ not found’; Code: ‘1’’
e[35m[UiAutomator2]e[39m Restoring hidden api policy to the device default configuration
2019-07-10 21:56:33.570 INFO c.k.k.c.a.driver.AppiumDriverManager - deviceId = 5200a0aafa5b745f
2019-07-10 21:56:33.574 INFO c.k.k.c.a.driver.AppiumDriverManager - deviceName = samsung SM-J701F (Android 9)
2019-07-10 21:56:33.576 INFO c.k.k.c.a.driver.AppiumDriverManager - deviceModel = SM-J701F
2019-07-10 21:56:33.576 INFO c.k.k.c.a.driver.AppiumDriverManager - deviceManufacturer = samsung
2019-07-10 21:56:33.597 INFO c.k.k.c.a.driver.AppiumDriverManager - deviceOS = Android
2019-07-10 21:56:33.597 INFO c.k.k.c.a.driver.AppiumDriverManager - deviceOSVersion = 9
2019-07-10 21:56:33.667 ERROR c.k.k.core.keyword.internal.KeywordMain - :x: Unable to start app at: ‘C:\Users\Admin\Katalon Studio\mobile.prj\androidapp\APIDemos.apk’ (Root cause: org.openqa.selenium.SessionNotCreatedException: Unable to create a new remote session. Please check the server log for more details. Original error: An unknown server-side error occurred while processing the command. Original error: Error executing adbExec. Original error: ‘Command ‘C:\Users\Admin\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 5200a0aafa5b745f shell pm install /data/local/tmp/appium_cache/fe3aa6662b6c999cf661d7626a50da395fd786f4.apk’ timed out after 20000ms’. Try to increase the 20000ms adb execution timeout represented by ‘uiautomator2ServerInstallTimeout’ capability
Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:25:53’
System info: host: ‘DESKTOP-CG4UR49’, ip: ‘192.168.225.223’, os.name: ‘Windows 10’, os.arch: ‘amd64’, os.version: ‘10.0’, java.version: ‘1.8.0_181’
Driver info: driver.version: SwipeableAndroidDriver
remote stacktrace: UnknownError: An unknown server-side error occurred while processing the command. Original error: Error executing adbExec. Original error: ‘Command ‘C:\Users\Admin\.katalon\tools\android_sdk\platform-tools\adb.exe -P 5037 -s 5200a0aafa5b745f shell pm install /data/local/tmp/appium_cache/fe3aa6662b6c999cf661d7626a50da395fd786f4.apk’ timed out after 20000ms’. Try to increase the 20000ms adb execution timeout represented by ‘uiautomator2ServerInstallTimeout’ capability
at getResponseForW3CError (C:\Users\Admin\AppData\Roaming\npm\node_modules\appium\node_modules\appium-base-driver\lib\protocol\errors.js:826:9)
at asyncHandler (C:\Users\Admin\AppData\Roaming\npm\node_modules\appium\node_modules\appium-base-driver\lib\protocol\protocol.js:447:37)
Build info: version: ‘3.141.59’, revision: ‘e82be7d358’, time: ‘2018-11-14T08:25:53’