Activity Manager Error Activity Class Does Not Exist Android
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn
Error Activity Class Does Not Exist Android Studio
more about Stack Overflow the company Business Learn more about hiring developers or activity class does not exist adb posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community
Activity Class Does Not Exist React Native
Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Error type 3 Error: Activity class {} does not activitymanager: error type 3 exist up vote 82 down vote favorite 13 I have an INTELIJ(v12) android project successfully imported to AndroidStudio(v0.4.0). It works perfectly if I don't change anything in manifest. When I want to change the launcher activity and run, it outputs with the following error: Launching application: com.trackingeng/LandingActivity. DEVICE SHELL COMMAND: am start -D -n "com.trackingeng/LandingActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.trackingeng/LandingActivity } Error type error type 3 error activity class does not exist error while launching activity 3 Error: Activity class {com.trackingeng/LandingActivity} does not exist. When I click Sync Project with Gradle files it outputs: Project Sync The project 'TrackingEng' is not a Gradle-based project Anyone has faced this problem? Any ideas? Run settings: java android intellij-idea android-manifest android-studio share|improve this question edited Oct 11 '14 at 11:02 matthias_h 6,91841130 asked Jan 4 '14 at 0:35 Jacob 2,889112546 Where is your original AndroidManifest.xml file? –twlkyao Jan 4 '14 at 3:33 In the same place, under main folder in project. –Jacob Jan 4 '14 at 9:30 I mean is this picture in the post is your original AndroidManifest.xml or not. –twlkyao Jan 4 '14 at 9:42 6 I have found a thread, hope could help. stackoverflow.com/questions/19670607/… –twlkyao Jan 4 '14 at 13:48 1 Though not effective in the OP's case, doing a gradle sync solved Error: Activity class {...} does not exist. for me. –dinosaur May 8 at 3:00 | show 1 more comment 23 Answers 23 active oldest votes up vote 155 down vote accepted I faced a similar problem after refactoring. This is what i did to resolve this issue: Cleaned the Project Deleted the Build directory Restarted Android S
here for a quick overview of the site Help Center Detailed
Delete Build Directory Android Studio
answers to any questions you might have Meta Discuss the new package not yet registered with the system workings and policies of this site About Us Learn more about Stack Overflow the company
When An Activity Does Not Exist In Memory It Is In Which State
Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join http://stackoverflow.com/questions/20915266/error-type-3-error-activity-class-does-not-exist the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Activity class does not exist up vote 18 down vote favorite 1 Aaaargh! I don't know what's going on, but suddenly I http://stackoverflow.com/questions/7071271/activity-class-does-not-exist can't launch my app. I'm using IntelliJ and I keep getting this error. I thought maybe there was a typo somewhere in the manifest, but there doesn't seem to be. Heres' the error: Launching application: com.foo.app/com.foo.app.main. DEVICE SHELL COMMAND: am start -n "com.foo.app/com.foo.app.main" Starting: Intent { cmp=com.foo.app/.main} Error type 3 Error: Activity class {com.foo.app/com.foo.app.main} does not exist. And here's my Manifest:
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow http://stackoverflow.com/questions/20230285/error-activity-class-does-not-exist-when-launching-android-app-with-adb-shell the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up error “activity class does not exist” when launching android app with adb shell am start up vote does not 0 down vote favorite After adb install-ing my app, I can verify that it's there with adb shell pm list packages AppName: package:air.com.client.AppName So I know it's there, but when I try to launch it with adb shell am start -a android.intent.action.MAIN -n air.com.client/.AppName, I get this error: Starting: Intent { cmp=air.com.client/.AppName} Error type 3 Error: Activity class {air.com.client/air.com.client.AppName} does not exist. If it matters, this is, as you may have noticed, does not exist an AIR app that's been packaged as an Android app. Any ideas? Did I miss something somewhere? When I use aapt dump xmltree I can see that my .apk includes an android.intent.action.MAIN entry in the intent-filter node, for what it's worth. And finally, for sanity's sake, using the same command template I can launch the settings app with no problems: adb shell am start -a android.intent.action.MAIN -n com.android.settings/.Settings android air adb share|improve this question edited Nov 27 '13 at 0:36 asked Nov 26 '13 at 23:39 matt lohkamp 1,29712139 1 There is no air.com.client class. The class name is air.com.client.AppName. –Alex P. Nov 26 '13 at 23:49 you're gonna have to spell it out for me - what should the command be? –matt lohkamp Nov 26 '13 at 23:51 related q stackoverflow.com/questions/28388523/… –barlop Feb 10 '15 at 6:25 add a comment| 3 Answers 3 active oldest votes up vote 1 down vote accepted Managed to figure it out - I left a prompt open with adb logcat, then launched my app on the device - out of this corresponding log entry: I/ActivityManager( 2115): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=air.com.client.AppName/.AppEntry} from pid 2453 I put together a new command line: adb shell start -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -n air.com.client.AppName/.