BadgeView | Badge view with animated effect | Android library

If the app works in debug but not in release, it's probably because Proguard minified your classes and deserialization no longer works due to different (shorter) class and property names.

Make sure you have this in your proguard:

Try updating your buildToolVersion to 27.0.2 instead of 27.0.3

The error probably occurring because of compatibility issue with build tools

I think the solution here is easy: Add a @Keep - Anotation to your model (SomeResponse), so the marshalling-names shouldn't be obfuscated anymore. :-)

Maybe you misunderstand the using of IValueConverter and ViewModel . If want to binding data , you need to create ViewModel to bind it. And if want to convert value , first need to bind a data soure ,then bind a value converter to convert the paramater of data source .Having a look at this Xamarin.Forms Binding Value Converters document.

Data bindings usually transfer data from a source property to a target property, and in some cases from the target property to the source property.

From code you just bind a IValueConverter , this will not work.

Here is a Sample about using ViewModel :

I accomplished this with react-redux. Roughly something like this:

Problem is with BadgeView().setCoeff(coeff: CGFloat(porcentaje)/100, animated: true). In this line, you are creating a new instance of BadgeView and calling a method on it. Not to the instance that is displayed in the UI.

Try to understand OOPs concepts, Refs: https://www.math.uni-hamburg.de/doc/java/tutorial/java/javaOO/classvars.html

When upgrading to 3.1, I updated all the libraries to the latest version and got the same problem as you.

I rolled back the build.gradle file and it compiles without issue. I then updated one library at a time and found that the retrofit was the one causing the problem (2.4.0 didn't work for me, but 2.3.0 works).

I have found what the issue was. I was declaring the badge even before adding the tabs. i should have declared after "tabHost.addTab("YourTab1..")".

That is a ported version of the Java version that is deprecated and that issue was in the original.

A workaround is to remove the badge when the value goes over 99 and add it again instead of just increasing the count.

I have not looked at the C# version, but assume the code of BottomBarBadge.java is the "same" and the size of the badge view is only calculated once during the attachToTab method. So the workaround works since the attachToTab/adjustPositionAndSize flow is called again, but the badge contents should really be checked to determine if they would overflow the badge circle and re-call the adjustPositionAndSize, ...I think... ;-)

re: https://github.com/roughike/BottomBar/blob/master/bottom-bar/src/main/java/com/roughike/bottombar/BottomBarBadge.java#L94

There are a bunch of issues/bugs with removing/recreating a badge, etc.. in that library (which is slightly different than the original Java library).

While this should be in the library itself, you can do this to properly resize the badge when setting the count: