Open mtrakal opened 1 year ago
related for example to: https://github.com/material-components/material-components-android/issues/923
I understand crash, but I'm not able recognize even fragment/activity when it crash only in library code... So I'm not able to know on which screen it crash and not able know which slider on specified screen...
I faced the same problem. We have a lot of sliders on different fragments. Most of the stack trace in Android are useless and do not help to find the error.
Description: There is no way (when you have more sliders on one screen) which slider crash.
Expected behavior: Show ID or line of code where crash happens.
Source code: Just use slider and set data incorectly or in wrong order (set valueTo before valueFrom, or set step before ranges, etc... milions of combinations will cause slider crash, not so hard force into crashes like this)
Android API version: Any
Material Library version: Any
Device: Any
We need to know which slider / line of code caused this crash in our code. We have many sliders on same screen, dynamic data from backend, but how we should know which slider cause crashes like this? Not just this one, sometimes current value is out of range (because conditions was changed, but range is still in previous range...) There is no easy way how to invalidate all data together (valueFrom, valueTo and current values). When you start set new valueFrom/To it will crash on current value out of range... When set new current value it will crash on current value out of range (because we didn't set yet new range from/to)... etc. Set all values together before start validation will save a life of all whales (and devs). But as a first step WE NEED KNOW WHICH SLIDER CRASHED!