Most of the time , when i start the emulator, i see only the Home-
Screen, and my app is in the application list either. But a few times
it works fine.
the console says: "ActivityManager: Error: Activity class
{njust.dorm.pack1/njust.dorm.pack1.pro1} does not exist."
> Most of the time , when i start the emulator, i see only the Home-
> Screen, and my app is in the application list either. But a few times
> it works fine.
> the console says: "ActivityManager: Error: Activity class
> {njust.dorm.pack1/njust.dorm.pack1.pro1} does not exist."
Perhaps you did rename your "MainClass-File".java somewhen?
Did you check whether the AndroidManifest.xml
contains the correct Package
"... package="org.anddev.android.Hello_Android">"
AND the correct "Entry-Point":
"<activity class=".Hello_Android""
?
Regards, plusminus
http://anddev.org | Android Development Community / Tutorials
On Nov 16, 4:59 pm, JamesWang <sesame84.stud...@sina.com> wrote:
> Most of the time , when i start the emulator, i see only the Home-
> Screen, and my app is in the application list either. But a few times
> it works fine.
> the console says: "ActivityManager: Error: Activity class
> {njust.dorm.pack1/njust.dorm.pack1.pro1} does not exist."
> Perhaps you did rename your "MainClass-File".java somewhen?
> Did you check whether the AndroidManifest.xml
> contains the correct Package
> "... package="org.anddev.android.Hello_Android">"
> AND the correct "Entry-Point":
> "<activity class=".Hello_Android""
> ?
> Regards, plusminushttp://anddev.org | Android Development Community / Tutorials
> On Nov 16, 4:59 pm, JamesWang <sesame84.stud...@sina.com> wrote:
> > Most of the time , when i start the emulator, i see only the Home-
> > Screen, and my app is in the application list either. But a few times
> > it works fine.
> > the console says: "ActivityManager: Error: Activity class
> > {njust.dorm.pack1/njust.dorm.pack1.pro1} does not exist."
I saw this error today, but didn't need to recreate my project to fix
it.
I had added a provider to my AndroidManifest.xml that had an invalid
class attribute. This wasn't picked up at compile time in Eclipse
(like a mistyped activity is) so resulted in this error appearing on
the console.
FYI, I'd used:
<provider class="provider.FooProvider"
android:authorities="org.foo.provider.Foo" />
instead of: (note the . at the start of the class attribute value)
<provider class=".provider.FooProvider"
android:authorities="org.foo.provider.Foo" />
It's worth looking at the emulator log when weird stuff like this
happens. It's often very useful. Add ANDROID_HOME/tools to your path
and try:
adb logcat
In this case the following error shows me what went wrong:
W/PackageParser( 465): /data/app/Foo.apk (at Binary XML file line
#7): Using absolute class name provider.FooProvider in package
org.foo; not supported yet!
Cheers,
Andy Bryant
On Dec 6 2007, 6:17 pm, ZA_Alligator <alasdair.mcc...@gmail.com>
wrote:
> Basically he says you are doomed, and must simply copy and paste your
> code into a new project.
> Good luck, I hope someone solves this problem.
> Regards, Al.
> On Nov 16, 6:59 pm, plusminus <stoeps...@gmx.de> wrote:
> > Perhaps you did rename your "MainClass-File".java somewhen?
> > Did you check whether the AndroidManifest.xml
> > contains the correct Package
> > "... package="org.anddev.android.Hello_Android">"
> > AND the correct "Entry-Point":
> > "<activity class=".Hello_Android""
> > ?
> > Regards, plusminushttp://anddev.org| Android Development Community / Tutorials
> > On Nov 16, 4:59 pm, JamesWang <sesame84.stud...@sina.com> wrote:
> > > Most of the time , when i start the emulator, i see only the Home-
> > > Screen, and my app is in the application list either. But a few times
> > > it works fine.
> > > the console says: "ActivityManager: Error: Activity class
> > > {njust.dorm.pack1/njust.dorm.pack1.pro1} does not exist."
When I have the "class does not exist" problem, I just remove the app
from the emulator and kill all running. After an app-restart all
should be fine.
To remove your app type in a command window: "adb shell" -> "cd data/
app" -> "rm Your_app.apk" -> "exit" (while emulator is running) and
kill after this with: "adb kill-server".
On Jan 6, 7:43 pm, Andy Bryant <andybry...@gmail.com> wrote:
> I saw this error today, but didn't need to recreate my project to fix
> it.
> I had added a provider to my AndroidManifest.xml that had an invalid
> class attribute. This wasn't picked up at compile time in Eclipse
> (like a mistyped activity is) so resulted in this error appearing on
> the console.
> FYI, I'd used:
> <provider class="provider.FooProvider"
> android:authorities="org.foo.provider.Foo" />
> instead of: (note the . at the start of the class attribute value)
> <provider class=".provider.FooProvider"
> android:authorities="org.foo.provider.Foo" />
> It's worth looking at the emulator log when weird stuff like this
> happens. It's often very useful. Add ANDROID_HOME/tools to your path
> and try:
> adb logcat
> In this case the following error shows me what went wrong:
> W/PackageParser( 465): /data/app/Foo.apk (at Binary XML file line
> #7): Using absolute class name provider.FooProvider in package
> org.foo; not supported yet!
> Cheers,
> Andy Bryant
> On Dec 6 2007, 6:17 pm, ZA_Alligator <alasdair.mcc...@gmail.com>
> wrote:
> > Basically he says you are doomed, and must simply copy and paste your
> > code into a new project.
> > Good luck, I hope someone solves this problem.
> > Regards, Al.
> > On Nov 16, 6:59 pm, plusminus <stoeps...@gmx.de> wrote:
> > > Perhaps you did rename your "MainClass-File".java somewhen?
> > > Did you check whether the AndroidManifest.xml
> > > contains the correct Package
> > > "... package="org.anddev.android.Hello_Android">"
> > > AND the correct "Entry-Point":
> > > "<activity class=".Hello_Android""
> > > ?
> > > Regards, plusminushttp://anddev.org| Android Development Community / Tutorials
> > > On Nov 16, 4:59 pm, JamesWang <sesame84.stud...@sina.com> wrote:
> > > > Most of the time , when i start the emulator, i see only the Home-
> > > > Screen, and my app is in the application list either. But a few times
> > > > it works fine.
> > > > the console says: "ActivityManager: Error: Activity class
> > > > {njust.dorm.pack1/njust.dorm.pack1.pro1} does not exist."