Closed v-rodionov closed 4 years ago
Hi! Thank you for reaching out.
As per the Google's documentation, the intended use of TextInputLayout
is with TextInputEditText
or it's descendants, since it gives you access to proper behavior and accessibility services.
Although it is possible to just reference the EditText
, I'm not sure this is the best approach.
But anyway, you can submit a PR and resolve the issue.
But please make sure in that case that you add support of ViewMatchers.isAssignableFrom()
to Kakao and use it in this case so that any type of EditText
would be matched.
@v-rodionov I think at first you can try to change your codebase with TextInputEditText
and if the behaviour will be the same I think it can solve this issue.
@Vacxe We replaced TextInputEditText
toAppCompatEditText
because our users have crash on meizu devices(https://issuetracker.google.com/issues/112105087).
The crash was fixed in new library version, but in alpha only(https://github.com/material-components/material-components-android/pull/358).
Hi, we got a problem :)
In our layout files we have something like
In test
Expected Results:
Test passed
Actual Results:
androidx.test.espresso.NoMatchingViewException: No views in hierarchy found matching: (is descendant of a: (with id: com.test.test:id/textInputLayout) and an instance of com.google.android.material.textfield.TextInputEditText)
It's because KTextInputLayout has check
Do you have any reasons to check TextInputEditText ? I think it's possible to replace TextInputEditText to AppCompatEditText or EditText TextInputEditText extends AppCompatEditText