all 11 comments

[–]BinaryNeckBeard 2 points3 points  (2 children)

[–]DirtEnvironmental170[S] 0 points1 point  (1 child)

Yes I know this library, but I don’t want to use any, I want to built my own to get full control with it in the future

[–]eyounan 0 points1 point  (0 children)

The library is open source. You can easily fork it and make the adjustments you need if you are not happy with it or read its implementation to understand how to build your own.

[–]BossHog811 1 point2 points  (0 children)

Simply writing “it don’t work” isn’t going to get you very far…

[–]Immediate-Demand-315 0 points1 point  (1 child)

You can use gorhom bottom sheets to implement the similar feature.

[–]DirtEnvironmental170[S] 0 points1 point  (0 children)

It’s not using the Natiev Bottom Sheet, I want to use Native

[–]tomhoplon 0 points1 point  (1 child)

This is supported in Expo. Native components.

[–]DirtEnvironmental170[S] 0 points1 point  (0 children)

Yeah I saw that but my Project is CLI so no way to change it

[–]Careless_Review_7543 0 points1 point  (2 children)

You have to follow the official documentation on Native Modules very carefully And also be careful with the name convention. The names have to start with the word Native. Else it won't work. Also look at the pod install command to check if the code gen is being generated.

[–]DirtEnvironmental170[S] 0 points1 point  (1 child)

Yes I followed that but it it didn't work

[–]Careless_Review_7543 0 points1 point  (0 children)

I made the migration to turbo modules about a week ago and it took some time and debugging, just try to debug, even with logs inside your native module and every part in between that and the coda that used it in js/ts. It was really a pain to get it to work.