[dev-launcher] Launch directly into previously opened project (#24614)

# Why

Closes ENG-10041

# How

In order to allow users to launch directly into previously opened
projects, this PR upda

[dev-launcher] Launch directly into previously opened project (#24614)

# Why

Closes ENG-10041

# How

In order to allow users to launch directly into previously opened
projects, this PR updates `startWithWindow` and `handleIntent` to try to
launch from the most recent URL of the RecentlyOpenedAppsRegistry. If
the bundle cannot be loaded, it falls back to the regular launcher.

This also refactors the existing dev-client and dev-launcher config
plugins adding a new `tryToLaunchLastOpenedBundle` parameter to the
Android and iOS plugin config types.

E.g.

```json
"plugins": [
[
"expo-dev-client",
{
"android": {
"tryToLaunchLastOpenedBundle": true
},
"ios": {
"tryToLaunchLastOpenedBundle": true
}
}
]
]
```

# Test Plan

Run dev-client through bare-expo on Android and iOS testing opening the
app directly, with and without "Recent Apps" and opening through deep
links

# Checklist


- [ ] 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: Łukasz Kosmaty <[email protected]>

show more ...

[android] Remove unnecessary version checks (#24203)

# Why

This PR is related to #24201, it removes unnecessary version checks

# How

Remove version check logic for SDK's < 23

# Test Pla

[android] Remove unnecessary version checks (#24203)

# Why

This PR is related to #24201, it removes unnecessary version checks

# How

Remove version check logic for SDK's < 23

# Test Plan

Tested in Bare Expo in Android 13 simulator

show more ...

[dev-launcher] Fix useFocusEffect import (#24502)

# Why

Last week while releasing dev-launcher v2.4.11 from the `sdk-49` branch
we encountered this instacrash when using dev-launcher.


![ima

[dev-launcher] Fix useFocusEffect import (#24502)

# Why

Last week while releasing dev-launcher v2.4.11 from the `sdk-49` branch
we encountered this instacrash when using dev-launcher.



> Error: Couldn't find a navigation object. Is your component inside
NavigationContainer?


This error does not happen on `main`, which makes me think that this
could be related to a different version being resolved by yarn
workspaces?

# How

Updating the `useFocusEffect` import from `@react-navigation/core` to
`@react-navigation/native` fixes this issues on both branches

# Test Plan

Run dev-client through bare-expo on `main` and `sdk-49` (cherry-picked
this commit) branches
<img width="537" alt="image"
src="https://github.com/expo/expo/assets/11707729/055aa706-8e30-4668-ab55-058b9bc1f03a">


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

[core] Add native functions for UUIDv4 generation (#24199)

# Why

For Android and iOS we want to use native UUIDv4 generation methods.

# How

Exposed the common methods using the `CoreModule`

[core] Add native functions for UUIDv4 generation (#24199)

# Why

For Android and iOS we want to use native UUIDv4 generation methods.

# How

Exposed the common methods using the `CoreModule` file.
Changed the way uuids are exported. Now `expo-modules-core` exports a
`uuid` object which contains `v4` function.

# Test Plan

Tested in BareExpo on Android, ios and web

show more ...

[dev-launcher] Fetch dev sessions whenever navigating to Home screen (#24378)

# Why

Closes ENG-10047

# How

Update dev-launcher `HomeScreen` to fetch dev sessions on focus if the
list of se

[dev-launcher] Fetch dev sessions whenever navigating to Home screen (#24378)

# Why

Closes ENG-10047

# How

Update dev-launcher `HomeScreen` to fetch dev sessions on focus if the
list of sessions is empty

# Test Plan

Run `dev-client` locally on iOS and Android through bare-expo

# 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: Expo Bot <[email protected]>

show more ...

[dev-launcher] Update dev session default ports to check (#24380)

# Why

Closes ENG-10063

# How

Update default ports to `[8081, 8082, 8083, 8084, 8085, 19000, 19001,
19002]`

# Test Plan

[dev-launcher] Update dev session default ports to check (#24380)

# Why

Closes ENG-10063

# How

Update default ports to `[8081, 8082, 8083, 8084, 8085, 19000, 19001,
19002]`

# Test Plan

Run `dev-client` locally on iOS and Android through bare-expo

# 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: Expo Bot <[email protected]>

show more ...

Update JS bundles in expo-dev-launcher

fix(expo, asset, cli)!: unify asset hashing (#24090)

# Why

Convert the `../` segments of the server URL to `_` to support
monorepos. This same transformation takes place in
`AssetSourceResolver

fix(expo, asset, cli)!: unify asset hashing (#24090)

# Why

Convert the `../` segments of the server URL to `_` to support
monorepos. This same transformation takes place in
`AssetSourceResolver.web` (expo-assets, expo-image) and
`persistMetroAssets` of Expo CLI, this originally came from the [Metro
opinion](https://github.com/react-native-community/cli/blob/2204d357379e2067cebe2791e90388f7e97fc5f5/packages/cli-plugin-metro/src/commands/bundle/getAssetDestPathIOS.ts#L19C5-L19C10).

The purpose is to ensure no URL like `/foo/../bar.png` is requested, as
the result would be `/bar.png` which wouldn't work. The of how to handle
this didn't come from us, but we do need to ensure it's unified. At a
high-level, this does prevent the usage of certain files, as
`/foo/../bar.png` will be `/foo/_bar.png`, meaning a file named
`/foo/_bar.png` cannot also exist. This logic, while applied at runtime,
is actually only valid for production exports as we don't move or alias
files in development. The only way to have valid development files is to
ensure `../` never appears in the URL, i.e. by using
`unstable_serverRoot`.

- Drop legacy `expo/tools/hashAssetFiles.js` in favor of `expo-asset`
version.
- Unify runtime logic of asset file loading for monorepos.
- Split out of https://github.com/expo/expo/pull/23911

<!--
Please describe the motivation for this PR, and link to relevant GitHub
issues, forums posts, or feature requests.
-->

# How

<!--
How did you build this feature or fix this bug and why?
-->

# Test Plan

<!--
Please describe how you tested this change and how a reviewer could
reproduce your test, especially if this PR does not include automated
tests! If possible, please also provide terminal output and/or
screenshots demonstrating your test/reproduction.
-->

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

chore: update react-native to 0.72.4 (#24044)

close ENG-9814

- update react-native to 0.72.4
- [react-native-lab] cherry pick native changes
- [babel-preset-expo] bump `metro-react-native-babel-pre

chore: update react-native to 0.72.4 (#24044)

close ENG-9814

- update react-native to 0.72.4
- [react-native-lab] cherry pick native changes
- [babel-preset-expo] bump `[email protected]`
- [android][ios] re-version sdk-49 code
- [dev-menu][dev-launcher] rebuild js bundles

versioned expo go + sdk 49 project smoke test

show more ...

[packages] fix react-native 0.73 compatibility [1/3] (#24018)

# Why

fix react-native 0.73 compatibility. these are for AGP 8 support - https://github.com/react-native-community/discussions-and-pr

[packages] fix react-native 0.73 compatibility [1/3] (#24018)

# Why

fix react-native 0.73 compatibility. these are for AGP 8 support - https://github.com/react-native-community/discussions-and-proposals/issues/671#issuecomment-1677632448

# How

- [packages][bare-expo] set jvm version only if AGP < 8
- [av][dev-launcher] fix AGP 8 non transitive R issue
- [dev-client][dev-launcher][dev-menu][core][notifications] fix AGP 8 non default buildConfig issue

# Test Plan

ci passed in #23961 (https://github.com/expo/expo/pull/23961/checks)

show more ...