[ios] Remove legacy notifications module code (#24325)

[iOS] Refactor version manager in Expo Go (#23624)

[dev-client][updates] fix ios use_frameworks build errors (#23218)

# Why

fix ios use_frameworks with expo-dev-client and expo-updates
fixes #23190
close ENG-9158

# How

- [dev-launcher][d

[dev-client][updates] fix ios use_frameworks build errors (#23218)

# Why

fix ios use_frameworks with expo-dev-client and expo-updates
fixes #23190
close ENG-9158

# How

- [dev-launcher][dev-menu] remove bridging headers. bridging headers are only supported in app projects as far as i know.
- [dev-launcher][dev-menu] remove double quoted imports
- [manifests][updates-interface] remove the swift generated header copying to PODS_ROOT. if we did that, xcode will have ambiguous imports that import from non-module header.

# Test Plan

- ci passed
- versioned expo go
- bare-expo
- sdk49 project + use_frameworks! static

show more ...

[cli][dev-menu][go] add react devtools (#21462)

# Why

close ENG-7468
close ENG-7469

# How

- [cli] add websocket proxy to forward react-devtools events.
- [cli] add static page for react-d

[cli][dev-menu][go] add react devtools (#21462)

# Why

close ENG-7468
close ENG-7469

# How

- [cli] add websocket proxy to forward react-devtools events.
- [cli] add static page for react-devtools frontend. since react-devtools only ships commonjs format, this pr tries to use jspm to support it on browsers.
- [dev-menu][go] listen `reconnectDevTools` metro websocket event and send `RCTDevMenuShown` to js for app to reconnect devtools websocket

# Test Plan

manual test only. please let me know if there's any proper points to add unit tests

show more ...

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

[android][ios] Integrate JS inspector on Expo Go (#19175)

# Why

close ENG-4165

# How

- if the underlying js runtime is inspectable, show the dev menu as "Open JS Debugger" and open inspecto

[android][ios] Integrate JS inspector on Expo Go (#19175)

# Why

close ENG-4165

# How

- if the underlying js runtime is inspectable, show the dev menu as "Open JS Debugger" and open inspector provided by expo cli.
- on android, there's a workaround for checking js runtime isInspectable. because react-native doesn't expose the information from jsi runtime to java side, we could only check the underlying js executor name if it's hermes or not.

# Test Plan

- ✅ unversioned android/ios expo go + NCL (remote debugging)
- ✅ unversioned android/ios expo go + NCL jsEngine hermes (js inspector)
- ✅ unversioned android/ios expo go + NCL jsEngine hermes + tunnel (js inspector)

Co-authored-by: Łukasz Kosmaty <[email protected]>

show more ...

[iOS][Expo Go] Remove legacy splash screen code (#14650)

[iOS][Expo Go] Remove legacy code (#14690)

[Expo Go][iOS] Catch invalid manifest assertions better (#14404)

* Catch invalid manifest assertions

* Added catches for more fatal loading errors

* assert early

* Catch manifest parsing er

[Expo Go][iOS] Catch invalid manifest assertions better (#14404)

* Catch invalid manifest assertions

* Added catches for more fatal loading errors

* assert early

* Catch manifest parsing errors

* Remove unused assertion

* backdate changes

Co-authored-by: Evan Bacon <[email protected]>

show more ...

[expo-manifests] Rename RawManifest -> Manifest (#14194)

[expo-updates] Factor out raw manifests into their own package (#14183)

[ios] Migrate all remaining native code

[ios] Use stable manifest ID where applicable (#13280)

[ios] Fix second instance of manifest JSON bug (#13443)

[ios] Replace clang's `typeof` with `__typeof`

[go][ios][android] Fix recent project feature with new manifest wrappers (#12805)

[updates] Factor out raw manifest into wrapper class (#12631)

[ios] Don't call RCTPackagerConnection when it isn't available (related: 5026ff91)

[ios][Expo Go] fix web socket versioning (#12286)

[Expo Go][iOS] Added web socket controls for the CLI (#12151)

* Added websocket controls for the CLI

* Added more commands

[Android][fix] Remove JSONBundleConverter usage for passing manifest from Android to JS (#11678)

# Why

`Expo Go` is unable to load any project on Android now.
Recent change in app manifest shape

[Android][fix] Remove JSONBundleConverter usage for passing manifest from Android to JS (#11678)

# Why

`Expo Go` is unable to load any project on Android now.
Recent change in app manifest shape is responsible for that, namely, new `config plugin system` (for `ncl` project this file: https://github.com/expo/expo/blob/master/apps/native-component-list/app.config.js is adding some array with strings/objects alternately).
That is causing https://github.com/expo/expo/blob/fec8b1534e8d27584a685c01a3a12ff432b3fbbd/android/expoview/src/main/java/host/exp/exponent/utils/JSONBundleConverter.java#L72-L81 to throw an error.

# How

There's no way to convert `JSONArray` with different entries to `Bundle` data type as the latter does not allow arrays/lists containing different data types, only homogenous entries are allowed.
I've removed this conversion altogether and replaced all `<someBundle>.putBundle("manifest", JSONBundleConverter.JSONToBundle(manifest))` with `<someBundle>.putString("manifest" manifest.toString())`.
I've tried to find any place in the code that would read the `"manifest"` fields from the bundle, but failed to do so �� cc @lukmccall, as there are changes in the `DevMenu` module.

From now on, `manifest` field in `initialProps` is replaced by `manifestString` that has to be deserialised upon access. Fortunately this field is not used anywhere in our codebase.

# Test Plan

- [x] I've succeeded in launching `ncl` and `test-suite` again on Android and observed no regressions.
- [x] I've checked that DevMenu shows all the things in the header properly.
- [x] I've checked both Android & iOS behaviours.

show more ...

[expo-constants] add executionEnvironment (#10986)

[ios] ensure ErrorRecoveryManager/Kernel can handle nil experienceId (#10918)

[LoadingBar][iOS] Hide LoadingBar once the JS is fully downloaded (#10450)