App is not launching


#1

snapshot of the capabilities is attached and all applications are up to date.

Appium leaves the following error:

An unknown server-side error occurred while processing the command. Original error: Cannot start the ‘com.psav.lighthousedev’ application. Visit https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/android/activity-startup.md for troubleshooting. Original error: Error executing adbExec. Original error: ‘Command ‘‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe’ -P 5037 -s emulator-5554 shell am start -W -n com.psav.lighthousedev/md531e465ed3d5776cb0141b60c4e472cb5.MainActivity -S’ exited with code 4294967295’; Stderr: 'Security exception: Permission Denial: starting Intent { flg=0x10000000 cmp=com.psav.lighthousedev/md531e465ed3d5776cb0141b60c4e472cb5.MainActivity } from null (pid=26364, uid=2000) not exported from uid 10083

java.lang.SecurityException: Permission Denial: starting Intent { flg=0x10000000 cmp=com.psav.lighthousedev/md531e465ed3d5776cb0141b60c4e472cb5.MainActivity } from null (pid=26364, uid=2000) not exported from uid 10083
at com.android.server.am.ActivityStackSupervisor.checkStartAnyActivityPermission(ActivityStackSupervisor.java:1632)
at com.android.server.am.ActivityStarter.startActivity(ActivityStarter.java:438)
at com.android.server.am.ActivityStarter.startActivityLocked(ActivityStarter.java:278)
at com.android.server.am.ActivityStarter.startActivityMayWait(ActivityStarter.java:817)
at com.android.server.am.ActivityManagerService.startActivityAndWait(ActivityManagerService.java:4625)
at com.android.server.am.ActivityManagerShellCommand.runStartActivity(ActivityManagerShellCommand.java:412)
at com.android.server.am.ActivityManagerShellCommand.onCommand(ActivityManagerShellCommand.java:141)
at android.os.ShellCommand.exec(ShellCommand.java:96)
at com.android.server.am.ActivityManagerService.onShellCommand(ActivityManagerService.java:15014)
at android.os.Binder.shellCommand(Binder.java:594)
at android.os.Binder.onTransact(Binder.java:492)
at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:4243)
at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2919)
at android.os.Binder.execTransact(Binder.java:697)’; Code: ‘4294967295’

The appium log :

[HTTP] --> POST /wd/hub/session
[HTTP] {“desiredCapabilities”:{“Udid”:“emulator-5554”,“appActivity”:“md531e465ed3d5776cb0141b60c4e472cb5.MainActivity”,“appPackage”:“com.psav.lighthousedev”,“appWaitActivity”:“md531e465ed3d5776cb0141b60c4e472cb5.SplashActivity”,“autoGrantPermissions”:“true”,“deviceName”:“Android25”,“platformName”:“Android”,“newCommandTimeout”:0,“connectHardwareKeyboard”:true}}
[MJSONWP] Calling AppiumDriver.createSession() with args: [{“Udid”:“emulator-5554”,“appActivity”:“md531e465ed3d5776cb0141b60c4e472cb5.MainActivity”,“appPackage”:“com.psav.lighthousedev”,“appWaitActivity”:“md531e465ed3d5776cb0141b60c4e472cb5.SplashActivity”,“autoGrantPermissions”:“true”,“deviceName”:“Android25”,“platformName”:“Android”,“newCommandTimeout”:0,“connectHardwareKeyboard”:true},null,null]
[BaseDriver] Event ‘newSessionRequested’ logged at 1538378328448 (12:48:48 GMT+0530 (India Standard Time))
[Appium] Creating new AndroidDriver (v4.1.1) session
[Appium] Capabilities:
[Appium] Udid: emulator-5554
[Appium] appActivity: md531e465ed3d5776cb0141b60c4e472cb5.MainActivity
[Appium] appPackage: com.psav.lighthousedev
[Appium] appWaitActivity: md531e465ed3d5776cb0141b60c4e472cb5.SplashActivity
[Appium] autoGrantPermissions: true
[Appium] deviceName: Android25
[Appium] platformName: Android
[Appium] newCommandTimeout: 0
[Appium] connectHardwareKeyboard: true
[BaseDriver] Creating session with MJSONWP desired capabilities: {“Udid”:“emulator-5554”,“ap…
[BaseDriver] Capability ‘autoGrantPermissions’ changed from string to boolean. This may cause unexpected behavior
[BaseDriver] The following capabilities were provided, but are not recognized by appium: Udid, connectHardwareKeyboard.
[BaseDriver] Session created with session id: dc88a0b1-b077-48c4-b582-eb33371ff769
[AndroidDriver] Java version is: 10.0.2
[AndroidDriver] Retrieving device list
[ADB] Trying to find a connected android device
[ADB] Getting connected devices…
[ADB] 1 device(s) connected
[AndroidDriver] Using device: emulator-5554
[ADB] Setting device id to emulator-5554
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell getprop ro.build.version.sdk’
[ADB] Current device property ‘ro.build.version.sdk’: 27
[ADB] Device API level: 27
[AndroidDriver] Consider setting ‘automationName’ capability to ‘uiautomator2’ on Android >= 6, since UIAutomator framework is not maintained anymore by the OS vendor.
[AndroidDriver] App file was not listed, instead we’re going to run com.psav.lighthousedev directly on the device
[AndroidDriver] Checking whether package is present on the device
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell pm list packages com.psav.lighthousedev’
[AndroidDriver] Starting Android session
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 wait-for-device’
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell echo ping’
[AndroidDriver] Pushing settings apk to device…
[ADB] Getting install status for io.appium.settings
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell pm list packages io.appium.settings’
[ADB] App is installed
[ADB] Getting package info for ‘io.appium.settings’
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys package io.appium.settings’
[ADB] The installed ‘io.appium.settings’ package does not require upgrade (‘2.3.0’ >= ‘2.3.0’)
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell ps’
[AndroidDriver] io.appium.settings is already running. There is no need to reset its permissions.
[ADB] Device API level: 27
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell appops set io.appium.settings android:mock_location allow’
[AndroidDriver] setDeviceLanguageCountry requires language or country.
[AndroidDriver] Got language: ‘undefined’ and country: ‘undefined’
[Logcat] Starting logcat capture
[AndroidDriver] Pushing unlock helper app to device…
[ADB] Getting install status for io.appium.unlock
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell pm list packages io.appium.unlock’
[ADB] App is installed
[ADB] Getting package info for ‘io.appium.unlock’
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys package io.appium.unlock’
[ADB] The installed ‘io.appium.unlock’ package does not require upgrade (‘2.0.0’ >= ‘2.0.0’)
[ADB] Getting device platform version
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell getprop ro.build.version.release’
[ADB] Current device property ‘ro.build.version.release’: 8.1.0
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell wm size’
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell getprop ro.product.model’
[ADB] Current device property ‘ro.product.model’: Android SDK built for x86
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell getprop ro.product.manufacturer’
[ADB] Current device property ‘ro.product.manufacturer’: Google
[AndroidDriver] No app sent in, not parsing package/activity
[AndroidDriver] No app capability. Assuming it is already on the device
[ADB] Getting install status for com.psav.lighthousedev
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell pm list packages com.psav.lighthousedev’
[ADB] App is installed
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell am force-stop com.psav.lighthousedev’
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell pm clear com.psav.lighthousedev’
[ADB] Device API level: 27
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys package com.psav.lighthousedev’
[AndroidDriver] Performed fast reset on the installed ‘com.psav.lighthousedev’ application (stop and clear)
[AndroidBootstrap] Watching for bootstrap disconnect
[ADB] Forwarding system: 4724 to device: 4724
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 forward tcp:4724 tcp:4724’
[UiAutomator] Starting UiAutomator
[UiAutomator] Moving to state ‘starting’
[UiAutomator] Parsing uiautomator jar
[UiAutomator] Found jar name: ‘AppiumBootstrap.jar’
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 push ‘C:\Program Files (x86)\Appium\resources\app\node_modules\appium\node_modules\appium-android-driver\bootstrap\bin\AppiumBootstrap.jar’ /data/local/tmp/’
[ADB] Attempting to kill all uiautomator processes
[ADB] Getting all processes with uiautomator
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell ps’
[ADB] No uiautomator process found to kill, continuing…
[UiAutomator] Starting UIAutomator
[ADB] Creating ADB subprocess with args: [”-P",5037,"-s",“emulator-5554”,“shell”,“uiautomator”,“runtest”,“AppiumBootstrap.jar”,"-c",“io.appium.android.bootstrap.Bootstrap”,"-e",“pkg”,“com.psav.lighthousedev”,"-e",“disableAndroidWatchers”,false,"-e",“acceptSslCerts”,false]
[UiAutomator] Moving to state ‘online’
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] json loading complete.
[AndroidBootstrap] Android bootstrap socket is now connected
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell dumpsys window’
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Registered crash watchers.
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Client connected
[AndroidDriver] Screen already unlocked, doing nothing
[ADB] Device API level: 27
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell am start -W -n com.psav.lighthousedev/md531e465ed3d5776cb0141b60c4e472cb5.MainActivity -S’
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell am start -W -n com.psav.lighthousedev/md531e465ed3d5776cb0141b60c4e472cb5.MainActivity -S’
[AndroidDriver] Shutting down Android driver
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell am force-stop com.psav.lighthousedev’
[ADB] Pressing the HOME button
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell input keyevent 3’
[AndroidBootstrap] Sending command to android: {“cmd”:“shutdown”}
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Got data from client: {“cmd”:“shutdown”}
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Got command of type SHUTDOWN
[AndroidBootstrap] Received command result from bootstrap
[UiAutomator] Shutting down UiAutomator
[UiAutomator] Moving to state ‘stopping’
[AndroidBootstrap] [BOOTSTRAP LOG] [debug] Returning result: {“status”:0,“value”:“OK, shutting down”}
[UiAutomator] UiAutomator shut down normally
[UiAutomator] Moving to state ‘stopped’
[ADB] Attempting to kill all uiautomator processes
[ADB] Getting all processes with uiautomator
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell ps’
[ADB] No uiautomator process found to kill, continuing…
[UiAutomator] Moving to state ‘stopped’
[Logcat] Stopping logcat capture
[ADB] Running ‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -P 5037 -s emulator-5554 shell am force-stop io.appium.unlock’
[AndroidDriver] Not cleaning generated files. Add clearSystemFiles capability if wanted.
[BaseDriver] Event ‘newSessionStarted’ logged at 1538378333650 (12:48:53 GMT+0530 (India Standard Time))
[MJSONWP] Encountered internal error running command: Error: Cannot start the ‘com.psav.lighthousedev’ application. Visit https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/android/activity-startup.md for troubleshooting. Original error: Error executing adbExec. Original error: ‘Command ‘‘C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe’ -P 5037 -s emulator-5554 shell am start -W -n com.psav.lighthousedev/md531e465ed3d5776cb0141b60c4e472cb5.MainActivity -S’ exited with code 4294967295’; Stderr: ‘Security exception: Permission Denial: starting Intent { flg=0x10000000 cmp=com.psav.lighthousedev/md531e465ed3d5776cb0141b60c4e472cb5.MainActivity } from null (pid=26780, uid=2000) not exported from uid 10083
[MJSONWP]
[MJSONWP] java.lang.SecurityException: Permission Denial: starting Intent { flg=0x10000000 cmp=com.psav.lighthousedev/md531e465ed3d5776cb0141b60c4e472cb5.MainActivity } from null (pid=26780, uid=2000) not exported from uid 10083
[MJSONWP] at com.android.server.am.ActivityStackSupervisor.checkStartAnyActivityPermission(ActivityStackSupervisor.java:1632)
[MJSONWP] at com.android.server.am.ActivityStarter.startActivity(ActivityStarter.java:438)
[MJSONWP] at com.android.server.am.ActivityStarter.startActivityLocked(ActivityStarter.java:278)
[MJSONWP] at com.android.server.am.ActivityStarter.startActivityMayWait(ActivityStarter.java:817)
[MJSONWP] at com.android.server.am.ActivityManagerService.startActivityAndWait(ActivityManagerService.java:4625)
[MJSONWP] at com.android.server.am.ActivityManagerShellCommand.runStartActivity(ActivityManagerShellCommand.java:412)
[MJSONWP] at com.android.server.am.ActivityManagerShellCommand.onCommand(ActivityManagerShellCommand.java:141)
[MJSONWP] at android.os.ShellCommand.exec(ShellCommand.java:96)
[MJSONWP] at com.android.server.am.ActivityManagerService.onShellCommand(ActivityManagerService.java:15014)
[MJSONWP] at android.os.Binder.shellCommand(Binder.java:594)
[MJSONWP] at android.os.Binder.onTransact(Binder.java:492)
[MJSONWP] at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:4243)
[MJSONWP] at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2919)
[MJSONWP] at android.os.Binder.execTransact(Binder.java:697)’; Code: ‘4294967295’
[MJSONWP] at ADB.callee$0$0$ (C:\Program Files (x86)\Appium\resources\app\node_modules\appium\node_modules\appium-adb\lib\tools\apk-utils.js:134:11)
[MJSONWP] at tryCatch (C:\Program Files (x86)\Appium\resources\app\node_modules\appium\node_modules\babel-runtime\regenerator\runtime.js:67:40)
[MJSONWP] at GeneratorFunctionPrototype.invoke [as _invoke] (C:\Program Files (x86)\Appium\resources\app\node_modules\appium\node_modules\babel-runtime\regenerator\runtime.js:315:22)
[MJSONWP] at GeneratorFunctionPrototype.prototype.(anonymous function) [as throw] (C:\Program Files (x86)\Appium\resources\app\node_modules\appium\node_modules\babel-runtime\regenerator\runtime.js💯21)
[MJSONWP] at GeneratorFunctionPrototype.invoke (C:\Program Files (x86)\Appium\resources\app\node_modules\appium\node_modules\babel-runtime\regenerator\runtime.js:136:37)
[MJSONWP] at
[HTTP] <-- POST /wd/hub/session 500 5206 ms - 2316
[HTTP]
[HTTP] --> DELETE /wd/hub/session
[HTTP] {}
[HTTP] No route found. Setting content type to ‘text/plain’
[HTTP] <-- DELETE /wd/hub/session 404 4 ms - 57
[HTTP]


#2

I used splash activuty instead of main activity.It worked


#3

Hi,

I’m new to mobile application. I got the issue 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: Cannot start the ‘com.fg.bot’ application. Anyone plz assist me. I could not see Android settings in Appium also. so I should use in code.