I love Expo, but upgrading from SDK 51 to 52 is truly one of the hardest challenges a React Native developer can face. I spent hours upon hours trying to resolve issues related to navigation, Gorhom, and other packages. While I appreciate Expo, this release contains numerous bugs that can make a developer feel discouraged-almost like dealing with bare React Native. For now, I’ve decided to stick with SDK 51 until things improve. There are many blog posts from developers struggling to upgrade to SDK 52. Previous Expo upgrades were straightforward, but this one is far from ideal. We’ll wait until SDK 52 becomes more stable. Perhaps Expo could create a blog post or video demonstrating how to upgrade a functional app, addressing the most commonly used packages. Our codebase has evolved since SDK 42, and until now, upgrading was never such a difficult process.
My upgrade RN 0.68 upgrade to RN 0.71 was a hell's road trip, i dont know what could be worse than that, hope expo by default is way better, since it is the preferred way nowadays.
God, I was facing difficulties while upgrading from 49 to 51, I ditched it midway and just initialized a new 51 app and dumb-copied everything from 49 to 51. And here you're telling me this upgrade was even harder than that? I was actually thinking of giving this a try 😧
We are living in a golden age. Things have gotten so much easier and now i can confidently make expo modules and never have to expo to bare bones again. What a time to be alive :D
Well, this update broke several parts of our UI. Luckily, we were planning to redo most of it. Still with EXPO GO dropping support for onder SDKs. It could have easily left us in a bit of a pickle. It would be nice if EXPO GO regained the ability to run older SDKs so it didn't feel like we were being rushed to adopt the new SDK before we were ready.
The new expo-video in SDK 52 is truly a game-changer, offering so many features right out of the box. I just want to know how I can enable the quality selection feature for HLS videos?
It's kinda weird because the expo go app (latest version till Nov20) on my android renders the app icon for the splash screen instead of the splash screen, on ios, the splash screen is so tiny
Hi, the splash screen API for Android was migrated to resolve some long-standing issues and adapt to the changes Android 12+ brought. Please see the SDK 52 release changelog for more information: expo.dev/changelog/2024/11-12-sdk-52#big-improvements-to-expo-splash-screen.
The amount of bugs this sdk has is unheard of. Updated from 51 to 52 took 1 week to adapt the code. Crash rate from 0.2% to 5.2% with new arch. I disabled it later. I am not even joking i have a production application with 10 thousand active users. New arch sounds wow until you enable it in production and it crushes to random user devices with errors like Facebook Fabric etc etc random that never happened before 3 years in production.
@@lessko9 performance issues in debug mode. Modal not working on Android deep in react navigation stack. Some of custom native modules broke in mysterious ways. Personally had to open a few PRs upstream.
Expo still has no package for otp autofill on android using sms retriever api and the only one package out there doesn't support the new architecture. We will stick on expo 51 for now. There are also many packages out there that have no support for the new architecture. Maybe expo 52 new arch by default will push more devs to update their packages. For the moment we are stuck on 51
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 have been developing my app on my laptop and running it on my devices and on friend’s devices using debug mode where all the console log output shows up on my laptop. I now want to create a release candidate that’s uploaded to to my Expo account so that people can test it without involving my laptop. I’m having trouble finding a tutorial that explains how to accomplish this. Have you already created a tutorial for this? Are you willing to create one? Basically I’m not ready to release my app to the App Store, and I’d like to continue adding features and debugging my own local copy without changing the copy that my testers are using.
Hi, please check out our EAS tutorial chapter for more information on how to share both debug and release builds: docs.expo.dev/tutorial/eas/introduction/
@@ExpoDevelopers, Looks like Internal Distribution Build isn’t what I want. It’s too complicated to install, has bogus limitations, and requires an Apple Developer account. Why can’t the steps to install my app be: 1: Install Expo Go. 2: Click link or scan QR code. 3: Wait. It’s so simple and doesn’t require any developer accounts, registering devices or putting your device in developer mode.
7:42 fetching data directly from the database in the react component doesn't seem like a good idea, isn't the app fully running on the client device or am I missing something?
New Splash screen config and features and maybe a small tutorial on expo vid and another small one on react compiler. Im a visual learner and seeing official tutorials from you guys helps! The more the merrier!!
please do migrate to 52 yet if you are using an older version they are a lot of issues especially when using axios you get weird errors like [TypeError: cyclical structure in JSON object] LOG error: cyclical structure in JSON object
The upgarding was really shit i just wanna say that. Half of my images broke and gorhom bottom sheet library got downgraded to a version from a few years go
Best Expo release so far 🎉
YOO sogar du hier haha
Totally agree.
Expo 52 is great! Thanks team
I love Expo, but upgrading from SDK 51 to 52 is truly one of the hardest challenges a React Native developer can face. I spent hours upon hours trying to resolve issues related to navigation, Gorhom, and other packages.
While I appreciate Expo, this release contains numerous bugs that can make a developer feel discouraged-almost like dealing with bare React Native. For now, I’ve decided to stick with SDK 51 until things improve.
There are many blog posts from developers struggling to upgrade to SDK 52. Previous Expo upgrades were straightforward, but this one is far from ideal. We’ll wait until SDK 52 becomes more stable.
Perhaps Expo could create a blog post or video demonstrating how to upgrade a functional app, addressing the most commonly used packages. Our codebase has evolved since SDK 42, and until now, upgrading was never such a difficult process.
> I spent hours upon hours
without expo you can spend __months__ upgrading a react native stack so i will say it's just part of the job.
@@flexbox_ o man, that's the point
My upgrade RN 0.68 upgrade to RN 0.71 was a hell's road trip, i dont know what could be worse than that, hope expo by default is way better, since it is the preferred way nowadays.
Same HERE. I will stay in SDK 51 too. You are not alone
God, I was facing difficulties while upgrading from 49 to 51, I ditched it midway and just initialized a new 51 app and dumb-copied everything from 49 to 51. And here you're telling me this upgrade was even harder than that? I was actually thinking of giving this a try 😧
I'm so hyped about the server components functionality!!
It's magic.
That's amazing! Congratulations on this major release!
Its crazy!! Best update!
This is great, thank you!
Outstanding presentation!
We are living in a golden age. Things have gotten so much easier and now i can confidently make expo modules and never have to expo to bare bones again. What a time to be alive :D
Thanks for the awesome work. Expo Team and SWM are amazing!!!
Great job team! Keep up the good work
The only Expo 52 video I was waiting for
Well, this update broke several parts of our UI. Luckily, we were planning to redo most of it.
Still with EXPO GO dropping support for onder SDKs. It could have easily left us in a bit of a pickle. It would be nice if EXPO GO regained the ability to run older SDKs so it didn't feel like we were being rushed to adopt the new SDK before we were ready.
We hear you! Can you please create an issue in our expo/expo GitHub repo with a minimal reproducible example of the UI issues you're encountering?
@@ExpoDevelopers how can i contact you by email because i have the same error as the above friend said
hello , do you mind if i need your help with similar issues on Expo Go, i've had a lot of issues with it😭😭
Thanks Alot expo team
One of the things that I hate is that the Expo app always forces me to upgrade the SDK version in order to continue using it!
i love expo more than i love my children
Expo is good
Your wife must hear this 🤣🤣🤣
What a loser 😅
I ...I love expo more than i love my job
Chill bro
🎉 Great work 🎉
The new expo-video in SDK 52 is truly a game-changer, offering so many features right out of the box.
I just want to know how I can enable the quality selection feature for HLS videos?
I don't know react native and expo. Just saw this video on my recomendation. But this is a huge upgrade.
Expo really is great and help me alot, I hope this release fix previous bugs
Great work people. Plugins on plugins on plugins but hey it's all worth it in the end.
Upgrading from 51 to 52 was flawless! It is faster , cool, but I really hope that debugging improves!
I hope you guys fixed the flash on video mode while using the camera.
It's kinda weird because the expo go app (latest version till Nov20) on my android renders the app icon for the splash screen instead of the splash screen, on ios, the splash screen is so tiny
Hi, the splash screen API for Android was migrated to resolve some long-standing issues and adapt to the changes Android 12+ brought. Please see the SDK 52 release changelog for more information: expo.dev/changelog/2024/11-12-sdk-52#big-improvements-to-expo-splash-screen.
This is banger🎉
Navigation literally broke right after updating the app(((
It’s impossible to pass parameters through setParams in expo-router(
I also got many regressions upon upgrading to SDK 52, including navigation issues.
@@canardeur8390 github issues are more than welcome
I'll give new release a try by updating my existing apps to SDK 52. Best release!
The amount of bugs this sdk has is unheard of. Updated from 51 to 52 took 1 week to adapt the code. Crash rate from 0.2% to 5.2% with new arch. I disabled it later. I am not even joking i have a production application with 10 thousand active users. New arch sounds wow until you enable it in production and it crushes to random user devices with errors like Facebook Fabric etc etc random that never happened before 3 years in production.
We'd be happy to investigate! Can you please create an issue with a minimal reproducible example for any bugs you ran into? thank you!
I couldn't agree more...
Can you created a tutorial of notification and google map, why it's changing
Amazing!
good job
tbh a lot of changes with unexpected behaviors, not stable for now but we will be there
Expo 52 is a stable release wdym
@@lessko9 it's not actually stable if you use it in production. So many bugs.
@@thespacejedi which ones
@@lessko9 performance issues in debug mode. Modal not working on Android deep in react navigation stack. Some of custom native modules broke in mysterious ways. Personally had to open a few PRs upstream.
I had a lot of problems with google ads mob hopefully they fixed that aswell
Expo still has no package for otp autofill on android using sms retriever api and the only one package out there doesn't support the new architecture. We will stick on expo 51 for now. There are also many packages out there that have no support for the new architecture. Maybe expo 52 new arch by default will push more devs to update their packages. For the moment we are stuck on 51
I cant seem to find the blogpost mentioned in the getting started section. Can someone help me out please? Thanks :)
looking forward to it. 2 years ago i ditched react-native because of performance. I hope it'll get better
Nice update
Do you have any thoughts about an NFC add-on?
i have problem in sdk 52 with expo-network cant connection status always false (true in android) and barcodescanner wot working on ios again
Can you please create a minimal reproduction example and share it in our expo/expo GitHub repo so that we can look into the issue further? thank you!
finaly expo release sdk 52
expo notifications dont work in this version?
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?
Hey webwiz - can you create an issue with a minimal reproducible example of this problem for us to look at?
I think we will stay on SKD51 for some time - to much issues we faced with new one :/
This looks amazing! Too scared to update a rather large app from SDK 51 though :(
Don't be scared! This is basically how it should go: x.com/hirbod_dev/status/1859570309268963529
so when do we have the production release? where we can actually be competing with flutter performance release ?
Not sure what you mean by production release. The SDK 52 has already been released.
Comparison with other frameworks depend a lot on your app itself.
nice!!
I have been developing my app on my laptop and running it on my devices and on friend’s devices using debug mode where all the console log output shows up on my laptop. I now want to create a release candidate that’s uploaded to to my Expo account so that people can test it without involving my laptop. I’m having trouble finding a tutorial that explains how to accomplish this. Have you already created a tutorial for this? Are you willing to create one?
Basically I’m not ready to release my app to the App Store, and I’d like to continue adding features and debugging my own local copy without changing the copy that my testers are using.
Hi, please check out our EAS tutorial chapter for more information on how to share both debug and release builds: docs.expo.dev/tutorial/eas/introduction/
@@ExpoDevelopers, Is Internal distribution build what I’m looking for? Does it run inside Expo Go and install with a link and/or QR code?
@@ExpoDevelopers, Looks like Internal Distribution Build isn’t what I want. It’s too complicated to install, has bogus limitations, and requires an Apple Developer account.
Why can’t the steps to install my app be:
1: Install Expo Go.
2: Click link or scan QR code.
3: Wait.
It’s so simple and doesn’t require any developer accounts, registering devices or putting your device in developer mode.
Does he have 2 cameras built into his glasses ? 🤔
(Good job on all the new features, can't wait to try it !)
I'm starting Expo now, i was waiting for this "use dom"
That damn shutter sound I swear! 😂
Splash screen is not working or maybe not showing in the new Expo 52 SDK
got the same problem. The splash screen icon is fetching from the app icon and I can't change anything.
7:42 fetching data directly from the database in the react component doesn't seem like a good idea, isn't the app fully running on the client device or am I missing something?
Can we get updated tutorials?
Are you looking for a specific tutorial?
New Splash screen config and features and maybe a small tutorial on expo vid and another small one on react compiler. Im a visual learner and seeing official tutorials from you guys helps! The more the merrier!!
My project broke with this upgrade!! So many incompatible libraries!!
There's tauri 2 now... What's the purpose?
nice glass
please do migrate to 52 yet if you are using an older version they are a lot of issues especially when using axios you get weird errors like
[TypeError: cyclical structure in JSON object]
LOG error: cyclical structure in JSON object
Ugh i remember having this issue. The worst i ever had.
Upgrade was easy and smooth... Nothing broke on my code
There's a lot of bugs. The splash screen doesn´t resize and expo-updates is broken.
Can you create an issue with a minimal reproducible example of this problem in our expo/expo GitHub repo for us to look at? Thank you!
And Splash Screen...?
Is this free tu use ?
Please build Expo Reader for epub, pdf...
Can't you just use webview for it?
@@najlepszyinformatyk1661 If webview can solve the problem, why we have Expo Video, Audio...
@@najlepszyinformatyk1661 No, I can't. The same reason why they build Expo Video, Audio...instead of using webview.
Broke my entire app
Can't really tell if your glasses are taking a video of me 😂
Does the react compiler mean that hooks such as useMemo, useCallback, etc. are useless now?
You need to fix some issues when building and run for android on windows.
Please i hate ejecting add all the packages
LFG
Add Live activities for iOS!!!! Please!!!!
Everything is broken nativewind is not working properly, statusbar not working properly etc please fix these ASAP
File them a bug on their GitHub
wasn't Nativewind broken before as well?
nativewind is working well for me (but I am at version 4)...if you upgrade, make sure to change all the config files as well
More releases, more bugs bcz of less quality. Less release more quality and stable release. Let's see in which part it will fall.
@@misalambasta plz no second angular
please improve expo intent launcher
Yooo 👋👋
Largest and... buggiest release ever!
Can't even build empty project on win
@@vitalyzema8518 which issues do you have?
We'd be happy to investigate your bug! Can you please create an issue with a minimal reproducible example?
Can’t install node properly 💀
@@ExpoDevelopers yes, but it closed automatically by expo-bot. Maybe because expo-bot thinks it react-native issue
@@vitalyzema8518 feel free to share the link of your issue which was closed.
it brokes react native maps markers and callouts
The upgarding was really shit i just wanna say that. Half of my images broke and gorhom bottom sheet library got downgraded to a version from a few years go
same thing I'm experiencing, Axios just broke on iOS,
This is problematic
I got similar issues, before npx expo-doctor was great, now with latest release it gives several more details and somehow not as seamless as before
Yes! The upgrade was so tough.. took so long to get everything working again.
Same thing bro I had to change so many things in my app 😢
Now rewrite everything in Rust.
GOOGLE MAP!!!!!!!!!!:(((((((
New expo is the shitiest version you have ever made. And the worst part is that ios forces you to use newest expo app. Do better next time.