feat(expo)!: drop logging endpoint (#18596)

# Why

- In the new versioned CLI we don't support the logging endpoint,
instead favoring the logging WebSocket setup by `metro-runtime`.
- Dropping s

feat(expo)!: drop logging endpoint (#18596)

# Why

- In the new versioned CLI we don't support the logging endpoint,
instead favoring the logging WebSocket setup by `metro-runtime`.
- Dropping support for `logUrl` will break logging in the legacy
`expo-cli start` command, no logs will show up.
- Drop `Logs` module: `import { Logs } from 'expo';`.
- Drop stack trace filter that removes `react-native-logging.fx` since
we no longer need it.
- Also removes the "temporary workaround"s from 2018 that filter out
warnings from the lottie package.
- Drop direct dependency on `invariant`, `pretty-format`, `fbemitter`

> This doesn't add breaking changes to the local Expo CLI, only the
deprecated global CLI.

# Test Plan

- Copied the JS expo files into a new project and websockets continued
to send logs.

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

---------

Co-authored-by: Expo Bot <[email protected]>

show more ...

[expo-manifests] Fix error in handling nested array (#23562)

# Why

Fix crash on iOS if a plugin is passed in as an array, but with only the
name element and not the props element.

Also fix co

[expo-manifests] Fix error in handling nested array (#23562)

# Why

Fix crash on iOS if a plugin is passed in as an array, but with only the
name element and not the props element.

Also fix corresponding code on Android, where an exception is thrown.

Fixes #23549.

# How

Modified `Manifest.swift` and `Manifest.kt` to handle the above case
correctly.

# Test Plan

- Tested with Expo Go and the project provided in the above issue
- New unit tests for both iOS and Android

# Checklist

- [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 `npx expo prebuild` & EAS Build
(eg: updated a module plugin).

show more ...