Hey Alex,
thanks for showing an interest ;-)
I don't have a reference to the dialog. I just use managed dialogs
(showDialog/dimissDialog).
I guess the solution is to make my error reporter ignore this exception.
It's a bit lame though.
Also I have half a dozen different stacktraces that
Before calling Dialog.dismiss() try checking whether it is shown,
isShown();
On May 19, 10:22 pm, Mariano Kamp mariano.k...@gmail.com wrote:
Exactly my original point. That's the reason I originally asked this: I am
wondering how to track down this IAE? It doesn't mention my code
*bump*
Since Cupcake I have a couple of those issues where I don't see my code in
the stack trace.
Should I open bug reports for them ... just with the stacktrace?
In Cupcake do the line numbers from the stack traces match any git tag that
I can use with the git web interface?
On Sat, May 9,
Since Cupcake I have a couple of those issues where I don't see my code in
the stack trace.
That doesn't mean it's not your code at fault. For instance in this
case what are you doing with the dialogs and their parent activities?
--
Romain Guy
Android framework engineer
romain...@android.com
Exactly my original point. That's the reason I originally asked this: I am
wondering how to track down this IAE? It doesn't mention my code
(com.newsrob.*) in the stack trace.
Is there anymore information that I can automatically gather and include
in the bug reports to get a better
I just thought that for some completeness it would be good to add another
bug report.This one is from Android 1.1, this other one was from 1.5.
-- Android Version: sdk=2, release=1.1, inc=128600
-- Memory free: 2.06MB total: 5.88MB max: 16.00MB-- Thread State: RUNNABLE
-- NewsRob Version:
6 matches
Mail list logo
