I'm having the same issue in my app. We're having continuous reports on this error. We have a dialog with a WebView inside it.
Hope someone can help :) Thanks! Luis. On 28 jul, 04:32, GJTorikian <[email protected]> wrote: > Bump (do bumps exist in email?) to see if there's anyone out there who > knows what is going on. I read on an online forum that users hitting > the back button on the WebView was causing a crash, but this does not > seem to be the case for me. > > On Jul 20, 8:33 pm, GJTorikian <[email protected]> wrote: > > > > > Ok—good to know I'm not the only one. > > > For what it's worth I just let the screen on my phone dim, then turn > > off. I did not get a crash, however. Very weird. > > > On Jul 14, 8:17 am, Open <[email protected]> wrote: > > > > I've started seeing reports like this too. The screen dimming is the > > > only thing I can think of too, but the stack trace just isn't very > > > much in terms of debugging information. > > > > On Jun 29, 7:13 am,GJTorikian<[email protected]> wrote: > > > > > Howdy— > > > > > I'm getting crash reports from my app out in the wild. Problem is, I > > > > don't know what's causing it. The only place I'm using WebKit is when > > > > constructing an -in-app help browser. Here's the full stack trace: > > > > > java.lang.NullPointerException > > > > at > > > > android.webkit.WebView.onWindowFocusChanged(WebView.java:4177) > > > > at android.view.View.dispatchWindowFocusChanged(View.java:3788) > > > > at > > > > android.view.ViewGroup.dispatchWindowFocusChanged(ViewGroup.java: > > > > 658) > > > > at > > > > android.view.ViewGroup.dispatchWindowFocusChanged(ViewGroup.java: > > > > 662) > > > > at > > > > android.view.ViewGroup.dispatchWindowFocusChanged(ViewGroup.java: > > > > 662) > > > > at > > > > android.view.ViewGroup.dispatchWindowFocusChanged(ViewGroup.java: > > > > 662) > > > > at > > > > android.view.ViewGroup.dispatchWindowFocusChanged(ViewGroup.java: > > > > 662) > > > > at android.view.ViewRoot.handleMessage(ViewRoot.java:1921) > > > > at android.os.Handler.dispatchMessage(Handler.java:99) > > > > at android.os.Looper.loop(Looper.java:123) > > > > at android.app.ActivityThread.main(ActivityThread.java:4627) > > > > 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:868) > > > > at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626) > > > > at dalvik.system.NativeStart.main(Native Method) > > > > > The help browser window takes the full screen, with a bar at the > > > > bottom for "help" and "done" buttons. The only way I can conceive of > > > > the help window losing focus is if someone clicks outside of the bar, > > > > or the screen dims. Will catching and throwing the NPE be sufficient > > > > for eliminating this error, or do I need to add some further metadata > > > > in the Android Manifest XML? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
