I have been developing a project in eclipse for an android app. An error which i frequently get is that of- activity class does not exist. But when i just save the manifest file once again the error vanishes and the program runs correctly. Why then do i get the same error again and again. ?
Console error:
[2011-11-18 15:08:38 - link] Starting activity acb.abc.LinkActivity on device emulator-5554
[2011-11-18 15:08:40 - link] ActivityManager: Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=acb.abc/.LinkActivity }
[2011-11-18 15:08:40 - link] New package not yet registered with the system. Waiting 3 seconds before next attempt.
[2011-11-18 15:08:40 - link] ActivityManager: Error: Activity class {acb.abc/acb.abc.LinkActivity} does not exist.
every time a new activity is added in the application, it needs to be added in the manifest file as well with a new tag.
Make sure that u r doing this otherwise the new activity will not be considered.
For reference see This
I got this problem today.
Attention that: "class {acb.abc/acb.abc.LinkActivity}",you should modify the AndroidManifest.xml, change acb.abc.LinkActivity to ".LinkActivity". Then will be OK.
You are not declairing your package name correctly in your manifest, thats what I guess. Either post your manifest or go through this discussion.
http://groups.google.com/group/android-developers/browse_thread/thread/ce62996fde2d4727
Cheers.....!!!!!!
In may case, in Android Studio, I changed AndroidManifest.xml like this: change main Activity on my custom Activity. Then I start my app on emulation device, I get:
"Error type 3 Error: Activity class {...} does not exist.",
and may app failed.
I was forced delete my app on virtual device (use Application Manager in device) and restarted app in Android Studio. This solution helped me.
I saw this error because I had installed my app as a built-in app, then disabled it to removed it. I thought I had removed it when I tried to run my app in eclipse as a "normal" app. I discovered that my app was still in system/app.
Once I removed it, I didn't see this error when running my app in Eclipse.
i had this problem too and it was because i had a second tag in my AndroidManifest.xml
on android studio <= 0.8.6 it was no problem
i'm not sure yet how to handle this if one needs two application's defined here
my use case was related to saving the application state in a separate activity
e.g.
http://blog.tomgibara.com/post/126377651/global-application-state-in-android
Error: Activity class {com.myapplication5.myapplication/com.myapplication5.myapplication.MainActivity} does not exist.
answer:
file-projectstructur-flavors-minsdk version =4
ok
Related
I am developing an Android application with Xamarin.Android.
My application is running perfectly, but when I add GCM Component it gives the following error:
Android application is debugging.
The application could not be started. Ensure that the application has been installed to the target device and has a launchable activity (MainLauncher = true).
Additionally, check Build->Configuration Manager to ensure this project is set to Deploy for this configuration.
If I remove the component then it works fine.
Here is the image for the error:
I have tried many solutions from Google, but nothing has helped.
How can I prevent this error from happening?
You need to make sure that your package name does not start with an uppercase letter - from your screenshot, it looks like it does "RestaurantAPP".
This is a known issue with GCM itself and is not a bug in the Xamarin component: https://code.google.com/p/android/issues/detail?id=37658
Has anyone experienced something like this ? My app works but after I add the line "Parse.enableLocalDatastore(this);" in my Application class it stops. Eclipse tries to launch it but right after the white screen, it turns black and LogCat notifies this warning "05-24 14:15:20.683: W/ActivityManager(382): Launch timeout has expired, giving up wake lock!"
First time I experience such thing, tried searching on Parse.com and nothing.
Additional info:
Android + Google APIs v4.4.2
Parse v1.5.0
Well, it wasn't the SDK's fault.
Solution: Had to create a new AVD to test my app after adding the line "enableLocalDatastore".
^true, same here, I lost ~10h to find out why!!!! seems it is parse.com lib BUG!!!!! when build the android application on release mode!!!!!!!
solution add this :
Parse.enableLocalDatastore(this);
before
Parse.initialize
I am trying to write a sms receiver for android. But I am having issues. I found an example here: http://www.apriorit.com/our-company/dev-blog/227-handle-sms-on-android
Eclipse had underlined the line :
android:text="Update SMS list" />
So I changed it to:
<Button android:layout_height="wrap_content"
android:layout_width="match_parent"
android:layout_margin="2dip"
android:text="#string/UpdateList"
android:id="#+id/UpdateList"/>
and added this into strings.xml :
<string name="UpdateList">Update SMS List</string>
The issue is now with the line :
android:text="#string/UpdateList"
This is the error message:
[2013-03-14 16:37:07 - FindMyPhone] ActivityManager: Warning: Activity not started, its current task has been brought to the front
Does anyone see what the issue is? Or have an idea of how to fix it?
Underline Issue:
I reckon the Linter just hasn't noticed the change yet, I often find that saving the file, closing it and opening it up again, is required to clear it's "cache", if it can be called that, of errors / warnings.
ActivityManager: Warning: Activity not started, its current task has
been brought to the front
This just means that the Activity is open on the device/emulator and you're launching it again. This happens if the code hasn't changed since the last launch, and it brings the current Activity to the front.
[2013-03-14 16:37:07 - FindMyPhone] ActivityManager: Warning: Activity not started, its current task has been brought to the front
This generally indicates that the APK being installed on the device isn't different from what is on there already. Based on your question, the error can be resolved by cleaning and rebuilding the application, then reloading it on to your device.
[2013-03-14 16:37:07 - FindMyPhone] ActivityManager: Warning: Activity not started, its current task has been brought to the front
Your code isn't the problem, it's that the app is currently running on the emulator/device and Eclipse is trying to launch it again. Just hit back until you get to the home screen and try to launch it again.
I have updated my app with change of launcher activity class. User reporting issue about their app icon and shortcut are not working. I want to know is it an OS specific Issue ???
Error they are getting "Linker not available"
Yep, if you have changed the class name for the Activity that used to be an intent launcher, or removed it from being a launcher then peoples current shortcuts won't work.
Simplest answer is to tell them to remove the shortcut and re-add it.
Long solution is to programatically do this yourself (latest Android API's only I believe)
Register the new launcher class in your manifest file.
I created a service application without any GUI...infact take help of other applications available on this website...but when i try to run it on my Emulator (2.3.3), I keep on getting error:
2012-02-13 17:36:56 - RUN_SERVICE] No Launcher activity found!
[2012-02-13 17:36:56 - RUN_SERVICE] The launch will only sync the application package on the device!
After it installs properly, but i dont see my service running...i tried adding toast messages, but I am not receving that as well...i didnt try it on real device yet...as I didnt have any phone with this android version 2.3.3. I am using jre6
As your applicatinon does not have any GUI.
You must start the Service from at least one activivity that may be lanucher acitivity by using
<category android:name="android.intent.category.LAUNCHER>
So that your Service need to start when the app is installed or Run.
Make sure you have defined the activity in your AndroidManifest.xml file....
I think you mentioned this in your manifest <category android:name="android.intent.category.LAUNCHER>. if yes then remove this