Steve Moretz: EAS Build is the way forward here: https://blog.expo.io/expo-application-services-eas-build-and-submit-fc1d1476aa2e

we'll release a beta of managed support in the coming weeks

Brent Vatne: When I heard about that EAS build it already blew my head.Didn't know that can support the size reduction as well!

That is just staggering!

Will it be free?

For building once in a week maybe for example?

That is a game changer.

I have a hackintosh it is on my lenovo laptop, apple introduced the new cpus they built and they're going to that gradually.

Meaning every one like me or with old macs using intel cpus will get totally screwed if they can't afford to buy a new mac!

EAS can save our lives!

THANKS MAN

Steve Moretz: https://expo.io/pricing

Michael Wood: So none of EAS build/EAS Submit/EAS Update will have a free tier?That is disappointing!

At least developers should be able to make the apps for free with EAS build and then for EAS Submit and EAS Update it is logical to pay.

Steve Moretz: I think you misread! It says at the bottom "these services will be available under the free plan"

Michael Wood: My apologies, I just saw the ticks of the features under free plan, under comparison table.Thanks for clarification.

Michael Wood: no sir whole thing is a paid service.

Ibrahim Arif: Please understand that "After graduating from preview" and "will be" means "in the future". They are still working out some issues. When they have done so it will be available as part of the free plan.

Michael Wood: oh ok.. I didn't read that. Thanks man.

We've designed EAS to be optional and independent from Expo. Making apps with Expo doesn't require EAS. It's for developers who want a cloud service for builds, updates, submissions, team coordination, and other parts of their development workflow.

One reason we've designed Expo to be independent from EAS is that we believe that making Expo free and open source is one of the best ways to make Expo succeed. You can use your own computer to build your apps and your own server to host your updates (it's kind of like the web in this way). Or you can build and set up a workflow on servers from the cloud provider of your choice like AWS or EAS. EAS is designed and run by the Expo team for making Expo apps.

We understand that customers need time to develop the first version of their app and want to try out EAS to see how it works for them. To help small customers become big ones, we want to offer a level of free usage that's useful for starting out before they're ready for production.

Behnam Kamrani: Hello, did you fix this issue? I'm also experiencing this

Esther Amara: sorry; I did not!

Esther Amara: "enableDangerousExperimentalLeanBuilds" : true fails in sdk40 but works in 39. I tried all I could but to no avail. I had to downgrade to sdk39

Nathanael Martins: I think I fixed it, kinda. I had to download expo-splashscreen package, and it worked.

Esther Amara: Wow! okay. Definitely trying it right now

Edit: It worked. You're a life saver Esther. My app size went from 53 to 31.4 MB

From your name, you're Nigerian. Do you mind if we connect? I'm in search of a smart React Native developer from Nigeria. Here is my Telegram handle https://t.me/nate_martins

Nathanael Martins: Thank you. Sending a message now

Sascha Reuter: Yes, EAS Build is the planned solution:

"The goal for managed projects with EAS Build is to remove the limitations commonly encountered with the expo build service: it will produce smaller binaries by only including the dependencies you need[...]"

Nathanael Martins: I am getting this warning in play console on my managed flow app too generated on sdk-38.

Summer Syed I just ignored the warning for now while anticipating the Expo team to come up with a better way to reduce app size. At least the Play Store does not prevent the app from being served.

This doesn't work anymore if you're using sdk40. Expo team, kindly fix this Michael Wood

Edit: For future readers, to get it to work, you have to install expo-splash-screen before building.