Inconsistent case-insensitive functions [232290071]

Assigned

Bug

Status Update

No update yet.

Description

ch...@gmail.com

created issue #1

May 11, 2022 10:18PM

Component used: DocumentFile

Devices/Android versions reproduced on: Pixel 6 (32)

Repository that hosts code in question: https://github.com/chaneylc/DocumentTreeCaseSensitiveTest

In the source (DocumentProvider) I noticed that it is recommended to handle DISPLAY_NAME queries as case insensitive. From my example you can see that there are inconsistencies when dealing with DISPLAY_NAME for file names in a DocumentFile/Tree.

       //give access to a document tree uri
        val doc = DocumentFile.fromTreeUri(this, uri)

        //create first file "Test" <-- note title case
        doc?.createFile("*/*", "Test")

        //attempt to find lowercase "test" instead
        val name = "test"
        val child = doc?.findFile(name)

        //this is null, as it should be, intuitively...
        //even though DocumentProvider recommends using case-insensitive for DISPLAY_NAME queries
        Log.d("Test", "${child?.exists()}")

        //now create "test"
        doc?.createFile("*/*", "test")

        //this also returns null! very unintuitive
        val child2 = doc?.findFile("test")
        Log.d("Test", "${child2?.exists()}")

        //the second createFile seems to have a case-insensitive check to find duplicate names,
        //this leads to the creation of "test (1)"

Comments

ma...@google.com <ma...@google.com> #2May 12, 2022 08:47AM

Reassigned to ze...@google.com.

We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

ch...@gmail.com <ch...@gmail.com> #3May 12, 2022 01:36PM

Sadly, I can't enter any character I wish, such as of other languages. I think it supports only ascii...

adb is fine:

~$ adb shell echo '1박 2일'
1박 2일
~$ adb shell echo '1박 2일'| xxd
00000000: 31eb b095 2032 ec9d bc0a                 1... 2....
~$

but it does look like the 'input' command might have issues:

~$ adb shell input keyboard text '1박 2일'

Exception occurred while executing 'keyboard':
java.lang.NullPointerException: Attempt to get length of null array
	at com.android.server.input.InputShellCommand.sendText(InputShellCommand.java:318)
	at com.android.server.input.InputShellCommand.runText(InputShellCommand.java:290)
	at com.android.server.input.InputShellCommand.onCommand(InputShellCommand.java:231)
	at com.android.modules.utils.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:97)
	at android.os.ShellCommand.exec(ShellCommand.java:38)
	at com.android.server.input.InputManagerService.onShellCommand(InputManagerService.java:3432)
	at android.os.Binder.shellCommand(Binder.java:968)
	at android.os.Binder.onTransact(Binder.java:849)
	at android.hardware.input.IInputManager$Stub.onTransact(IInputManager.java:981)
	at android.os.Binder.execTransactInternal(Binder.java:1205)
	at android.os.Binder.execTransact(Binder.java:1163)
~$

what's the code?

        final char[] chars = buff.toString().toCharArray();
        final KeyCharacterMap kcm = KeyCharacterMap.load(KeyCharacterMap.VIRTUAL_KEYBOARD);
        final KeyEvent[] events = kcm.getEvents(chars);
        for (int i = 0; i < events.length; i++) {
            KeyEvent e = events[i];
            if (source != e.getSource()) {
                e.setSource(source);
            }
            e.setDisplayId(displayId);
            injectKeyEvent(e);
        }

okay, so maybe you have to have the right virtual keyboard in use?

nope ... changing to the korean keyboard doesn't fix my korean example above.

over to lzye who seems to have touched this last, and might know whether this is a bug/regression/unfortunate unfixable limitation.

ze...@google.com <ze...@google.com> Jul 27, 2022 03:45PM

Reassigned to an...@google.com.

sa...@google.com <sa...@google.com> #4Jan 8, 2024 06:03AM

Reassigned to al...@google.com.

If anyone knows about AccessibilityService, please answer me about this possible workaround of this matter, to dispatch unicode keys through it:

https://stackoverflow.com/q/70160582/878126

sh...@google.com <sh...@google.com> Jan 8, 2024 11:58AM

Reassigned to sh...@google.com.

sh...@google.com <sh...@google.com> Jan 9, 2025 09:16PM