AlertDialog broken in XE12

[GoogleCodeExporter]

Starting in XE12, any AlertDialog that should contain a list results in an 
empty window. In particular, a ListPreference in a PreferenceActivity has no 
list, and you can't select anything; and the intent-disambiguation dialog that 
pops up when an intent is triggered that more than one application can handle, 
is similarly blank.

Original issue reported on code.google.com by jimrandomh@gmail.com on 28 Dec 2013 at 1:17

[GoogleCodeExporter]

Original comment by ala...@google.com on 6 Jan 2014 at 5:44

• Changed state: Accepted
• Added labels: Component-GDK, log-12414441

[GoogleCodeExporter]

This is still broken in XE16, but the behavior is different than described 
above.  

When using the below code:

--------
final CharSequence[] items = new CharSequence[4]);

...
// populate list
...

AlertDialog.Builder builder = new AlertDialog.Builder(mContext);
builder.setTitle("My Title");
builder.setCancelable(false);
builder.setItems(items, new DialogInterface.OnClickListener() {
    public void onClick(DialogInterface dialog, int item) {
        //Do something
    }
});

AlertDialog alert = builder.create();
alert.show();
--------

...I see the view in the attached screenshot from Glass.  

I can see the populated list, but the selection indicator is frozen on the 
first item in the list.  I can select the first item and the OnClickListener() 
correctly fires, but I can't scroll to select anything else.

I also get the error message:

04-18 10:55:29.139    2860-2860/com.joulespersecond.seattlebusbot 
E/WindowManager﹕ android.view.WindowLeaked: Activity 
com.joulespersecond.seattlebusbot.GlassArrivalsListActivity has leaked window 
com.android.internal.policy.impl.PhoneWindow$DecorView{213e032c V.E..... 
R....... 0,0-640,360} that was originally added here
            at android.view.ViewRootImpl.<init>(ViewRootImpl.java:348)
            at android.view.WindowManagerGlobal.addView(WindowManagerGlobal.java:248)
            at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:69)
            at android.app.Dialog.show(Dialog.java:286)
            at com.joulespersecond.oba.region.ObaRegionsTask.haveUserChooseRegion(ObaRegionsTask.java:215)
            at com.joulespersecond.oba.region.ObaRegionsTask.onPostExecute(ObaRegionsTask.java:154)
            at com.joulespersecond.oba.region.ObaRegionsTask.onPostExecute(ObaRegionsTask.java:47)
            at android.os.AsyncTask.finish(AsyncTask.java:670)
            at android.os.AsyncTask.access$600(AsyncTask.java:177)
            at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:683)
            at android.os.Handler.dispatchMessage(Handler.java:102)
            at android.os.Looper.loop(Looper.java:149)
            at android.app.ActivityThread.main(ActivityThread.java:5061)
            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:794)
            at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:610)
            at dalvik.system.NativeStart.main(Native Method)

Glass has occasionally freaked out from this view as well (seems when I try to 
scroll to other results), and  has flashed back and gotten stuck at the "ok 
glass, find my bus" screen, or gone dark and completely frozen up.

Original comment by sjbarb...@gmail.com on 18 Apr 2014 at 3:15

Attachments:

• AlertDialogGlass1.png

[GoogleCodeExporter]

Same behavior described in #2 above still occurs on XE16.1.

Original comment by sjbarb...@gmail.com on 22 Apr 2014 at 5:44

[GoogleCodeExporter]

This is not actually the same bug. The previous bug was specific to dialogs. 
The new bug is that the forward/next gestures don't fall through and generate 
key events if unhandled, which breaks all lists (regardless of whether they're 
dialogs).

(It has now been five months since I had a build of Glass that could run 
ConnectBot. This is my primary use case for Glass. Reflashing to XE11 does not 
work because the auto-updater is extremely aggressive, and cannot be turned 
off. I am pissed about this.)

Original comment by jimrandomh@gmail.com on 22 Apr 2014 at 5:52

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

This has also blocked my ability to develop on glass for months now. Please 
escalate so we may resume development. When using a BT keyboard to navigate 
this prompt in XE 16.1 I get a home crash on input.

Original comment by mrub...@umich.edu on 22 Apr 2014 at 5:56

[GoogleCodeExporter]

I'd also like to point out that this is probably not the only blocking issue 
for developers on XE16. Launcher2 crashes on start due to an unrelated issue, 
which means it's impossible (without some hackery that I haven't done) to get 
into the legacy Android settings. Bluetooth keyboard pairing can't be tested, 
due to this bug, but given the amount changed there's a high probability it's 
broken, too.

Please escalate.

Original comment by jimrandomh@gmail.com on 22 Apr 2014 at 6:01

[GoogleCodeExporter]

Agreed, I've filed a separate bug report specific to the scrolling issues on 
ListViews in general here:
https://code.google.com/p/google-glass-api/issues/detail?id=484

At the time of my #2 comment I thought the issue was specific to AlertDialogs, 
but its not.

Original comment by sjbarb...@gmail.com on 22 Apr 2014 at 6:28

[GoogleCodeExporter]

Related  issue 484  has been inappropriately closed WontFix:
https://code.google.com/p/google-glass-api/issues/detail?id=484

Original comment by p...@swooby.com on 24 Apr 2014 at 8:30