UI Kit crashed on Android

[msanvarov]

Hey @hetmann, love the ui kit as always, just ran into a problem when I started using it on android. It gives the following error. I googled how to resolve this and tried to debug wherever flex is being passed in a boolean rather than a double. I ejected the expo app to see debug the Java code but can't seem to find where the issue is coming from.
Wondering if you have come across this issue and have seen this happen before on android. It works fine on IPhone though.

[hetmann]

Hey @hetmann, love the ui kit as always, just ran into a problem when I started using it on android. It gives the following error. I googled how to resolve this and tried to debug wherever flex is being passed in a boolean rather than a double. I ejected the expo app to see debug the Java code but can't seem to find where the issue is coming from.
Wondering if you have come across this issue and have seen this happen before on android. It works fine on IPhone though.

Thanks for pointing this out. I am aware of this error, this is due to the fact flex prop is receiving flex true or false and is updated to 0.5 or something like that.
Did you used the npm package or directly this repo?

[msanvarov]

Hey @hetmann, love the ui kit as always, just ran into a problem when I started using it on android. It gives the following error. I googled how to resolve this and tried to debug wherever flex is being passed in a boolean rather than a double. I ejected the expo app to see debug the Java code but can't seem to find where the issue is coming from.
Wondering if you have come across this issue and have seen this happen before on android. It works fine on IPhone though.

Thanks for pointing this out. I am aware of this error, this is due to the fact flex prop is receiving flex true or false and is updated to 0.5 or something like that.
Did you used the npm package or directly this repo?

I'm using the npm package you have published. I'm thinking this has to do with a utility function somewhere that is breaking. I'm surprised it doesn't crash for ios because in Objective C there is no proper way to convert a boolean into a number aside from doing

bool vIn = true;
int vOut = vIn?1:0;