[android-developers] Re: How to track down: java.lang.IllegalArgumentException: View not attached to window manager
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 show errors where my app's code is not part of the stacktrace. And it's really hard to debug that as I have the feeling that also for Cupcake I can't be sure from what sources the release is built and the line numbers in the stacktrace aren't that helpful then. It doesn't help that some of the stacktraces just show up on Cupcake builds ;-( Cheers, Mariano On Wed, May 20, 2009 at 7:35 PM, Alexey Krasnoriadtsev < ale...@agilefusion.com> wrote: > > Before calling Dialog.dismiss() try checking whether it is shown, > isShown(); > > > On May 19, 10:22 pm, Mariano Kamp 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 > > (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 understanding why this happens?" > > > > I just have the stack traces and wonder how to go from there. > > > > Mariano > > > > On Wed, May 20, 2009 at 7:10 AM, Romain Guy > wrote: > > > > > > 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 > > > > > Note: please don't send private questions to me, as I don't have time > > > to provide private support. All such questions should be posted on > > > public forums, where I and others can see and answer them > > > > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: How to track down: java.lang.IllegalArgumentException: View not attached to window manager
Before calling Dialog.dismiss() try checking whether it is shown, isShown(); On May 19, 10:22 pm, Mariano Kamp 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 > (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 understanding why this happens?" > > I just have the stack traces and wonder how to go from there. > > Mariano > > On Wed, May 20, 2009 at 7:10 AM, Romain Guy wrote: > > > > 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 > > > Note: please don't send private questions to me, as I don't have time > > to provide private support. All such questions should be posted on > > public forums, where I and others can see and answer them > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: How to track down: java.lang.IllegalArgumentException: View not attached to window manager
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 understanding why this happens?" I just have the stack traces and wonder how to go from there. Mariano On Wed, May 20, 2009 at 7:10 AM, Romain Guy wrote: > > > 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 > > Note: please don't send private questions to me, as I don't have time > to provide private support. All such questions should be posted on > public forums, where I and others can see and answer them > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: How to track down: java.lang.IllegalArgumentException: View not attached to window manager
> 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 Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: How to track down: java.lang.IllegalArgumentException: View not attached to window manager
*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, 2009 at 2:36 PM, Mariano Kamp wrote: > Hi, > > 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 understanding why this happens? > > Cheers, > Mariano > > -- Android Version: sdk=3, release=1.5, inc=146733 > -- Memory free: 0.67MB total: 3.44MB max: 16.00MB-- Thread State: RUNNABLE > -- NewsRob Version: 2.1.2/212 > -- Job: Mark All As Read > -- Stacktrace: > java.lang.IllegalArgumentException: View not attached to window manager > at > android.view.WindowManagerImpl.findViewLocked(WindowManagerImpl.java:356) > at android.view.WindowManagerImpl.removeView(WindowManagerImpl.java:201) > at android.view.Window$LocalWindowManager.removeView(Window.java:400) > at android.app.Dialog.dismissDialog(Dialog.java:268) > at android.app.Dialog.access$000(Dialog.java:69) > at android.app.Dialog$1.run(Dialog.java:103) > at android.os.Handler.handleCallback(Handler.java:587) > at android.os.Handler.dispatchMessage(Handler.java:92) > at android.os.Looper.loop(Looper.java:123) > at android.app.ActivityThread.main(ActivityThread.java:3948) > at java.lang.reflect.Method.invokeNative(Native Method) > at java.lang.reflect.Method.invoke(Method.java:521) > at > com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:782) > at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:540) > at dalvik.system.NativeStart.main(Native Method) > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: How to track down: java.lang.IllegalArgumentException: View not attached to window manager
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: 2.1.2/212 -- Stacktrace: java.lang.IllegalArgumentException: View not attached to window manager at android.view.WindowManagerImpl.findViewLocked(WindowManagerImpl.java:331) at android.view.WindowManagerImpl.removeView(WindowManagerImpl.java:200) at android.view.Window$LocalWindowManager.removeView(Window.java:401) at android.app.Dialog.dismissDialog(Dialog.java:249) at android.app.Dialog.access$000(Dialog.java:59) at android.app.Dialog$1.run(Dialog.java:93) at android.os.Handler.handleCallback(Handler.java:542) at android.os.Handler.dispatchMessage(Handler.java:86) at android.os.Looper.loop(Looper.java:123) at android.app.ActivityThread.main(ActivityThread.java:3739) at java.lang.reflect.Method.invokeNative(Native Method) at java.lang.reflect.Method.invoke(Method.java:515) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:739) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:497) at dalvik.system.NativeStart.main(Native Method) On Sat, May 9, 2009 at 2:36 PM, Mariano Kamp wrote: > Hi, > > 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 understanding why this happens? > > Cheers, > Mariano > > -- Android Version: sdk=3, release=1.5, inc=146733 > -- Memory free: 0.67MB total: 3.44MB max: 16.00MB-- Thread State: RUNNABLE > -- NewsRob Version: 2.1.2/212 > -- Job: Mark All As Read > -- Stacktrace: > java.lang.IllegalArgumentException: View not attached to window manager > at > android.view.WindowManagerImpl.findViewLocked(WindowManagerImpl.java:356) > at android.view.WindowManagerImpl.removeView(WindowManagerImpl.java:201) > at android.view.Window$LocalWindowManager.removeView(Window.java:400) > at android.app.Dialog.dismissDialog(Dialog.java:268) > at android.app.Dialog.access$000(Dialog.java:69) > at android.app.Dialog$1.run(Dialog.java:103) > at android.os.Handler.handleCallback(Handler.java:587) > at android.os.Handler.dispatchMessage(Handler.java:92) > at android.os.Looper.loop(Looper.java:123) > at android.app.ActivityThread.main(ActivityThread.java:3948) > at java.lang.reflect.Method.invokeNative(Native Method) > at java.lang.reflect.Method.invoke(Method.java:521) > at > com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:782) > at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:540) > at dalvik.system.NativeStart.main(Native Method) > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
