Incorrect package and activity. Retrying in Appium 1.6.4

I’m using Appium 1.6.4-beta.2 version and testing in Android 7.0 platform.

Error in console

Exception in thread “main” org.openqa.selenium.WebDriverException: An unknown server-side error occurred while processing the command. Original error: Error occured while starting App. Original error: com.medlink.mehdi.tavietest/com.medlink.mehdi.tavie.SplashScreen or com.medlink.mehdi.tavietest.com.medlink.mehdi.tavie.SplashScreen never started (WARNING: The server did not provide any stacktrace information.

Here’s my log

,“windows”]
[debug] [ADB] Found package: ‘com.medlink.mehdi.tavietest’ and fully qualified a
ctivity name : ‘com.medlink.mehdi.tavie.RegisterMainActivity’
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Getting connected devices…
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running ‘C:\Users\Raghuram\AppData\Local\Android\sdk\platform-tool
s\adb.exe’ with args: ["-P",5037,"-s",“emulator-5554”,“shell”,“dumpsys”,“window”
,“windows”]
[debug] [ADB] Found package: ‘com.medlink.mehdi.tavietest’ and fully qualified a
ctivity name : ‘com.medlink.mehdi.tavie.RegisterMainActivity’
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Getting connected devices…
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running ‘C:\Users\Raghuram\AppData\Local\Android\sdk\platform-tool
s\adb.exe’ with args: ["-P",5037,"-s",“emulator-5554”,“shell”,“dumpsys”,“window”
,“windows”]
[debug] [ADB] Found package: ‘com.medlink.mehdi.tavietest’ and fully qualified a
ctivity name : ‘com.medlink.mehdi.tavie.RegisterMainActivity’
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Getting connected devices…
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running ‘C:\Users\Raghuram\AppData\Local\Android\sdk\platform-tool
s\adb.exe’ with args: ["-P",5037,"-s",“emulator-5554”,“shell”,“dumpsys”,“window”
,“windows”]
[debug] [ADB] Found package: ‘com.medlink.mehdi.tavietest’ and fully qualified a
ctivity name : ‘com.medlink.mehdi.tavie.RegisterMainActivity’
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Getting connected devices…
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running ‘C:\Users\Raghuram\AppData\Local\Android\sdk\platform-tool
s\adb.exe’ with args: ["-P",5037,"-s",“emulator-5554”,“shell”,“dumpsys”,“window”
,“windows”]
[debug] [ADB] Found package: ‘com.medlink.mehdi.tavietest’ and fully qualified a
ctivity name : ‘com.medlink.mehdi.tavie.RegisterMainActivity’
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Getting connected devices…
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running ‘C:\Users\Raghuram\AppData\Local\Android\sdk\platform-tool
s\adb.exe’ with args: ["-P",5037,"-s",“emulator-5554”,“shell”,“dumpsys”,“window”
,“windows”]
[debug] [ADB] Found package: ‘com.medlink.mehdi.tavietest’ and fully qualified a
ctivity name : ‘com.medlink.mehdi.tavie.RegisterMainActivity’
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Getting connected devices…
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running ‘C:\Users\Raghuram\AppData\Local\Android\sdk\platform-tool
s\adb.exe’ with args: ["-P",5037,"-s",“emulator-5554”,“shell”,“dumpsys”,“window”
,“windows”]
[debug] [ADB] Found package: ‘com.medlink.mehdi.tavietest’ and fully qualified a
ctivity name : ‘com.medlink.mehdi.tavie.RegisterMainActivity’
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Getting connected devices…
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running ‘C:\Users\Raghuram\AppData\Local\Android\sdk\platform-tool
s\adb.exe’ with args: ["-P",5037,"-s",“emulator-5554”,“shell”,“dumpsys”,“window”
,“windows”]
[debug] [ADB] Found package: ‘com.medlink.mehdi.tavietest’ and fully qualified a
ctivity name : ‘com.medlink.mehdi.tavie.RegisterMainActivity’
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Getting connected devices…
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running ‘C:\Users\Raghuram\AppData\Local\Android\sdk\platform-tool
s\adb.exe’ with args: ["-P",5037,"-s",“emulator-5554”,“shell”,“dumpsys”,“window”
,“windows”]
[debug] [ADB] Found package: ‘com.medlink.mehdi.tavietest’ and fully qualified a
ctivity name : ‘com.medlink.mehdi.tavie.RegisterMainActivity’
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Getting connected devices…
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running ‘C:\Users\Raghuram\AppData\Local\Android\sdk\platform-tool
s\adb.exe’ with args: ["-P",5037,"-s",“emulator-5554”,“shell”,“dumpsys”,“window”
,“windows”]
[debug] [ADB] Found package: ‘com.medlink.mehdi.tavietest’ and fully qualified a
ctivity name : ‘com.medlink.mehdi.tavie.RegisterMainActivity’
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Getting connected devices…
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running ‘C:\Users\Raghuram\AppData\Local\Android\sdk\platform-tool
s\adb.exe’ with args: ["-P",5037,"-s",“emulator-5554”,“shell”,“dumpsys”,“window”
,“windows”]
[debug] [ADB] Found package: ‘com.medlink.mehdi.tavietest’ and fully qualified a
ctivity name : ‘com.medlink.mehdi.tavie.RegisterMainActivity’
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Getting connected devices…
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running ‘C:\Users\Raghuram\AppData\Local\Android\sdk\platform-tool
s\adb.exe’ with args: ["-P",5037,"-s",“emulator-5554”,“shell”,“dumpsys”,“window”
,“windows”]
[debug] [ADB] Found package: ‘com.medlink.mehdi.tavietest’ and fully qualified a
ctivity name : ‘com.medlink.mehdi.tavie.RegisterMainActivity’
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Getting connected devices…
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running ‘C:\Users\Raghuram\AppData\Local\Android\sdk\platform-tool
s\adb.exe’ with args: ["-P",5037,"-s",“emulator-5554”,“shell”,“dumpsys”,“window”
,“windows”]
[debug] [ADB] Found package: ‘com.medlink.mehdi.tavietest’ and fully qualified a
ctivity name : ‘com.medlink.mehdi.tavie.RegisterMainActivity’
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Getting connected devices…
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running ‘C:\Users\Raghuram\AppData\Local\Android\sdk\platform-tool
s\adb.exe’ with args: ["-P",5037,"-s",“emulator-5554”,“shell”,“dumpsys”,“window”
,“windows”]
[debug] [ADB] Found package: ‘com.medlink.mehdi.tavietest’ and fully qualified a
ctivity name : ‘com.medlink.mehdi.tavie.RegisterMainActivity’
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Getting connected devices…
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running ‘C:\Users\Raghuram\AppData\Local\Android\sdk\platform-tool
s\adb.exe’ with args: ["-P",5037,"-s",“emulator-5554”,“shell”,“dumpsys”,“window”
,“windows”]
[debug] [ADB] Found package: ‘com.medlink.mehdi.tavietest’ and fully qualified a
ctivity name : ‘com.medlink.mehdi.tavie.RegisterMainActivity’
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Getting connected devices…
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running ‘C:\Users\Raghuram\AppData\Local\Android\sdk\platform-tool
s\adb.exe’ with args: ["-P",5037,"-s",“emulator-5554”,“shell”,“dumpsys”,“window”
,“windows”]
[debug] [ADB] Found package: ‘com.medlink.mehdi.tavietest’ and fully qualified a
ctivity name : ‘com.medlink.mehdi.tavie.RegisterMainActivity’
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Getting connected devices…
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running ‘C:\Users\Raghuram\AppData\Local\Android\sdk\platform-tool
s\adb.exe’ with args: ["-P",5037,"-s",“emulator-5554”,“shell”,“dumpsys”,“window”
,“windows”]
[debug] [ADB] Found package: ‘com.medlink.mehdi.tavietest’ and fully qualified a
ctivity name : ‘com.medlink.mehdi.tavie.RegisterMainActivity’
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Getting connected devices…
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running ‘C:\Users\Raghuram\AppData\Local\Android\sdk\platform-tool
s\adb.exe’ with args: ["-P",5037,"-s",“emulator-5554”,“shell”,“dumpsys”,“window”
,“windows”]
[debug] [ADB] Found package: ‘com.medlink.mehdi.tavietest’ and fully qualified a
ctivity name : ‘com.medlink.mehdi.tavie.RegisterMainActivity’
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Getting connected devices…
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running ‘C:\Users\Raghuram\AppData\Local\Android\sdk\platform-tool
s\adb.exe’ with args: ["-P",5037,"-s",“emulator-5554”,“shell”,“dumpsys”,“window”
,“windows”]
[debug] [ADB] Found package: ‘com.medlink.mehdi.tavietest’ and fully qualified a
ctivity name : ‘com.medlink.mehdi.tavie.RegisterMainActivity’
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Getting connected devices…
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running ‘C:\Users\Raghuram\AppData\Local\Android\sdk\platform-tool
s\adb.exe’ with args: ["-P",5037,"-s",“emulator-5554”,“shell”,“dumpsys”,“window”
,“windows”]
[debug] [ADB] Found package: ‘com.medlink.mehdi.tavietest’ and fully qualified a
ctivity name : ‘com.medlink.mehdi.tavie.RegisterMainActivity’
[debug] [ADB] Incorrect package and activity. Retrying.
[debug] [ADB] Getting focused package and activity
[debug] [ADB] Getting connected devices…
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running ‘C:\Users\Raghuram\AppData\Local\Android\sdk\platform-tool
s\adb.exe’ with args: ["-P",5037,"-s",“emulator-5554”,“shell”,“dumpsys”,“window”
,“windows”]
[debug] [ADB] Found package: ‘com.medlink.mehdi.tavietest’ and fully qualified a
ctivity name : ‘com.medlink.mehdi.tavie.RegisterMainActivity’
[debug] [ADB] Incorrect package and activity. Retrying.
[ADB] Error: com.medlink.mehdi.tavietest/com.medlink.mehdi.tavie.SplashScreen or
com.medlink.mehdi.tavietest.com.medlink.mehdi.tavie.SplashScreen never started
at Object.wrappedLogger.errorAndThrow (…/…/lib/logging.js:63:13)
at ADB.callee$0$0$ (…/…/…/lib/tools/apk-utils.js:147:7)
at tryCatch (C:\Users\Raghuram\AppData\Roaming\npm\node_modules\appium\node_
modules\babel-runtime\regenerator\runtime.js:67:40)
at GeneratorFunctionPrototype.invoke [as invoke] (C:\Users\Raghuram\AppData
\Roaming\npm\node_modules\appium\node_modules\babel-runtime\regenerator\runtime.
js:315:22)
at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (C:\U
sers\Raghuram\AppData\Roaming\npm\node_modules\appium\node_modules\babel-runtime
\regenerator\runtime.js:100:21)
at GeneratorFunctionPrototype.invoke (C:\Users\Raghuram\AppData\Roaming\npm
node_modules\appium\node_modules\babel-runtime\regenerator\runtime.js:136:37)
Error: com.medlink.mehdi.tavietest/com.medlink.mehdi.tavie.SplashScreen or com.
medlink.mehdi.tavietest.com.medlink.mehdi.tavie.SplashScreen never started
at Object.wrappedLogger.errorAndThrow (…/…/lib/logging.js:63:13)
at ADB.callee$0$0$ (…/…/…/lib/tools/apk-utils.js:147:7)
at tryCatch (C:\Users\Raghuram\AppData\Roaming\npm\node_modules\appium\node

modules\babel-runtime\regenerator\runtime.js:67:40)
at GeneratorFunctionPrototype.invoke [as invoke] (C:\Users\Raghuram\AppData
\Roaming\npm\node_modules\appium\node_modules\babel-runtime\regenerator\runtime.
js:315:22)
at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (C:\U
sers\Raghuram\AppData\Roaming\npm\node_modules\appium\node_modules\babel-runtime
\regenerator\runtime.js:100:21)
at GeneratorFunctionPrototype.invoke (C:\Users\Raghuram\AppData\Roaming\npm
node_modules\appium\node_modules\babel-runtime\regenerator\runtime.js:136:37)
[ADB] Error: Error occured while starting App. Original error: com.medlink.mehdi
.tavietest/com.medlink.mehdi.tavie.SplashScreen or com.medlink.mehdi.tavietest.c
om.medlink.mehdi.tavie.SplashScreen never started
at Object.wrappedLogger.errorAndThrow (…/…/lib/logging.js:63:13)
at ADB.callee$0$0$ (…/…/…/lib/tools/apk-utils.js:77:9)
at tryCatch (C:\Users\Raghuram\AppData\Roaming\npm\node_modules\appium\node

modules\babel-runtime\regenerator\runtime.js:67:40)
at GeneratorFunctionPrototype.invoke [as invoke] (C:\Users\Raghuram\AppData
\Roaming\npm\node_modules\appium\node_modules\babel-runtime\regenerator\runtime.
js:315:22)
at GeneratorFunctionPrototype.prototype.(anonymous function) [as throw] (C:
Users\Raghuram\AppData\Roaming\npm\node_modules\appium\node_modules\babel-runtim
e\regenerator\runtime.js:100:21)
at GeneratorFunctionPrototype.invoke (C:\Users\Raghuram\AppData\Roaming\npm
node_modules\appium\node_modules\babel-runtime\regenerator\runtime.js:136:37)
Error: Error occured while starting App. Original error: com.medlink.mehdi.tavi
etest/com.medlink.mehdi.tavie.SplashScreen or com.medlink.mehdi.tavietest.com.me
dlink.mehdi.tavie.SplashScreen never started
at Object.wrappedLogger.errorAndThrow (…/…/lib/logging.js:63:13)
at ADB.callee$0$0$ (…/…/…/lib/tools/apk-utils.js:77:9)
at tryCatch (C:\Users\Raghuram\AppData\Roaming\npm\node_modules\appium\node

modules\babel-runtime\regenerator\runtime.js:67:40)
at GeneratorFunctionPrototype.invoke [as invoke] (C:\Users\Raghuram\AppData
\Roaming\npm\node_modules\appium\node_modules\babel-runtime\regenerator\runtime.
js:315:22)
at GeneratorFunctionPrototype.prototype.(anonymous function) [as throw] (C:
Users\Raghuram\AppData\Roaming\npm\node_modules\appium\node_modules\babel-runtim
e\regenerator\runtime.js:100:21)
at GeneratorFunctionPrototype.invoke (C:\Users\Raghuram\AppData\Roaming\npm
node_modules\appium\node_modules\babel-runtime\regenerator\runtime.js:136:37)
[debug] [AndroidDriver] Shutting down Android driver
[debug] [ADB] Getting connected devices…
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running ‘C:\Users\Raghuram\AppData\Local\Android\sdk\platform-tool
s\adb.exe’ with args: ["-P",5037,"-s",“emulator-5554”,“shell”,“am”,“force-stop”,
“com.medlink.mehdi.tavietest”]
[debug] [ADB] Pressing the HOME button
[debug] [ADB] Getting connected devices…
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running ‘C:\Users\Raghuram\AppData\Local\Android\sdk\platform-tool
s\adb.exe’ with args: ["-P",5037,"-s",“emulator-5554”,“shell”,“input”,“keyevent”
,3]
[debug] [AndroidBootstrap] Sending command to android: {“cmd”:“shutdown”}
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Got data from client: {“cmd”:“shutdow
n”}
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Got command of type SHUTDOWN
[debug] [AndroidBootstrap] Received command result from bootstrap
[debug] [UiAutomator] Shutting down UiAutomator
[debug] [UiAutomator] Moving to state ‘stopping’
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Returning result: {“status”:0,“value”
:“OK, shutting down”}
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Closed client connection
[debug] [UiAutomator] UiAutomator shut down normally
[debug] [UiAutomator] Moving to state ‘stopped’
[debug] [ADB] Attempting to kill all uiautomator processes
[debug] [ADB] Getting all processes with uiautomator
[debug] [ADB] Getting connected devices…
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running ‘C:\Users\Raghuram\AppData\Local\Android\sdk\platform-tool
s\adb.exe’ with args: ["-P",5037,"-s",“emulator-5554”,“shell”,“ps”]
[ADB] No uiautomator process found to kill, continuing…
[debug] [UiAutomator] Moving to state ‘stopped’
[debug] [Logcat] Stopping logcat capture
[debug] [ADB] Getting connected devices…
[debug] [ADB] 1 device(s) connected
[debug] [ADB] Running ‘C:\Users\Raghuram\AppData\Local\Android\sdk\platform-tool
s\adb.exe’ with args: ["-P",5037,"-s",“emulator-5554”,“shell”,“am”,“force-stop”,
“io.appium.unlock”]
[debug] [AndroidDriver] Not cleaning generated files. Add clearSystemFiles cap
ability if wanted.
[MJSONWP] Encountered internal error running command: Error: Error occured while
starting App. Original error: com.medlink.mehdi.tavietest/com.medlink.mehdi.tav
ie.SplashScreen or com.medlink.mehdi.tavietest.com.medlink.mehdi.tavie.SplashScr
een never started
at Object.wrappedLogger.errorAndThrow (…/…/lib/logging.js:63:13)
at ADB.callee$0$0$ (…/…/…/lib/tools/apk-utils.js:77:9)
at tryCatch (C:\Users\Raghuram\AppData\Roaming\npm\node_modules\appium\node

modules\babel-runtime\regenerator\runtime.js:67:40)
at GeneratorFunctionPrototype.invoke [as _invoke] (C:\Users\Raghuram\AppData
\Roaming\npm\node_modules\appium\node_modules\babel-runtime\regenerator\runtime.
js:315:22)
at GeneratorFunctionPrototype.prototype.(anonymous function) [as throw] (C:
Users\Raghuram\AppData\Roaming\npm\node_modules\appium\node_modules\babel-runtim
e\regenerator\runtime.js:100:21)
at GeneratorFunctionPrototype.invoke (C:\Users\Raghuram\AppData\Roaming\npm
node_modules\appium\node_modules\babel-runtime\regenerator\runtime.js:136:37)
[HTTP] <-- POST /wd/hub/session 500 50199 ms - 333

Here’s my code in eclipse

package utility;

import java.io.File;
import java.net.MalformedURLException;
import java.net.URL;

import org.openqa.selenium.remote.DesiredCapabilities;

import io.appium.java_client.android.AndroidDriver;
import io.appium.java_client.android.AndroidElement;
import io.appium.java_client.remote.MobileCapabilityType;

public class Setup {

public static void main(String[] args) throws MalformedURLException, InterruptedException {
	// TODO Auto-generated method stub
	
	File tavie_hiv_apk_folder=new File("src/test/java"); //Go to source folder
	File tavie_hiv_apk=new File(tavie_hiv_apk_folder, "app-TAVIETEST-debug.apk"); //Pulling out apk file and assigning to fil

	
	DesiredCapabilities tavieDc=new DesiredCapabilities();
	tavieDc.setCapability(MobileCapabilityType.DEVICE_NAME, "TavieHIV"); //Emulator name
	tavieDc.setCapability(MobileCapabilityType.APP, tavie_hiv_apk.getAbsolutePath());

	
	
	AndroidDriver<AndroidElement> driver=new AndroidDriver<AndroidElement>(new URL("http://127.0.0.1:4723/wd/hub"),tavieDc);
	
	System.out.println(driver.findElementByXPath("//android.widget.TextView[@index=0]").getText());
	
}
1 Like

Faced with the same issue, after each test app start from the previous test activity but not reseting and starting from the ground up since i started using uiautomator2

Try adding below code:

tavieDc.setCapability(“appActivity”, “com.medlink.mehdi.tavie.RegisterMainActivity”);

Best solution is wildcast :slight_smile:

capabilities.setCapability(MobileCapabilityType.APP, appDir.getAbsolutePath());
capabilities.setCapability(AndroidMobileCapabilityType.APP_WAIT_ACTIVITY, "com.medlink.*"); 

This issue may also occur if the appium is not installed properly (or) if you have multiple versions of appium in your machine.

so , please uninstall them and reinstall it.

This should work. :slight_smile: