Dude these videos are amazing! It's been a while since I used React Native and coming back seeing the new router in action in your video really makes it sink in and make sense to me! Thanks for the great video!
Hi! nice video, I would like to know what if i want to have some screens with the tabs layout and some others without it, also the same thing with the header, what if i want a custom header in custom components?
You know, it would be great if you included solutions for common problems like if you can't get the icons to show up and such. AND provided a Git Repo. I literally can't get the Ionicons to show up and you give no instructions for if that doesn't happen ... for example.
Interesting. This video is fresh, but I dont have property for StatusBar like "style", i have "barStyle={"light-content"}" But Thanks. It was really Useful. Hello from Ukraine
Yes, since, in most cases, you'll have modal/stack screens. You can add these screens inside the and apply properties to each screen, like presentation animation.
I don't understand. Isn't this the official Expo channel? how is it that you just silence warnings without finding/solving the issue? you just said I don't know. If I wanted to hear "I don't know" I can find other youtubers.
@@ExpoDevelopers I think he is referring to the fact that there was a warning regarding the routes which you silenced using Logbox.ignoreAllLogs(true) at 11:45, which I do find odd myself. As someone else stated, the issue was fixed by removing the line found in the _layout.tsx file in the (tabs) folder.
That too many screen error is because +not-found route also added on Tab.Screen means on (tabs)/_layout.tsx file at the bottom, if we remove that line of code then it will resolved. this line is causing that error on app/(tabs)/_layout.tsx
How come the app renders the not found screen for any other route which isn't "/" or "/about"? For example, it would work for "/test" or "/sffsf" or anything else. Where have we defined it to do this?
Expo Router has a fallback route for unmatched routes. This means it will automatically catch any unmatched route, but we can further customize the unmatched route s by creating the not-found screen.
Git repo for the lessons would be much appreciated to go along with your amazing videos!
github.com/expo/examples/tree/master/stickersmash
YES PLEASE
Dude these videos are amazing! It's been a while since I used React Native and coming back seeing the new router in action in your video really makes it sink in and make sense to me! Thanks for the great video!
I've been struggling with RN since 2018 (not proud about that!). Finally I can understand the core concepts .... thank you !
Feels good to be in class
To fix the error it is necessary to delete in _layout.tsx file situated in the (tabs) folder.
Very cool! Thank you, bro
Helpful
Hi! nice video, I would like to know what if i want to have some screens with the tabs layout and some others without it, also the same thing with the header, what if i want a custom header in custom components?
Check out docs.expo.dev/router/advanced/nesting-navigators for a comprehensive guide on nesting layouts
I don't get the swipe back from the about screen at all.
You know, it would be great if you included solutions for common problems like if you can't get the icons to show up and such. AND provided a Git Repo. I literally can't get the Ionicons to show up and you give no instructions for if that doesn't happen ... for example.
Interesting. This video is fresh, but I dont have property for StatusBar like "style", i have "barStyle={"light-content"}" But Thanks. It was really Useful. Hello from Ukraine
I am just stuck on No found screen i cant see Tab buttons. I copied all codes from expo docums
which extention give the suggestion as shown in the video?
Github copilot
What about if I have name folder and it has index file line explore name then how routing will work ?
_layout.tsx is meant to have shared ui , headers and tabs, but why is used in it ? Do we have to always mention in _layout file ?
Yes, since, in most cases, you'll have modal/stack screens. You can add these screens inside the and apply properties to each screen, like presentation animation.
How can we integrate animations and transition using Tabs ?
CAN YOU PLEASE PUT IN A REPO ON GIT SO WE CAN CHECK WHEN WE GET IT WRONG?
The source code is available in our GitHub examples: github.com/expo/examples/tree/master/stickersmash.
I don't understand. Isn't this the official Expo channel? how is it that you just silence warnings without finding/solving the issue? you just said I don't know. If I wanted to hear "I don't know" I can find other youtubers.
Not sure what you're referring to here. Do you have a question that we can help answer?
@@ExpoDevelopers I think he is referring to the fact that there was a warning regarding the routes which you silenced using Logbox.ignoreAllLogs(true) at 11:45, which I do find odd myself. As someone else stated, the issue was fixed by removing the line found in the _layout.tsx file in the (tabs) folder.
That too many screen error is because +not-found route also added on Tab.Screen means on (tabs)/_layout.tsx file at the bottom, if we remove that line of code then it will resolved.
this line is causing that error on app/(tabs)/_layout.tsx
3:04 как в vs code сделать автозаполнение/подсказки?
🌋🌋
Why didn't you use arrow functions for the screen?
It does not make any difference
@@ExpoDevelopers okay, most people use it and that was why I ask
Somehow this guide is giving me error not matter how much I copy paste or really do single step by single step.
How to add bottom navigation + drawer in a single page
Check out docs.expo.dev/router/advanced/nesting-navigators for a comprehensive guide on nesting layouts
curio mensen hiero?
How come the app renders the not found screen for any other route which isn't "/" or "/about"? For example, it would work for "/test" or "/sffsf" or anything else. Where have we defined it to do this?
Expo Router has a fallback route for unmatched routes. This means it will automatically catch any unmatched route, but we can further customize the unmatched route s by creating the not-found screen.
which extention give the suggestion as shown in the video?