-
Notifications
You must be signed in to change notification settings - Fork 18
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
Comments
(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.) |
We made a change in 1.0.8 to automatically convert spaces to dashes ( |
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 :/ |
1.0.7 also works for me. |
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. |
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! |
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. |
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 typing1-a
, thea
never appears in the text box, all I can type is1-
. 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.
The text was updated successfully, but these errors were encountered: