org.openqa.selenium.SessionNotCreatedException: A new session could not be created. Getting this error after launching the app

Launching Appium server with command: C:\Program Files (x86)\Appium\node.exe lib\server\main.js --address 127.0.0.1 --port 4723 --platform-name Android --platform-version 23 --automation-name Appium --log-no-color
info: Welcome to Appium v1.4.16 (REV ae6877eff263066b26328d457bd285c0cc62430d)
info: Appium REST http interface listener started on 127.0.0.1:4723
info: [debug] Non-default server args: {“address”:“127.0.0.1”,“logNoColors”:true,“platformName”:“Android”,“platformVersion”:“23”,“automationName”:“Appium”}
info: Console LogLevel: debug
info: → POST /wd/hub/session {“desiredCapabilities”:{“appPackage”:“com.dummyApp”,“appActivity”:“com.dummyApp.activity.SplashActivity”,“BROWSER_NAME”:“Android”,“VERSION”:“6.0”,“platformName”:“Android”,“deviceName”:“Galaxy S5”}}
info: Client User-Agent string: Apache-HttpClient/4.5.1 (Java/1.8.0_101)
info: [debug] The following desired capabilities were provided, but not recognized by appium. They will be passed on to any other services running on this server. : BROWSER_NAME, VERSION
info: [debug] Didn’t get app but did get Android package, will attempt to launch it on the device
info: [debug] Creating new appium session 75fab114-0b75-4eb3-8e38-50b5011e71f4
info: Starting android appium
info: [debug] Getting Java version
info: Java version is: 1.8.0_101
info: [debug] Checking whether adb is present
info: [debug] Using adb from D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe
warn: No app capability, can’t parse package/activity
info: [debug] Using fast reset? true
info: [debug] Preparing device for session
info: [debug] Not checking whether app is present since we are assuming it’s already on the device
info: Retrieving device
info: [debug] Trying to find a connected android device
info: [debug] Getting connected devices…
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe devices
info: [debug] 1 device(s) connected
info: Found device HT4AZJT00764
info: [debug] Setting device id to HT4AZJT00764
info: [debug] Waiting for device to be ready and to respond to shell commands (timeout = 5)
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 wait-for-device
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “echo ‘ready’”
info: [debug] Starting logcat capture
info: [debug] Getting device API level
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “getprop ro.build.version.sdk”
info: [debug] Device is at API Level 22
info: Device API level is: 22
info: [debug] Extracting strings for language: default
info: [debug] Apk doesn’t exist locally
info: [debug] Could not get strings, but it looks like we had an old strings file anyway, so ignoring
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “rm -rf /data/local/tmp/strings.json”
info: [debug] Not uninstalling app since server not started with --full-reset
info: [debug] Skipping install since we launched with a package instead of an app path
info: [debug] Forwarding system:4724 to device:4724
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 forward tcp:4724 tcp:4724
info: [debug] Pushing appium bootstrap to device…
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 push “C:\Program Files (x86)\Appium\node_modules\appium\build\android_bootstrap\AppiumBootstrap.jar” /data/local/tmp/
info: [debug] Pushing settings apk to device…
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 install “C:\Program Files (x86)\Appium\node_modules\appium\build\settings_apk\settings_apk-debug.apk”
info: [debug] Pushing unlock helper app to device…
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 install “C:\Program Files (x86)\Appium\node_modules\appium\build\unlock_apk\unlock_apk-debug.apk”
info: Starting App
info: [debug] Attempting to kill all ‘uiautomator’ processes
info: [debug] Getting all processes with ‘uiautomator’
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “ps ‘uiautomator’”
info: [debug] No matching processes found
info: [debug] Running bootstrap
info: [debug] spawning: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell uiautomator runtest AppiumBootstrap.jar -c io.appium.android.bootstrap.Bootstrap -e pkg com.dummyApp -e disableAndroidWatchers false
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
info: [debug] [UIAUTOMATOR STDOUT] io.appium.android.bootstrap.Bootstrap:
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 1
info: [debug] [BOOTSTRAP] [debug] Socket opened on port 4724
info: [debug] [BOOTSTRAP] [debug] Appium Socket Server Ready
info: [debug] [BOOTSTRAP] [debug] Loading json…
info: [debug] [BOOTSTRAP] [debug] Registered crash watchers.
info: [debug] Waking up device if it’s not alive
info: [debug] Pushing command to appium work queue: [“wake”,{}]
info: [debug] [BOOTSTRAP] [debug] Client connected
info: [debug] [BOOTSTRAP] [debug] Got data from client: {“cmd”:“action”,“action”:“wake”,“params”:{}}
info: [debug] [BOOTSTRAP] [debug] Got command of type ACTION
info: [debug] [BOOTSTRAP] [debug] Got command action: wake
info: [debug] [BOOTSTRAP] [debug] Returning result: {“status”:0,“value”:true}
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “dumpsys window”
info: [debug] Screen already unlocked, continuing.
info: [debug] Pushing command to appium work queue: [“getDataDir”,{}]
info: [debug] [BOOTSTRAP] [debug] Got data from client: {“cmd”:“action”,“action”:“getDataDir”,“params”:{}}
info: [debug] [BOOTSTRAP] [debug] Got command of type ACTION
info: [debug] [BOOTSTRAP] [debug] Got command action: getDataDir
info: [debug] [BOOTSTRAP] [debug] Returning result: {“status”:0,“value”:“/data/local/tmp”}
info: [debug] dataDir set to: /data/local/tmp
info: [debug] Pushing command to appium work queue: [“compressedLayoutHierarchy”,{“compressLayout”:false}]
info: [debug] [BOOTSTRAP] [debug] Got data from client: {“cmd”:“action”,“action”:“compressedLayoutHierarchy”,“params”:{“compressLayout”:false}}
info: [debug] [BOOTSTRAP] [debug] Got command of type ACTION
info: [debug] [BOOTSTRAP] [debug] Got command action: compressedLayoutHierarchy
info: [debug] [BOOTSTRAP] [debug] Returning result: {“status”:0,“value”:false}
info: [debug] Getting device API level
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “getprop ro.build.version.sdk”
info: [debug] Device is at API Level 22
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “am start -S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000 -n com.dummyApp/com.dummyApp.activity.SplashActivity”
info: [debug] Waiting for pkg “com.dummyApp” and activity “com.dummyApp.activity.SplashActivity” to be focused
info: [debug] Getting focused package and activity
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “dumpsys window windows”
info: [debug] Getting focused package and activity
info: [debug] executing cmd: D:\OLDSYSTEMBACKUP\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platform-tools\adb.exe -s HT4AZJT00764 shell “dumpsys window windows”
error: com.dummyApp/.activity.SplashActivity never started. Current: com.dummyApp/.activity.GatewayDiscoveryActivity
info: [debug] Stopping logcat capture
info: [debug] Logcat terminated with code null, signal SIGTERM
info: [debug] [BOOTSTRAP] [debug] Got data from client: {“cmd”:“shutdown”}
info: [debug] [BOOTSTRAP] [debug] Got command of type SHUTDOWN
info: [debug] [BOOTSTRAP] [debug] Returning result: {“status”:0,“value”:“OK, shutting down”}
info: [debug] [BOOTSTRAP] [debug] Closed client connection
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=.
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 0
info: [debug] Sent shutdown command, waiting for UiAutomator to stop…
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
info: [debug] [UIAUTOMATOR STDOUT] Test results for WatcherResultPrinter=.
info: [debug] [UIAUTOMATOR STDOUT] Time: 22.099
info: [debug] [UIAUTOMATOR STDOUT] OK (1 test)
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: -1
info: [debug] UiAutomator shut down normally
info: [debug] Cleaning up android objects
info: [debug] Cleaning up appium session
info: [debug] Error: com.dummyApp/.activity.SplashActivity never started. Current: com.dummyApp/.activity.GatewayDiscoveryActivity
at [object Object]. (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-adb\lib\adb.js:1314:12)
at [object Object]. (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-adb\lib\adb.js:1258:7)
at [object Object]. (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-adb\lib\adb.js:180:9)
at ChildProcess.exithandler (child_process.js:742:7)
at ChildProcess.emit (events.js:110:17)
at maybeClose (child_process.js:1016:16)
at Process.ChildProcess._handle.onexit (child_process.js:1088:5)
info: [debug] Responding to client with error: {“status”:33,“value”:{“message”:“A new session could not be created. (Original error: com.dummyApp/.activity.SplashActivity never started. Current: com.dummyApp/.activity.GatewayDiscoveryActivity)”,“origValue”:“com.dummyApp/.activity.SplashActivity never started. Current: com.dummyApp/.activity.GatewayDiscoveryActivity”},“sessionId”:null}
info: ← POST /wd/hub/session 500 25876.291 ms - 360

Looks like you are picking up some old/bad tools. I would try setting up again from scratch. Sometimes a system is in such a bad state that you just have to start over.

Can u share your code @anjalijaiswal0990