Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to type in receive codes #27

Open
duxovni opened this issue Mar 30, 2022 · 7 comments
Open

Unable to type in receive codes #27

duxovni opened this issue Mar 30, 2022 · 7 comments

Comments

@duxovni
Copy link

duxovni commented Mar 30, 2022

All of the text input fields in the app seem to break when I try to input a string matching [0-9]+-[a-z]+. For instance, if i start typing 1-a, the a never appears in the text box, all I can type is 1-. This is obviously especially problematic for the recv code field, but the send text field has the same issue.

I'm using version 1.0.8 on a Pixel 3a running LineageOS 18.1.

@duxovni
Copy link
Author

duxovni commented Mar 30, 2022

(The app isn't completely unusable, I can still paste in recv codes from the clipboard, but I need to type them into a text field on a different app to copy them.)

@psanford
Copy link
Owner

We made a change in 1.0.8 to automatically convert spaces to dashes (-) to make it easier to input codes. I wonder if that is causing an issue for you here. Could you try testing with 1.0.6 to see if that version also has the issue? https://github.com/psanford/wormhole-william-mobile/releases/tag/v1.0.6

@duxovni
Copy link
Author

duxovni commented Mar 30, 2022

Just checked, 1.0.6 works fine. I'm puzzled why fields other than the recv code field would also be affected if the space conversion were the cause of the bug, but it's definitely due to some change between 1.0.6 and 1.0.8 :/

@duxovni
Copy link
Author

duxovni commented Mar 30, 2022

1.0.7 also works for me.

@psanford
Copy link
Owner

That makes it very likely this change is somehow responsible: 07a623f

Not sure why this would behave differently on lineageOS vs stock Android 12. I'll see if if can dig in a bit more when I have some time. Worst case, we can revert that change.

@duxovni
Copy link
Author

duxovni commented Mar 30, 2022

LineageOS 18.1 is based off Android 11 fwiw. Given that text fields other than the recv code field have the same bug, I'm not sure reverting the change to that one field will actually make a difference, but maybe if I have time at some point I'll try and set up a build environment and do some testing of my own. I appreciate you looking into this!

@nogweii
Copy link

nogweii commented May 16, 2023

I get the same behavior on my Pixel 6 Pro (running GrapheneOS, which is based on Android 13).

I tried downgrading to 1.0.7, but that only lead to crashes. 1.0.6 allows me to type in the code easily, and works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants