[go] Load embedded bundle and manifest in release builds (#24412)
[ios] Remove dead code (#24316)
[exmanifests][ios] Convert to swift (#21298)
[Expo Go][iOS] No remote home app loads in release builds (#20416)# Why Per ENG-7047, we need to disable remote loading of home app, and checking for home app updates, for release builds. Upda
[Expo Go][iOS] No remote home app loads in release builds (#20416)# Why Per ENG-7047, we need to disable remote loading of home app, and checking for home app updates, for release builds. Updates and loading from the packager will still work in debug builds. # How Add `#ifdef DEBUG` in several places in `Exponent/Kernel/AppLoader/EXAppLoader.m` # Test Plan - CI should pass - Test Expo Go builds locally and verify that updates are not loaded, and that nothing else is broken # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [x] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [x] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [x] This diff will work correctly for `expo prebuild` & EAS Build (eg: updated a module plugin).
show more ...
switch cloudfront domain to classic-assets.eascdn.net (#15781)* switch cloudfront domain to classic-assets.eascdn.net * build expo asset * fix lint * changelog
[expo-manifests] Rename RawManifest -> Manifest (#14194)
[expo-updates] Factor out raw manifests into their own package (#14183)
[updates] Factor out raw manifest into wrapper class (#12631)
[ios] Expo Client -> Expo Go (#10847)The name "Expo Client" implies that it's the single way to develop Expo app. In the future, it will no longer be as ubiquitous nor the main way to develop. To h
[ios] Expo Client -> Expo Go (#10847)The name "Expo Client" implies that it's the single way to develop Expo app. In the future, it will no longer be as ubiquitous nor the main way to develop. To head off confusion with default development clients, this commit renames the app store development client known as "Expo Client" to "Expo Go". "Expo Go" is the name for the App Store and Play Store development clients that are published under the Expo team's accounts and currently have support for multiple SDK versions. Expo Go is the fastest way to get started. But we've seen billion-dollar companies use the managed workflow for production apps, so names like "Expo Lite" or "Expo Start" wrongly communicate that the app is just for demos or getting started. "Expo Go" implies it's a good way to get started and also not the entire workflow, but also a workflow that can hold its own. In this commit I focused just on iOS (native). Android (native) and Home need to come later. I also changed "experience" to "project" in a few places to start cleaning up our terminology. Tested by running the app and verifying it shows up as "Expo Go" on the home screen in a simulator.
Build out AppLoader request expectation, add more e2e AppLoader request tests, clean up other AppLoader testsfbshipit-source-id: 0620f2c
Strengthen AppLoader failure testsfbshipit-source-id: 6340361
Maintain error state after AppFetcher fails (#2716)* [iOS] Maintain state after AppFetcher failsFixes https://github.com/expo/universe/issues/2631* [iOS][tests] Test that AppFetcher is preserve
Maintain error state after AppFetcher fails (#2716)* [iOS] Maintain state after AppFetcher failsFixes https://github.com/expo/universe/issues/2631* [iOS][tests] Test that AppFetcher is preserved after failed App Loadregression test for https://github.com/expo/universe/issues/2631fbshipit-source-id: 9442ef0
Split XCTest cases into superclasses by runtime environmentfbshipit-source-id: 42bf9f9