[go] Load embedded bundle and manifest in release builds (#24412)
[tools] Switch expo home publishing to EAS update (#24216)
[home][ci] Remove dogfood expo home variant (#24193)
[iOS] Refactor version manager in Expo Go (#23624)
[go][ios] Fix Expo Go not respecting the orientation field on initial load (#23581)# Why https://github.com/expo/expo/issues/23368, ENG-9262 On iOS 16+ Expo Go wouldn't respect the values under
[go][ios] Fix Expo Go not respecting the orientation field on initial load (#23581)# Why https://github.com/expo/expo/issues/23368, ENG-9262 On iOS 16+ Expo Go wouldn't respect the values under the `"orientation"` key in `app.json` until something caused the view controller to update it's orientation using `supportedInterfaceOrientaitons` (for example opening the dev-menu). On iOS 15 it would work on initial load but it was possible to cause the "orientation" field to stop working. (For example setting the "orientation" key to landscape, opening an app, opening the dev-menu, going home and opening the app again while keeping the device in portrait). # How When transitioning to an app Expo Go will make the root view controller check for the supported orientations. On iOS 16+ this is archived with a built in method, and on iOS < 16 this is done by setting the UIDevice.orientation.current (via a `ScreenOrientationRegistry` method) to the desired orientation. # Test Plan Tested in Expo Go on iOS 16 and 15
show more ...
[go] Fix DevMenu window bounds on macOS (#23318)# Why Partially fixes ENG-9201 # How By not manually setting `bounds` to `[[UIScreen mainScreen] bounds]` the DevMenu automatically resizes
[go] Fix DevMenu window bounds on macOS (#23318)# Why Partially fixes ENG-9201 # How By not manually setting `bounds` to `[[UIScreen mainScreen] bounds]` the DevMenu automatically resizes when resizing the Expo Go window on macOS # Test Plan Run Expo Go on iOS and macOS <table> <tr><th>iOS</th><th>macOS</th></tr> <tr> <td> <video src="https://github.com/expo/expo/assets/11707729/065d746f-7def-4f9e-ad39-e5cc3e0e1c8c"/> </td> <td> <video src="https://github.com/expo/expo/assets/11707729/b3f1e6e7-42e3-4def-89f5-78941e6f49ad" /> </td> </tr> </table> # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [ ] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [ ] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin).
Remove Amplitude from Expo Go (#22523)
[exupdates][ios] Start converting to swift (#21320)# Why Start the conversion process of the expo-updates library by converting EXUpdatesUpdate and subclasses. # How Convert manually... l
[exupdates][ios] Start converting to swift (#21320)# Why Start the conversion process of the expo-updates library by converting EXUpdatesUpdate and subclasses. # How Convert manually... lol. The main note is that we can't use swift nullability/type forcing operators (`!`, `as!`, `as?`) etc since the previous implementation was relying upon NSAssert to raise an NSException which is caught in the calling code, so I added new extension functions to replicate the behavior (similar to EXManifests util functions). # Test Plan Build and run all tests. # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [ ] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [ ] This diff will work correctly for `expo prebuild` & EAS Build (eg: updated a module plugin).
[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).
[iOS][Expo Go] Add EXAppViewController as a direct child of EXRootViewController (#15960)
[ios] Fix lint issues in Swift files (#15640)
[ios] New ExpoAppDelegate independent of singleton modules (#14867)
[iOS][Expo Go] Remove legacy screen orientation code (#14649)
[expo-manifests][android] Move factory into package (#14273)
[expo-manifests] Rename RawManifest -> Manifest (#14194)
[expo-updates] Factor out raw manifests into their own package (#14183)
[ios] Migrate all remaining native code
[actions] Run dogfooding home kernel publish before building client (#13960)
[ios] Use stable manifest ID where applicable (#13280)
[ios] Fix bug where we attempt to validate manifest instance rather than JSON as a JSON object (#13442)
[ios] Merge unimodules core and adapter into expo-modules-core (#13353)# Why Part of Expo modules re-architecture # How - Copied iOS sources from `@unimodules/core` and `@unimodules/react-
[ios] Merge unimodules core and adapter into expo-modules-core (#13353)# Why Part of Expo modules re-architecture # How - Copied iOS sources from `@unimodules/core` and `@unimodules/react-native-adapter` to `expo-modules-core` - In these copied files replaced `UM` prefix with `EX` - Swift names for classes used by the users (`AppDelegateWrapper`, `ModuleRegistry`, `ModuleRegistryAdapter`, `ModuleRegistryProvider`) won't have any prefix — we would drop these prefixes anyway, in the future when we rewrite them to Swift - Old `UM*` names are still supported and most of them are marked as deprecated, however I couldn't get it to work for Swift (but seems like no one uses it for app delegates?) and protocols - `ExpoModulesCore` provides `EXUnimodulesCompat.h` header that expands old `UM_*` macros to `EX_*` - Previously `ExpoModulesCore` depended upon `UMCore`, now it's the other way around — `UMReactNativeAdapter` and `UMCore` depend on `ExpoModulesCore` to import `EXUnimodulesCompat` header - Fixed `EXTrackingTransparency` to depend on `ExpoModulesCore` directly - _There are no changes in the logic or architecture of unimodules/expo modules, I'll do this separately_ # Test Plan - CI jobs are passing - Tested locally, apps seem to work as before
[go][ios][android] Fix recent project feature with new manifest wrappers (#12805)
[updates] Factor out raw manifest into wrapper class (#12631)
[Expo Go] Set iOS dev menu above LogBox (#12154)* set iOS dev menu above LogBox * Apply suggestions from code review
12345