Closed ToshKoevoets closed 11 months ago
Hey @ToshKoevoets, from the package.json you have shared, the react-native version is 0.71.14, so its a bit confusing whether this issue is 0.73 specific?
That's my bad; apologies, shared with you the package.json after hours of debugging. It took me a while to figure out RN version was the issue.
I've tried downgrading an existing project, still got this error.
Then I've installed it in a fresh RN cli project, will also reproduce this error.
However installing a fresh RN project in v71 does work.
It's only on IOS, on Android it does work in v0.73.
I've experimented with reanimated, thought it might be the issue, but that's fine to be on 3 (your docs state 2)
Op ma 13 nov 2023 om 06:57 schreef Khushal Agarwal @.***
:
Hey @ToshKoevoets https://github.com/ToshKoevoets, from the package.json you have shared, the react-native version is 0.71.14, so its a bit confusing whether this issue is 0.73 specific?
— Reply to this email directly, view it on GitHub https://github.com/GetStream/stream-chat-react-native/issues/2303#issuecomment-1807520185, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJEFAHTK7JTBWVCVHSWJF3YEGZGLAVCNFSM6AAAAAA7GYJ4GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBXGUZDAMJYGU . You are receiving this because you were mentioned.Message ID: @.***>
Oh, we honestly haven't tested the project with RN 0.73 as it is fairly new. On older versions, we haven't seen any such issues. We will try to test it with 0.73 and let you know. Until then, please stick to 0.71 or 0.72 for now.
I think 0.72 has the same error for IOS, initialy my project was ported to 0.72, which is where I experienced the issue. Then I tried a complete fresh install, which was 0.73. But I only got it working on 0.71. But all the down & upgrading could have also caused the issue. Would need to do a fresh install on 0.72 to be sure.
Op ma 13 nov 2023 om 09:28 schreef Khushal Agarwal @.***
:
Oh, we honestly haven't tested the project with RN 0.73 as it is fairly new. On older versions, we haven't seen any such issues. We will try to test it with 0.73 and let you know. Until then, please stick to 0.71 or 0.72 for now.
— Reply to this email directly, view it on GitHub https://github.com/GetStream/stream-chat-react-native/issues/2303#issuecomment-1807668562, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJEFAGV5QVZZDV7PLBWC3LYEHK4VAVCNFSM6AAAAAA7GYJ4GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBXGY3DQNJWGI . You are receiving this because you were mentioned.Message ID: @.***>
It might be good to add a warning in docs, at the moment with a fresh React Native install you wont be able to use GetStream; I understand it's not a priority & there is a version indication already, but might be save some frustration to clarify it in the docs. Also certain parts of your table say minimum; although not the react native part.
We have our SampleApp(examples/SampleApp) on 0.72.6, and we didn't notice any issue.
It might be good to add a warning in docs, at the moment with a fresh React Native install you wont be able to use GetStream; I understand it's not a priority & there is a version indication already, but might be save some frustration to clarify it in the docs. Also certain parts of your table say minimum; although not the react native part.
We have taken this feedback and will close the issue. Please reach us if there is an issue. Thanks 😄
I had the same issue with react-native 0.72, the OverlayProvider worked fine with android, but I couldn't use it's component in iOS.
So I switched from:
return (
<OverlayProvider>
{childred}
</OverlayProvider>
);
To:
return (
OverlayProvider({children: children})
);
It worked fine with both OS and solve my problem completely
Tried complete fresh install. Not compatible yet with latest react-native?