[tools] Switch expo home publishing to EAS update (#24216)

[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

show more ...

[home][iOS] Fix SafeAreaView height after opening web browser (#23164)

# Why

Closes ENG-9124

Originally we switched to using the react-native `SafeAreaView` in order
to fix a brief layout fla

[home][iOS] Fix SafeAreaView height after opening web browser (#23164)

# Why

Closes ENG-9124

Originally we switched to using the react-native `SafeAreaView` in order
to fix a brief layout flash when launching the app on iOS
(https://github.com/expo/expo/pull/21310), but this introduced another
issue when opening 2 nested modals.

# How

This PR replaces the SafeAreaView used on the Expo Go home screen to use
the `useSafeAreaInsets` hook from `react-native-safe-area-context`. The
main reason for using the `useSafeAreaInsets` hook directly instead of
the SafeAreaView component from `react-native-safe-area-context` is that
as stated on the ([React Navigation
Docs](https://reactnavigation.org/docs/handling-safe-area/)) using
SafeAreaView may cause a jumpy behavior.


# Test Plan

Run Expo Go Versioned



<video
src="https://github.com/expo/expo/assets/11707729/c3dd9eb9-5e0e-4944-87d6-eacb453f9817"
/>


# 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 ...

[home] Publish dev and prod home

[home] Publish dev and prod home

[go] update react-native-reanimated to 3.3.0 (#22907)

# Why

update vendoring modules for sdk 49

# How

- `et uvm -m react-native-reanimated -c 3.3.0`
- publish dev home because prebuilt hom

[go] update react-native-reanimated to 3.3.0 (#22907)

# Why

update vendoring modules for sdk 49

# How

- `et uvm -m react-native-reanimated -c 3.3.0`
- publish dev home because prebuilt home still uses reanimated 3.1.0

# Test Plan

unversioned expo go + ncl reanimated

show more ...

[ios][android] Update react-native-svg to 13.9.0 (#22934)

[home][ncl] fix loading or exporting bundles (#22841)

# Why

fix the following errors when publishing dev home

```
Error: Cannot find module '/Users/kudo/expo/expo/react-native-lab/react-nativ

[home][ncl] fix loading or exporting bundles (#22841)

# Why

fix the following errors when publishing dev home

```
Error: Cannot find module '/Users/kudo/expo/expo/react-native-lab/react-native/rn-get-polyfills'
Require stack:
- /Users/kudo/expo/expo/home/metro.config.js
- /Users/kudo/expo/expo/node_modules/cosmiconfig/node_modules/import-fresh/index.js
- /Users/kudo/expo/expo/node_modules/cosmiconfig/dist/loaders.js
- /Users/kudo/expo/expo/node_modules/cosmiconfig/dist/createExplorer.js
- /Users/kudo/expo/expo/node_modules/cosmiconfig/dist/index.js
- /Users/kudo/expo/expo/node_modules/metro-config/src/loadConfig.js
- /Users/kudo/expo/expo/node_modules/metro-config/src/index.js
- /Users/kudo/expo/expo/node_modules/metro/src/commands/build.js
- /Users/kudo/expo/expo/node_modules/metro/src/index.flow.js
- /Users/kudo/expo/expo/node_modules/metro/src/index.js
- /Users/kudo/expo/expo/packages/@expo/dev-server/build/metro/importMetroFromProject.js
- /Users/kudo/expo/expo/packages/@expo/cli/build/src/export/fork-bundleAsync.js
- /Users/kudo/expo/expo/packages/@expo/cli/build/src/export/createBundles.js
- /Users/kudo/expo/expo/packages/@expo/cli/build/src/export/exportApp.js
- /Users/kudo/expo/expo/packages/@expo/cli/build/src/export/exportAsync.js
- /Users/kudo/expo/expo/packages/@expo/cli/build/src/export/index.js
- /Users/kudo/expo/expo/packages/@expo/cli/build/bin/cli
```

# How

- since the react-native monorepo changes, we should use the `react-native-lab/react-native/packages/react-native` as root.
- republish dev home

# Test Plan

- unversioned expo go + ncl

show more ...

Upgrade vendored reanimated to 3.1.0 (#22570)

Update dev-home-config with reanimated 3 and no amplitude expo go (#22541)

[home] Fix SafeAreaView brief layout flash (#21310)

# Why

Closes ENG-7608

This is one of the classic problems with
`react-native-safe-area-context`, sometimes during the first mount of a
Saf

[home] Fix SafeAreaView brief layout flash (#21310)

# Why

Closes ENG-7608

This is one of the classic problems with
`react-native-safe-area-context`, sometimes during the first mount of a
SafeAreaView, the insets are not populated correctly.

# How

This PR replaces the `SafeAreaView` used on the Expo Go home screen to
use the component from `react-native` instead of
`react-native-safe-area-context`

# Test Plan

<table>
<tr><th>After</th><th>Before</th></tr>
<tr>
<td>
<video
src="https://user-images.githubusercontent.com/11707729/220131398-99a52509-97fd-45ea-8b17-8a94554c889a.mov"
/>
</td>
<td>
<video
src="https://user-images.githubusercontent.com/11707729/220135027-5be9269d-d37a-4db4-a978-16aa563effad.mov"
/>
</td>
</tr>
<tr>
<td>
<video
src="https://user-images.githubusercontent.com/11707729/220134838-5e636c9b-87cf-4e7b-89fb-34763c72f09a.mov"
/>
</td>
<td>
<video
src="https://user-images.githubusercontent.com/11707729/220135212-85b7ca46-627f-4fdd-9227-c30bb992caeb.mov"
/>
</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 `expo prebuild` & EAS Build (eg:
updated a module plugin).

show more ...

[go] Publish dev home

[home] publish dev home in hermes bytecode bundle format

[home] remove InfiniteScrollView and use FlatList-native infinite scroll props (#20914)

# Why

`InfiniteScrollView` is a legacy module from when Expo Go used
`ListView`, which didn't have props f

[home] remove InfiniteScrollView and use FlatList-native infinite scroll props (#20914)

# Why

`InfiniteScrollView` is a legacy module from when Expo Go used
`ListView`, which didn't have props for detecting end-of-list position
for infinite scrolling purposes. We want to remove that module in this
SDK release.

# How

Since we were already using `FlatList`, it was easy to simply remove
`InfiniteScrollView` and use the `FlatList` props that serve our
purposes.

On top of replacing `InfiniteScrollView` prop usage, I followed the
warnings in Apollo Client telling me that `updateQuery` is deprecated in
favor of `typePolicies`, so I used their pagination helpers to achieve
the same effect cache updating effect we had before.

# Test Plan

I opened the projects and snacks lists in Expo Go with this code running
locally to make sure lists updated correctly and there were no more
Apollo client warnings:


https://user-images.githubusercontent.com/12488826/213896603-09b11640-c417-4f3b-9078-1af50da54979.mov

I don't have any projects with enough branches to paginate, but it
should behave the same as the other two lists.

show more ...

Publish dev home to fix barcode scanner

[home] Republish dev-home to fix v.current.useMemo null issue [skip ci]

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]>

show more ...

[home] Publish dev and prod home [skip ci]

Update dev home [skip ci]

[iOS][Android] Update `react-native-svg` to `13.4.0` (#19434)

# Why

Closes ENG-6532.

# How

Run:
```
et uvm -m react-native-svg
```

> Note:
This version of SVG requires a new version

[iOS][Android] Update `react-native-svg` to `13.4.0` (#19434)

# Why

Closes ENG-6532.

# How

Run:
```
et uvm -m react-native-svg
```

> Note:
This version of SVG requires a new version of the home app. It will be created later because I faced other problems with the home app - see https://github.com/expo/expo/pull/19495



# Test Plan

- home - android, ios ✅
- NCL - android, ios ✅

show more ...

[home] publish dev home to apply expo-camera fix from #18946

[home] make outdated classic update warning more informative (#18790)

* [home] make outdated classic update warning more informative

* Update home/screens/ProjectScreen/LegacyLaunchSection.tsx

[home] make outdated classic update warning more informative (#18790)

* [home] make outdated classic update warning more informative

* Update home/screens/ProjectScreen/LegacyLaunchSection.tsx

Co-authored-by: Jon Samp <[email protected]>

Co-authored-by: Jon Samp <[email protected]>

show more ...

[home] don't use cached responses on home screen, fix broken useCallbacks (#18337)

[home] Publish dev and prod for SDK 46 [skip ci]

[home] Publish dev-home

The previous dev home is not for sdk 46.
Tested via
`curl 'https://exp.host/@expo-home-dev/expo-home-dev-9fa8ed7fbb5f9904f7af54c7d06f86ce1698ef16/index.exp?platform=ios&sdkVe

[home] Publish dev-home

The previous dev home is not for sdk 46.
Tested via
`curl 'https://exp.host/@expo-home-dev/expo-home-dev-9fa8ed7fbb5f9904f7af54c7d06f86ce1698ef16/index.exp?platform=ios&sdkVersion=46.0.0'`

show more ...