Instead of the "console", look at the system log (either using "adb
logcat" or with the ddms perspective in eclipse), and it will tell you
exactly where and why it crashed.
Im also having the same issue here. What are the probable causes of
this runtime error...any clue? It is a very common error we see on
emulators and android powered devices.
On Oct 12, 1:13 pm, Marco Nelissen <marc...@android.com> wrote:
> Instead of the "console", look at the system log (either using "adb
> logcat" or with the ddms perspective in eclipse), and it will tell you
> exactly where and why it crashed.
> On Mon, Oct 12, 2009 at 5:33 AM, Sunny <atulpmaha...@gmail.com> wrote:
> > Hi ,
> > I am testing basic AndroidPhoneDialer application on emulator my
> > console showing following result
Maxood wrote:
> Im also having the same issue here. What are the probable causes of
> this runtime error...any clue? It is a very common error we see on
> emulators and android powered devices.
Step #1: Use adb logcat, DDMS, or the DDMS perspective in Eclipse to
find the Java stack trace of the exception
Step #2: Fix the root cause of the exception
Step #3: There is no step #3
In other words, "this runtime error" is insufficient data for anyone to
provide assistance.
I have spotted where i was wrong and there was insufficient
data...right! My app is running just fine on the emulator.
Now i need to deploy my app on the device and need to know whether i
have to deploy/install the SQLite db file along with my app. Please
note that i haven't got any database file in my res/raw folder in
eclipse. Do i have to copy the database file and place it in my res/
raw folder and then deploy it on the device?
Because without the database file when i deploy my tried and tested
app on the device i get the same error: "The application
com.myapps.xxxx has stopped unexpectedly"
Please guide, thanks.
On Nov 6, 8:06 am, Mark Murphy <mmur...@commonsware.com> wrote:
> Maxood wrote:
> > Im also having the same issue here. What are the probable causes of
> > this runtime error...any clue? It is a very common error we see on
> > emulators and android powered devices.
> Step #1: Use adb logcat, DDMS, or the DDMS perspective in Eclipse to
> find the Java stack trace of the exception
> Step #2: Fix the root cause of the exception
> Step #3: There is no step #3
> In other words, "this runtime error" is insufficient data for anyone to
> provide assistance.
Maxood wrote:
> I have spotted where i was wrong and there was insufficient
> data...right! My app is running just fine on the emulator.
> Now i need to deploy my app on the device and need to know whether i
> have to deploy/install the SQLite db file along with my app.
From the standpoint of databases, devices and emulators are identical.
If it works on a clean emulator, it will work on a clean device. So,
create yourself a fresh AVD, install your app, and see what happens.
> Because without the database file when i deploy my tried and tested
> app on the device i get the same error: "The application
> com.myapps.xxxx has stopped unexpectedly"
Here it my advice again, updated:
Step #1: Use adb logcat, DDMS, or the DDMS perspective in Eclipse to
find the Java stack trace of the exception
Step #2: Fix the root cause of the exception
Step #3: There is no step #3
In other words, "The application com.myapps.xxxx has stopped
unexpectedly" is insufficient data for anyone to provide assistance.
When i create a new AVD, as i am developing on Android 1.6 so i
selected API level 4 for Target. Now for the SD Card, do i have to
provide the file size or should i browse the file location and provide
the path in the second option? And what about Skin and Hardware?
Should i leave them as they are and carry on with default values?
On Nov 8, 10:38 am, Mark Murphy <mmur...@commonsware.com> wrote:
> Maxood wrote:
> > I have spotted where i was wrong and there was insufficient
> > data...right! My app is running just fine on the emulator.
> > Now i need to deploy my app on the device and need to know whether i
> > have to deploy/install the SQLite db file along with my app.
> From the standpoint of databases, devices and emulators are identical.
> If it works on a clean emulator, it will work on a clean device. So,
> create yourself a fresh AVD, install your app, and see what happens.
> > Because without the database file when i deploy my tried and tested
> > app on the device i get the same error: "The application
> > com.myapps.xxxx has stopped unexpectedly"
> Here it my advice again, updated:
> Step #1: Use adb logcat, DDMS, or the DDMS perspective in Eclipse to
> find the Java stack trace of the exception
> Step #2: Fix the root cause of the exception
> Step #3: There is no step #3
> In other words, "The application com.myapps.xxxx has stopped
> unexpectedly" is insufficient data for anyone to provide assistance.
Maxood wrote:
> Now for the SD Card, do i have to
> provide the file size or should i browse the file location and provide
> the path in the second option?
That is up to you. Unless you have an existing SD card image to work
with, the former option is probably simplest.
> And what about Skin and Hardware?
> Should i leave them as they are and carry on with default values?
That is up to you. You probably should be creating several AVDs to test
on different screen sizes.
I created a new AVD. On emulator when the touch event is fired i get
the same error: "The application android has stopped unexpectedly". In
my logcat window i have the following error messages:
11-10 01:43:24.144: DEBUG/dalvikvm(743): GC freed 987 objects / 79024
bytes in 99ms
11-10 01:43:24.324: DEBUG/AndroidRuntime(743): Shutting down VM
11-10 01:43:24.334: WARN/dalvikvm(743): threadid=3: thread exiting
with uncaught exception (group=0x4001aa28)
11-10 01:43:24.334: ERROR/AndroidRuntime(743): Uncaught handler:
thread main exiting due to uncaught exception
11-10 01:43:24.343: ERROR/AndroidRuntime(743):
android.database.CursorIndexOutOfBoundsException: Index 0 requested,
with a size of 0
11-10 01:43:24.343: ERROR/AndroidRuntime(743): at
android.database.AbstractCursor.checkPosition(AbstractCursor.java:580)
11-10 01:43:24.343: ERROR/AndroidRuntime(743): at
android.database.AbstractWindowedCursor.checkPosition
(AbstractWindowedCursor.java:172)
11-10 01:43:24.343: ERROR/AndroidRuntime(743): at
android.database.AbstractWindowedCursor.getString
(AbstractWindowedCursor.java:41)
11-10 01:43:24.343: ERROR/AndroidRuntime(743): at
com.myapps.facts.Facts.onTouchEvent(Facts.java:237)
11-10 01:43:24.343: ERROR/AndroidRuntime(743): at
android.app.Activity.dispatchTouchEvent(Activity.java:1990)
11-10 01:43:24.343: ERROR/AndroidRuntime(743): at
com.android.internal.policy.impl.PhoneWindow
$DecorView.dispatchTouchEvent(PhoneWindow.java:1696)
11-10 01:43:24.343: ERROR/AndroidRuntime(743): at
android.view.ViewRoot.handleMessage(ViewRoot.java:1658)
11-10 01:43:24.343: ERROR/AndroidRuntime(743): at
android.os.Handler.dispatchMessage(Handler.java:99)
11-10 01:43:24.343: ERROR/AndroidRuntime(743): at
android.os.Looper.loop(Looper.java:123)
11-10 01:43:24.343: ERROR/AndroidRuntime(743): at
android.app.ActivityThread.main(ActivityThread.java:4203)
11-10 01:43:24.343: ERROR/AndroidRuntime(743): at
java.lang.reflect.Method.invokeNative(Native Method)
11-10 01:43:24.343: ERROR/AndroidRuntime(743): at
java.lang.reflect.Method.invoke(Method.java:521)
11-10 01:43:24.343: ERROR/AndroidRuntime(743): at
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run
(ZygoteInit.java:791)
11-10 01:43:24.343: ERROR/AndroidRuntime(743): at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:549)
11-10 01:43:24.343: ERROR/AndroidRuntime(743): at
dalvik.system.NativeStart.main(Native Method)
Where am i wrong? Is there something wrong with the Cursor position?
How to resolve the issue? Please guide.Thanks
On Nov 8, 12:20 pm, Mark Murphy <mmur...@commonsware.com> wrote:
> Maxood wrote:
> > Now for the SD Card, do i have to
> > provide the file size or should i browse the file location and provide
> > the path in the second option?
> That is up to you. Unless you have an existing SD card image to work
> with, the former option is probably simplest.
> > And what about Skin and Hardware?
> > Should i leave them as they are and carry on with default values?
> That is up to you. You probably should be creating several AVDs to test
> on different screen sizes.
> Maxood wrote:
> > Now for the SD Card, do i have to
> > provide the file size or should i browse the file location and provide
> > the path in the second option?
> That is up to you. Unless you have an existing SD card image to work
> with, the former option is probably simplest.
> > And what about Skin and Hardware?
> > Should i leave them as they are and carry on with default values?
> That is up to you. You probably should be creating several AVDs to test
> on different screen sizes.
Maxood wrote:
> I created a new AVD. On emulator when the touch event is fired i get
> the same error: "The application android has stopped unexpectedly". In
> my logcat window i have the following error messages:
> 11-10 01:43:24.144: DEBUG/dalvikvm(743): GC freed 987 objects / 79024
> bytes in 99ms
> 11-10 01:43:24.324: DEBUG/AndroidRuntime(743): Shutting down VM
> 11-10 01:43:24.334: WARN/dalvikvm(743): threadid=3: thread exiting
> with uncaught exception (group=0x4001aa28)
> 11-10 01:43:24.334: ERROR/AndroidRuntime(743): Uncaught handler:
> thread main exiting due to uncaught exception
> 11-10 01:43:24.343: ERROR/AndroidRuntime(743):
> android.database.CursorIndexOutOfBoundsException: Index 0 requested,
> with a size of 0
You appear to be handing something an empty cursor, or the cursor is
becoming empty unexpectedly.
|
