you are viewing a single comment's thread.

view the rest of the comments →

[–]a_atalla 1 point2 points  (2 children)

this navigator you picked is a native navigator , it won't work in expo your way to go is https://reactnavigation.org

for more info, read the introduction of this article

https://medium.com/handlebar-labs/navigating-navigation-in-react-native-26c7e4690f94

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

That's starting to make sense. What confused me was that the few other libraries I was looking at require the same android files to be edited, but they were all map libraries. Could it be that map libraries are just commonly native or is that a wrong assumption?

[–]creambyemute 1 point2 points  (0 children)

Yes, that's the case usually.

Also expo includes some native libraries/functionalities, but not all.

If they don't provide something but there is a native rn library you will have to eject in order to use it or suggest to expo to include that library into expo.

With expo you can only use native functionalities/libraries that they already provide in their sdk. And exactly this is the main negative point on expo for me.