fabsimilian

Any updates to this issue? It maybe is a reflection error? We really have to get rid about this strange bug :/

Thank u for the quick response. Hm, I'll try it, but the problem is that i can't reproduce this error / behaviour. I just see the logs from the crashes....

What i don't unterstand is how changing the order should affect the library to choose the right parameter names when deserializing?!

Ok I will give it a try!

So we just released this fix, but the error still occours. ``` Fatal Exception: java.lang.NumberFormatException: Invalid int: "z1 compact" at java.lang.Integer.invalidInt(Integer.java:137) at java.lang.Integer.parse(Integer.java:374) at java.lang.Integer.parseInt(Integer.java:365) at java.lang.Integer.parseInt(Integer.java:331) at co.uk.rushorm.core.implementation.RushColumnInt.deserialize(RushColumnInt.java:22) at...

The Bug impact is on around 8% of the devices. Mostly samsung galaxy s5 with Android 4 & 5 HTC One, HTC One M8, and HTC One S and some...