Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

1.5.2 - Android MainActivity is never detected by Appium

See original GitHub issue

The problem

I already filed this against the beta1.5 version here and it got closed as a duplicate… but it is still failing on 1.5.2. For reference https://github.com/appium/appium/issues/6020

Our main App activity never manages to be detected as launched even though it is and I can visually confirm this.

The error message is as such:

[MJSONWP] Encountered internal error running command: Error: Error occured while starting App. Original error: me.app.android.dev/me.app.android.ui.MainActivity never started
    at Object.wrappedLogger.errorAndThrow (lib/logger.js:60:13)
    at ADB.callee$0$0$ (lib/tools/apk-utils.js:80:9)
    at tryCatch (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:67:40)
    at GeneratorFunctionPrototype.invoke [as _invoke] (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:315:22)
    at GeneratorFunctionPrototype.prototype.(anonymous function) [as throw] (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:100:21)
    at GeneratorFunctionPrototype.invoke (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/regenerator/runtime.js:136:37)
    at run (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/node_modules/core-js/library/modules/es6.promise.js:104:47)
    at /usr/local/lib/node_modules/appium/node_modules/babel-runtime/node_modules/core-js/library/modules/es6.promise.js:115:28
    at flush (/usr/local/lib/node_modules/appium/node_modules/babel-runtime/node_modules/core-js/library/modules/$.microtask.js:19:5)
    at process._tickCallback (node.js:355:11)

Here is a gist to the full logs: https://gist.github.com/apallin/5d76b0297d8c0d9b111817d724536eaf

Environment

Appium 1.5.2
Last Appium to work 1.4.16
Mac OSX 10.11.4 (15E65)
Node version v0.12.2
Mobile version Android 4.4.2
Real Device
Appium CLI

Issue Analytics

State:
Created 7 years ago
Comments:25 (8 by maintainers)

Top GitHub Comments

1reaction

103683commented, Mar 13, 2017

i have the same issue.

0reactions

lock[bot]commented, Apr 25, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Top Results From Across the Web

Main activity launches too quickly so Appium doesn't recognize it

I'm having an issue where my main activity launches and moves to the next activity so quickly, that appium thinks it never launches....

Android on appium 1.6: 'Incorrect package and activity.' error

I'm guessing that for some reason appium 1.5.3 is picking the correct appActivity while 1.6.0beta3 is not? I don't have appActivity specified on ......

(Appium-Android)cannot read the application activity getting ...

The strange thing is that it only happens in my emulator (Genymotion), when I try my code in the real device it works...

Activities Startup Troubleshooting Guide - Appium

If they are not set explicitly then Appium tries to auto detect them by reading their values from the APK manifest. Although, if...

SplashActivity_' never started - Support - Appium Discuss

MainActivity -S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000 . java.lang.IllegalArgumentException: Bad component name: ...