Open darylsze opened 7 years ago
Hi,
it's not maintained as t should be. I'll try to look into the issue over the weekend.
Hi,
Thanks for your following up. May I ask for your progression?
After my investigation these days, I found that Horizontal Picker used some sdk support v4 widget features, which should be the crux of the bugs.
From Fabric, it shows the problem from "android.support.v4.view.accessibility.AccessibilityNodeInfoCompat”, and your source code has implemented “onPopulateNodeForVirtualView” with “AccessibilityNodeInfoCompat” parameters, which crash the activity.
Hope above information helps! I am greatly appreciate your following up to the project which you are no going to maintain far far ago. Cheers!
Best regards, Daryl SZE (wind)
On 2017年9月1日 +0800 PM3:54, Blaž Šolar notifications@github.com, wrote:
Hi, it's not maintained as t should be. I'll try to look into the issue over the weekend. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
Hi, may I know is this project no longer maintained? Currently I found that it crashes in lots of Android 7.0/ 7.1.1 and some of Android 6.0 / 5.0 devices. This may be a core library bugs in Android system which you have used.
The crash message is hard to read and untraceable. Callbacks must add text or a content description in populateNodeForVirtualViewId()
I have googled, datePicker is a known bug in ALL Samsung Android 5.0 devices, but now it happens in Android 7.0 or above.