You guys totally let down the whole community of developers. You can not just push folks to buy a premium Expo account. You were the one who took the responsibility when creating the Expo ecosystem Even official React Native recommends you as the best way how to start with React Native - and now you greedy asses decided to get money for something that was always free? I am done with Expo and I truly hope others will move to the clean React Native or Flutter.
@jaroslav.huss There are several messages in this thread about how you can do it without needing to pay Expo for anything.
Hi @jaroslav.huss. I’m sorry you feel the way you express yourself here. I wish we could respond with “it already works”. As you correctly mentioned, we maintain the infrastructure around EAS and the classic build (Turtle v1). This also includes shielding others from breaking their apps to allow some people to build with enterprise signed apps. We have to carefully apply this change in a way everybody’s app works, and that’s why we can’t just upgrade it right away.
That being said, just like @wodin mentioned, there are a few other ways you could build your app right now. And not every option requires you to have a subscription. Here are they:
- Using EAS to build your app (requires subscription, until the general availability)
- Using EAS CLI locally to build your app (does NOT require subscription)
- Using Turtle CLI locally to build your app (does NOT require subscription)
- Manually resigning the app after building it (does NOT require subscription)
I would also like to ask you to be civil in this community. Accusing us of “letting down the whole community” or calling us “greedy asses” does not help solve this issue. It only makes the people trying to solve these issues, and many more, feel bad — kindness and willingness to help others bring you way further in this community.
As @charliecruzan mentioned, if you support us in solving these issues and have a subscription, we are happy to refund this month if you send a note to billing@expo.dev.
Cheers,
Cedric
Can I just clarify something. When charliecruzan says “I would not rely on us upgrading our expo build machines to Xcode 13.”
Does that mean it won’t happen ever, or that you have no idea how long it will take but it is a thing you would intend to do?
We’re still looking into Xcode 13 support for expo build:ios to support it for the next SDK release, SDK 43. The complexity comes from the breaking changes introduced with Xcode 13. We are also looking into supporting Xcode 13 with SDK 42.
So it is an upgrade we intend to make
It’s also possible that we will solve the issue with iOS 15 enterprise builds earlier, but without upgrading xcode
Dear Cedric,
my apologies. I just got scared because of deadlines and since I am fully dependable at this moment on the Expo ecosystem, this rather unpleasant situation really scared me since I have to rebuild all our apps till Sunday.
Once again sorry for raged post - you guys are doing of course amazing job.
Kind regards
Let’s consider it water under the bridge 
You should be able to still build the right version with the options mentioned in this thread. If that doesn’t work for you, feel free to ask questions (either here or on discord).
I agree this isn’t an ideal state. I hope we have some good news soon, but rest assured, we are working on it.
We just released a new image for our classic iOS builds(but we are still using the same version of Xcode), new enterprise builds created with expo build:ios should now work on iOS 15 devices. I tested that on SDK 42 but older SDK should also work, please report if you still see any issues.
I upgraded to expo 42 and ran expo buidl:ios but I still get the original error that the app isn’t built for this device and needs to be upgraded. Do I have to download a separte sdk for ios 15?
can you link to the build? I’m only seeing app store builds on your account
I built it locally using Turtle cli as stated in the answer for this.
Here is a link to the .ipa builid. Is this what you’re referring to?
Thank you for the help btw!
I built it locally using Turtle cli as stated in the answer for this.
ok I’m confused you just mentioned in comment above that you built it using expo build:ios and now that you use turtle-cli, so which is exactly?
If you are building locally you need to have macos big sur and reasonably new xcode (we use 12.1)
I think I might have done the expo build:ios using the previous sdk then since it gave me the error I tried Turtle cli as indicated in this thread.
I am attempting to deploy on app to my local device using Apple Configurator 2 and I’m running Catalina. Would the expo build:ios ipa (using sdk 42) be only for test flight or can it also be deployed to a single device running ios 15?
I’m running Catalina
to build enterprise apps locally you need to have big sur or use expo build:ios
Would the expo build:ios ipa (using sdk 42) be only for test flight or can it also be deployed to a single device running ios 15?
That depends on your apple account
- app store build can be installed via tesflight,
- enterprise can be installed on the device directly
Ok I get it. What about with EAS build? Can I deploy directly to that with out using Test Flight?
Yes, you can use ad hoc distribution (regular $99 Apple Developer account) or enterprise distribution (enterprise $299 Apple Developer account) to create builds that run on your device without using TestFlight.
- EAS Build documentation for internal distribution. You can use either of Apple’s recommended methods with ad hoc or enterprise provisioning profiles: Internal distribution - Expo Documentation
- Expo documentation for classic builds: Sharing pre-release versions of your app - Expo Documentation
- Apple documentation on ad hoc distribution: Apple Developer Documentation
I can confirm a build using SDK Version 40 worked for me on iOS 15. Thanks!
Is OS 15 compatible with SDK 41? It seems like running eas build throws an error because your server build settings don’t support it yet. Should I use EAS build local?