I recently upgraded my Expo project to SDK 52, but I'm facing an issue on Android (in production mode): the navigation bar shakes rapidly, making it impossible for users to interact. It only happens with the APK build, not in development. Has anyone else encountered this?
I mostly do webdev, I tried react native with CLI and it was pretty horrific lol. Just when I abandoned RN expo was starting to make some noise, it's pretty neat to see how far they've come. It sure looks like a lot more fun than RN CLI. Very powerful too
@@galaxies_dev will do, specially worth it today that tools like v0 or Bolt can help you out so you can go almost as fast as you would go in your main stack. Future is promising. Cheers mate!
Nice t-shirt ;) Thx for review, but I'm already upgrade my app to SDK52. Main reason for update been unworked switching between native and react parts of splash screen. I seen flickering side-effect. But, how expo developers asks me, sdk52 resolve this issue. Although beta-version didn't helps =) I'm glad
When I updated, I got some problems with modal, I use regular modal from react native, but after updating, the modals kind of moved out of the screen... still don't know why
@galaxies_dev it is impossible to know programmatically if the audio is finished or not. So you can not change the state of the audio button for example change the icon between play ▶️ and pause⏸️. The don't provide any method to handle that.
can you explain to me what Server Component means in react-native? In nextjs it means "react that is ran on a server" ....in react-native there is no such thing as a server, we produce a .apk or whatever that has this js runtime that communicates with native kotlin/swift code. What the heck does server component mean here???
RSC in Expo means you can run React on a server. This means first-class data fetching, support for secure environment variables, also streaming and loading with Suspense/async functions instead of hooks. The server must be deployed to a host in production.
@@Baconbrix ok so basically they added the same thing to react-native here as nextjs added to react ...meaning, FE has its own server that pre-renders stuff right? Meaning that there will be .apks that are not working because server is shut down. Cool but strange :D but nextjs was strange too at first i guess
@@asifali_official3137 yeah you can absolutely use native modules. It’s sort of what the whole thing is built around. POD installs work fine. You can use config plug-ins with a string of text and an extra command. Dev client in EAS is 100X simpler than the alternative.
@@SolelyMat Have no idea, my devs don't understand how it works. we just now react, so expo go suppose to be simple in use, but my devs have no idea what to do with new SDK 52
@@CasaDeMold The behaviour you described has nothing to do with SDK 52, that's just how React Native works, some native modules require you to compile the app to test them, since the JavaScript bridge generated by the expo go app can't acces them.
⚡ Stay on top of Expo commands with my new cheat sheet: download.galaxies.dev/cheat-sheet
Thanks for the video! Seems things like Drawer Navigation still aren't ready for SDK 52. I guess I'll wait until things are more stable.
Love it! Thanks for being on bluesky
😎
Great video. How do you managed to have a dropdown menu in terminal? Thanks and looking forward to see expo modules.
Please, do a video about expo-router/ui! Styling a good tabbar with nativewind!
Great suggestion!
I recently upgraded my Expo project to SDK 52, but I'm facing an issue on Android (in production mode): the navigation bar shakes rapidly, making it impossible for users to interact. It only happens with the APK build, not in development. Has anyone else encountered this?
Great video! Would love to see a tutorial on React Native DevTools next!
Coming soon!
I mostly do webdev, I tried react native with CLI and it was pretty horrific lol.
Just when I abandoned RN expo was starting to make some noise, it's pretty neat to see how far they've come. It sure looks like a lot more fun than RN CLI. Very powerful too
It definitely is, give it a try :)
@@galaxies_dev will do, specially worth it today that tools like v0 or Bolt can help you out so you can go almost as fast as you would go in your main stack. Future is promising.
Cheers mate!
Nice t-shirt ;)
Thx for review, but I'm already upgrade my app to SDK52.
Main reason for update been unworked switching between native and react parts of splash screen. I seen flickering side-effect. But, how expo developers asks me, sdk52 resolve this issue. Although beta-version didn't helps =)
I'm glad
Yeah! We are waiting for react native devtool dedicated video 💚
Coming soon!
Love your so much. Next tutorial ASAP I request Expo SQLite
Noted!
Does the New Architecture need any change in the app's source code to work?
short answer if you lucky no. but some libs what you use may not 'support' it, so it may not work. Run expo doctor and you will see
No usually not really from your side, only from the packages you use
When I updated, I got some problems with modal, I use regular modal from react native, but after updating, the modals kind of moved out of the screen... still don't know why
Thanks for letting us know in advance. Will wait at least 3 months before moving to SDK 52.
3:02 : when you hear such phrase you know there is another bug coming 😂 😂
Only I can't now build in expo? Configs not working too. Release looks good. But seems with a lot of issues.
Yeah in general everything still works for me!
@galaxies_dev yes. After 5 cleaning and 10 build starts work too 😂
React native Expo are Best 🎉❤
Agree
Thanks!! :)
No problem!
A lot of bugs appeared when I upgraded. Will be working on it for few days at least
I updated my codebase to expo sdk 52 and now my android app keeps crashing ffs i hate to go through all these lines of codes
❤
I would like to request for tutorial
an app build with expo sdk 52
Server Components and Server Actions
Working on a demo!
Why you skipped dom components? It is the biggest feature in this latest release
Because I already had a full video on it an will cover it in more detail again soon :)
Expo camera it's just a pain in the a$$.
Same thing for audio.
Same thing for audio.
Why do you think so?
@galaxies_dev it is impossible to know programmatically if the audio is finished or not. So you can not change the state of the audio button for example change the icon between play ▶️ and pause⏸️. The don't provide any method to handle that.
Finally you are here. 😠
I am!
@@galaxies_dev I am glad though.
can you explain to me what Server Component means in react-native? In nextjs it means "react that is ran on a server" ....in react-native there is no such thing as a server, we produce a .apk or whatever that has this js runtime that communicates with native kotlin/swift code. What the heck does server component mean here???
RSC in Expo means you can run React on a server. This means first-class data fetching, support for secure environment variables, also streaming and loading with Suspense/async functions instead of hooks. The server must be deployed to a host in production.
@@Baconbrix ok so basically they added the same thing to react-native here as nextjs added to react ...meaning, FE has its own server that pre-renders stuff right? Meaning that there will be .apks that are not working because server is shut down. Cool but strange :D but nextjs was strange too at first i guess
Will show it in a demo soon!
3rd party libraries are taking a hit started new project today installed my go to library and voila they no longer working
no wonder my app is taking a shit now.
🤷♂️ Who cares. What about Angular 19!
🤣, don't forget, kids toys has also evolved.
Expo is useless , we can't directly access native modules, Using bare React Native is better than using Expo.
@@asifali_official3137 yeah you can.
What do you mean? Just don't use Expo Go, compile the dev app via EAS and you can acces whatever you want
@@asifali_official3137 yeah you can absolutely use native modules. It’s sort of what the whole thing is built around. POD installs work fine. You can use config plug-ins with a string of text and an extra command. Dev client in EAS is 100X simpler than the alternative.
@@SolelyMat Have no idea, my devs don't understand how it works. we just now react, so expo go suppose to be simple in use, but my devs have no idea what to do with new SDK 52
@@CasaDeMold The behaviour you described has nothing to do with SDK 52, that's just how React Native works, some native modules require you to compile the app to test them, since the JavaScript bridge generated by the expo go app can't acces them.