Conversation
I had some time to see into problem. If you look closer to the stack trace, you can see that it fails when trying to access list's item. It means, that your |
I pulled my last enhancement from master that I did, I hope now your functionality will be covered |
@ashdavies So, there are some issues with your PR, but in general now list item view is trying to match in the correct window, according to new stack trace:
|
I believe there was an issue with the view matcher because it was trying to match a child view of the list item, but was inflating |
Ok, so your autocomplete now passes, but please modify |
Whoops! I missed that one, thanks for the hint |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now looks legit. I'm happy that we could resolve you issue (if we did) 👍
Great! I've not yet tried it with our production repository, but I'm confident that it will resolve the issue, thanks for your help! 😄 |
🎉 |
With reference to issue #42 this provides a sample demo for the
AutoCompleteTextView
usage with aDecorPopupView
which is currently unsuccessful.Stack trace indicates that the platform popup view is not present in the view hierarchy, or that assertions are being made against the wrong window.
It can also be noted that introducing the following to the
KListView
builder is also unsuccessful.