-
Notifications
You must be signed in to change notification settings - Fork 527
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
[BUG]: java.lang.IllegalStateException - focus search returned a view that wasn't able to take focus! #5448
Comments
This is caused by ImeOptions. We don't have many screens that implement that, but the focus should be on the ones that set IME_ACTION_NEXT(pin creation) because they likely try to automove to next edittext, while the softkeyboard is still showing. |
@elin4046, thanks for looking into this. Some reasons why a view may not be focussable are:
Given that you have already investigated the first 3, and I tried looking a bit into Focus Order Issues, it maybe one of the other two. But those are situational and would be really difficult to reproduce, e.g if a device is low on storage or memory, then the app might slow down/freeze. This indicates that this issue would rarely occur, and we can put off trying to fix it for now. If however, we receive more crash reports, then we can investigate further. Would you like to select another issue, or would you like me to assign you something else? |
Hi @adhiamboperes, thanks for the info, makes sense to depriortize this effort then. You can assign this issue to me, #4312, and I'll take a stab at it |
Hi @adhiamboperes, I have tried but I wasn't able to reproduce the error. In a ConstraintLayout, the arrangement and constraints of views can sometimes result in unexpected focus behavior. By using android:nextFocusForward="@+id/next_view_id", pressing the "Next" button on the soft keyboard moves the focus to the view specified by @+id/next_view_id. However, in the pin_password_activity, there is no need to use the actionNext because there are no other views to focus on next. Instead, we can use actionDone. If this solution makes sense, you could assign it to me. Thank you! |
Describe the bug
We are seeing this crash in Crashlytics after the release of 0.13-beta.
This issue has 1 crash event affecting 1 user in the span of 1 day.
Full stacktrace
Steps To Reproduce
Not sure; this happened in production.
Expected Behavior
The crash should not happen.
Screenshots/Videos
No response
What device/emulator are you using?
Samsung Galaxy A13
Which Android version is your device/emulator running?
Android 14
Which version of the Oppia Android app are you using?
0.13-beta-dcde7b359e
Additional Context
No response
The text was updated successfully, but these errors were encountered: