[home] Fix tsc for expo-constants changes (#24312)# Why Types for classic manifests were removed in 50. This puts home in a weird state where it could still get classic updates but not have the
[home] Fix tsc for expo-constants changes (#24312)# Why Types for classic manifests were removed in 50. This puts home in a weird state where it could still get classic updates but not have the types for them. # How The fix that I applied here was just to design for EAS Update. In places that used to have special UI for classic updates, we now just show a generic UI. This is the lowest attention cost and is the fastest way forward (rather than reverting all the type changes and supporting classic manifest types for longer in the home app). # Test Plan `yarn tsc` # 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).
show more ...
[expo-go] Add expo.fyi link to home unverified badge (#23984)
[home] Make apollo client setup on login consistent with website (#23946)
[lint] Upgrade to Prettier v3, typescript-eslint to v6 (#23544)Why --- Prettier 3 is out. Add support for it with this linter config. **Note for reviewer:** the first commit is the one with th
[lint] Upgrade to Prettier v3, typescript-eslint to v6 (#23544)Why --- Prettier 3 is out. Add support for it with this linter config. **Note for reviewer:** the first commit is the one with the actual changes. The rest of this PR are changes to get the linter passing (mostly autofix). How --- Update eslint-config-prettier and eslint-plugin-prettier. To address deprecation warnings, also update typescript-eslint/parser and typescript-eslint/eslint-plugin. Because of an update to typescript-eslint/parser, we need to suppress deprecation warnings (documented in a comment). Regenerated test snapshots. Due to the upgraded dependencies, typecasts and optional chaining are now auto-fixable by lint. This converts warnings into autofixes. Test Plan --- `yarn test` in the linter config. Run `expotools check --all --fix-lint --no-build --no-test --no-uniformity-check` to try this config on the whole repo. --------- Co-authored-by: Expo Bot <[email protected]>
[go] fix android crash when returning back to home (#23435)# Why fixes #23393 close ENG-9266 # How the resolved promise result did matter on android because on native side, we will [conve
[go] fix android crash when returning back to home (#23435)# Why fixes #23393 close ENG-9266 # How the resolved promise result did matter on android because on native side, we will [convert the result to ReadableMap](https://github.com/expo/expo/blob/1d68edad21eea82cc9e30f5fbc0c2add9fdd9c06/android/expoview/src/main/java/host/exp/exponent/kernel/DevMenuManager.kt#L156). if we passing true, we will receive a java exception where boolean cannot convert to ReadableMap. this is a regression from #22219 # Test Plan test "go home" on expo-go
[home] Fix DevMenu onboarding height when loading a published update (#23148)# Why Brent noticed that when loading a published update in versioned Expo Go the Onboarding component is not fully
[home] Fix DevMenu onboarding height when loading a published update (#23148)# Why Brent noticed that when loading a published update in versioned Expo Go the Onboarding component is not fully visible and the user is not able to press "Continue" <img width="205" alt="image" src="https://github.com/expo/expo/assets/11707729/4cceb546-5554-4ee1-adce-083934a51e19"> # How This PR fixes this height calculation issue by conditionally rendering `DevMenuOnboarding` as position relative instead of just placing `DevMenuOnboarding` as a position absolute on top of everything. This also adds a padding bottom to the BottomSheet to respect the SafeAreaView insets of the device # Test Plan Run locally Expo Go versioned <table> <tr><th>Published update</th><th>Local bundle</th></tr> <tr> <td> <video src="https://github.com/expo/expo/assets/11707729/8d8acda6-876e-46be-94d7-2bed1ed58cd8"/> </td> <td> <video src="https://github.com/expo/expo/assets/11707729/d7638327-6be6-4fb4-8c7e-e6bd3596498a" /> </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).
[home] Better type dev menu, fix bugs, add verified indicator (#23059)
[go] Improve onboarding messaging (#23001)# Why Follow up PR of https://github.com/expo/expo/pull/22712 # How Update `home` DevMenu onboarding to look just like the new dev-client onboard
[go] Improve onboarding messaging (#23001)# Why Follow up PR of https://github.com/expo/expo/pull/22712 # How Update `home` DevMenu onboarding to look just like the new dev-client onboarding # Test Plan Run Expo Go unversioned on Android and iOS <table> <thead> <tr> <th></th> <th>Android</th> <th>iOS</th> </tr> </thead> <tbody> <tr> <th>Simulator</th> <td><img width="417" alt="image" src="https://github.com/expo/expo/assets/11707729/6b9e0179-2051-4997-9320-aeb79f229182"></td> <td><img width="417" alt="image" src="https://github.com/expo/expo/assets/11707729/3a97f47e-9680-477b-90b2-8f5f9ba363d3"></td> </tr> <tr> <th>Real Device</th> <td><img width="417" alt="image" src="https://github.com/expo/expo/assets/11707729/ec9c9cdb-24fa-473c-996e-dccd812b68ed"></td> <td><img width="417" alt="image" src="https://github.com/expo/expo/assets/11707729/7f12e156-cf3d-4b10-a6bd-242ef78b7fb2"></td> </tr> </tbody> </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). --------- Co-authored-by: Brent Vatne <[email protected]>
Rewrite bottom sheet (#22219)
[home] Simplify menu language (#20481)
Add manifest key to allow RTL in expo go experiences (#19634)Co-authored-by: Expo Bot <[email protected]> Co-authored-by: Łukasz Kosmaty <[email protected]> Co
Add manifest key to allow RTL in expo go experiences (#19634)Co-authored-by: Expo Bot <[email protected]> Co-authored-by: Łukasz Kosmaty <[email protected]> Co-authored-by: Tomasz Sapeta <[email protected]>
[home] use `isDevice` from expo-device package (#18431)
[home] optional chain manifest.extra accesses to prevent dev menu crashes (#18195)
[home] fix dev menu sdk version display (#18191)
Upgrade to react-native 0.69 (#18006)# Why for sdk 46 close ENG-5353 # How - update packages - react -> 18.0.0 - react-native -> 0.69.0 - react-dom -> 18.0.0 - react-native-w
Upgrade to react-native 0.69 (#18006)# Why for sdk 46 close ENG-5353 # How - update packages - react -> 18.0.0 - react-native -> 0.69.0 - react-dom -> 18.0.0 - react-native-web -> ~0.18.1 - react-test-renderer -> ~18.0.0 - @types/react -> ~18.0.14 - @types/react-native -> ~0.69.1 - early patch react-native for 0.69.1 fixes - https://github.com/facebook/react-native/commit/43f831b - https://github.com/facebook/react-native/commit/c2088e1 - https://github.com/facebook/react-native/commit/f97c6a5 - https://github.com/facebook/react-native/commit/79baca6 - https://github.com/facebook/react-native/pull/34064#issuecomment-1168810152 - migrate `expo-template-bare-minimum`, `bare-expo`, `bare-sandbox` to 0.69. reference from https://react-native-community.github.io/upgrade-helper/?from=0.68.1&to=0.69.0 - also remove the `hermesCommand` because 0.69 uses the builtin hermes-engine - `expo-av`, `expo-modules-core`, `expo-gl-cpp`: fix android cpp building errors, because 0.69 ships both release and debug aar - `expo-dev-client`: fix android build error from RedBox package rename - `html-elements`: update RNWView where react-native-web removed [the `css` import](https://github.com/necolas/react-native-web/commit/b27c9820) - `expo`: move Expo.podspec out from ios, because newer [rn-cli removed the `podspecPath` and `project` support](https://github.com/react-native-community/cli/commit/25eec7c#diff-0dddbcedebb33032fcac5991f3dcdfa44157e6ae87afcf3dabcd240a0db09832L58). - [ ] disable dev-client because the vendored reanimated in dev menu doesn't support 0.69 yet, e.g. `folly_json -> folly_runtime` - update reanimated and gesture-handler to latest for 0.69 support - `jest-expo`: update to [fix the deprecated react-native-web jest preset](https://github.com/necolas/react-native-web/commit/9b0c119) - `NCL`, `home`, patch `react-native-svg`: fix react 18 that [`children` should be explicitly added](https://reactjs.org/blog/2022/03/08/react-18-upgrade-guide.html#updates-to-typescript-definitions) - `@expo/cli` fix react-native-web and react-dom version checks # Test Plan - android bare-expo smoke test - ios bare-expo smoke test - ci passed - updates e2e is broken because in the flow the react-native doesn't include 0.69.1 fixes.
[home] update Expo Go dev menu design (#17315)* [home] update Expo Go dev menu design * publish dev home
[home] don't show projects section when logged out and change dev servers placeholder to be a sign in/up prompt (#16933)
[home] Get name from EAS Update Manifests to show in 'recently opened' section and dev menu (#16779)
[android][ios] Deprecate react-native-appearance (#16436)# Why react-native-appearance was deprecate from sdk 43. in this sdk cycle, we are going to deprecate sdk 42 as well. it's a good time to
[android][ios] Deprecate react-native-appearance (#16436)# Why react-native-appearance was deprecate from sdk 43. in this sdk cycle, we are going to deprecate sdk 42 as well. it's a good time to remove all react-native-appearance references. besides, it doesn't support gradle 7 where to break compile on react-native 0.66. # How - [android][ios] remove rnc-appearance unversioned native code - [ncl] migrate to react-native's appearance - [home] migrate to react-native's appearance - remove react-native-appearance from `bundledNativeModules.json` - [ncl] set `userInterfaceStyle` to `automatic` for appearance change testing. close ENG-2634 # Test Plan - ncl/home/dev-menu testing for dark/light mode changes Co-authored-by: Bartłomiej Bukowski <[email protected]>
[home] Fix home dev menu broken gesture controls (#15431)# Why for react-native-gesture-handler 2.0, native `RNGestureHandlerEnabledRootView` is deprecated in favor of `<GestureHandlerRootView /
[home] Fix home dev menu broken gesture controls (#15431)# Why for react-native-gesture-handler 2.0, native `RNGestureHandlerEnabledRootView` is deprecated in favor of `<GestureHandlerRootView />` component. i removed `RNGestureHandlerEnabledRootView` in https://github.com/expo/expo/pull/15404/files#diff-8577547e46982bd4a9595033ce80dc5047655e8a392fcb5d209db8a396241b55R9 but not adding the new component. that's why gesture is broken in expo go dev menu. # How - wrap home app components with `<GestureHandlerRootView />` - `et publish-dev-home` # Test Plan test expo go dev menu gesture functions
[home] fix lint issues (#14260)
[home] hotfix for home app (#14044)
[sdk] upgrade typescript to v4.3.5 (#14015)
[home] More typescript cleanup and types (#12975)
[home] Fix icon types
123