The changed code is pretty self-explanatory. In my case I have a step of 1 in my app, and setting the value from the backend that was decimal was resulting in unexpected floating precision on the rating bar. This behavior is now consistent with how step and setRating work for Android's native RatingBar.
The changed code is pretty self-explanatory. In my case I have a step of 1 in my app, and setting the value from the backend that was decimal was resulting in unexpected floating precision on the rating bar. This behavior is now consistent with how step and setRating work for Android's native RatingBar.