-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Different results when using package param to start app #151
Comments
@StephenMok1997 Hmm, if you use var sApp = startApp.set({
"action":"ACTION_MAIN",
"package":"com.lampa.startapp"
}); But if we need only start app with package name, without action or activity, we need to use parameter var sApp = startApp.set({
"application":"com.application.name"
}).start(); |
So any possible reason that some app can start and some app cannot? |
@StephenMok1997 error indicates that the main activity not found in the application (perhaps for |
What do you mean by device interface? |
Android Launcher |
No |
So you need to get the package name and the activity name of application for start application, example: var sApp = startApp.set({
"component": ["com.app.name","com.app.name.QrScannerActivity"]
}).start(); You can get package name and activity name by decompiling application and looking at its |
I have an old application which use package name to check app and start app. I found that some apps can be started with package and some are not. For example,
In App A, I check the app is installed in the device and start app is succeeded.
In App B, I also check the app is installed but cannot start app and receive android.content.ActiveityNotFoundException: No Activity found to handle Intent ( package name }.
Although I am able to use application and intentstart to start app, what is the reason of above problem?
The text was updated successfully, but these errors were encountered: