LinasKo

@PawelPeczek-Roboflow, any insights on this?

Hi @arpit2167407 👋 We're a bit behind with reviewing user submissions at the moment. As it stands, there's a PR for this already, so I wouldn't encourage new contributions.

Hi @Bhavay-2001, I've had a look, and we have something more urgent. How does #1293 sound? (you may reply there)

@SkalskiP, Here's some updates. I've addressed every comment you had, with the major changes being as follows: 1. Removed `_set_at_index`, without any logic changes to `__setitem__` - I found that...

Hi @SkalskiP, I've tidied this up - I believe it can now be merged.

Closing the issue as this is fixed.

Happens to me as well. It seems that `native-base` explicitly requires the latest version of both `react-native` and `react`. But `react-native` specifically depends on an older version of `react`. Are...

I don't see how that would work - the versions conflict within `native-base` itself. Minimal reproduction steps (valid until the next `react-native` update probably, but would break again in the...

The issue of the standalone install still persist, but I am now able to install `native-base` in expo without errors (albeit with many warnings). And hey, I've learnt a bit...

Hey @illian01 :wave: Thank you for reporting the issue! You're right - it definitely looks wrong. We'll need to rethink how we do it a bit. If anyone in the...