[config-plugins][config-types] align with server schema and fix errors (#24430)

# Why

- Align with schema changes (add `supportsTVOnly`)
- Fix test snapshots in `config-plugins`

# How

```

[config-plugins][config-types] align with server schema and fix errors (#24430)

# Why

- Align with schema changes (add `supportsTVOnly`)
- Fix test snapshots in `config-plugins`

# How

```
cd packages/\@expo/config-types
yarn generate --path ../../../../../easProjects/universe/server/www/xdl-schemas/UNVERSIONED-schema.json
npx prettier --write src/ExpoConfig.ts
```

Then fix tests in `config-plugins`.

# Test Plan

Existing tests should pass

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

show more ...

[expo-updates] Add fingerprintExperimental runtime version policy (#24126)

# Why

Manually handling runtimeVersions is a big pain for projects that uses
native modules. This PR adds a new runtime

[expo-updates] Add fingerprintExperimental runtime version policy (#24126)

# Why

Manually handling runtimeVersions is a big pain for projects that uses
native modules. This PR adds a new runtime policy that handles this
automatically.

See:

https://discord.com/channels/695411232856997968/1142023605908156476/1142023605908156476

# How

Using
[expo-fingerprint](https://github.com/expo/expo/tree/main/packages/@expo/fingerprint#readme)
to auto-generate a hash for the project.

# Test Plan

I made the changes locally on a working project and the build was
successfully with expo prebuild. I checked the native files and the
runtime version was set to the project hash.

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

---------

Co-authored-by: Expo Bot <[email protected]>
Co-authored-by: Aman Mittal <[email protected]>
Co-authored-by: Kudo Chien <[email protected]>
Co-authored-by: Douglas Lowder <[email protected]>

show more ...

[config-types] Remove classic updates (#24066)

[config-types] Pull in latest

chore(cli, docs): update typed routes (#22848)

# Why

I keep getting DMs about this feature being confusing so I'm doing a
pass to try and bring it to parity with the rest of our offering.

<!-

chore(cli, docs): update typed routes (#22848)

# Why

I keep getting DMs about this feature being confusing so I'm doing a
pass to try and bring it to parity with the rest of our offering.

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

# How

- Update the experimental docs to not be a general "TypeScript" guide
but rather, be focused on the "Typed Routes" feature.
- Use the new `experiments.typedRoutes` flag and not an environment
variable. https://github.com/expo/universe/pull/12590
- Drop flag misinfo in the Expo CLI docs "This includes support for the
network inspector."
- Add a slightly more e2e test for the side-effects.
- Document how to actually turn the feature on.

---------

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

show more ...

update scheme property to use array (#22324)

# Why

ENG-8466

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

#

update scheme property to use array (#22324)

# Why

ENG-8466

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

Update ExpoConfig.ts (#22317)

# Why

https://github.com/expo/universe/pull/12244
<!--
Please describe the motivation for this PR, and link to relevant GitHub
issues, forums posts, or feature re

Update ExpoConfig.ts (#22317)

# Why

https://github.com/expo/universe/pull/12244
<!--
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 ...

[config-plugins][updates] Add support for config.updates.useClassicUpdates defaulting behavior (#22169)

[config-types][config-plugins] additional values for updates.checkAutomatically (#22119)

[constants] Remove references to Constants.manifest (#22070)

chore(cli): switch `EXPO_USE_PATH_ALIASES` to `expo.experiments.tsconfigPaths`. (#21897)

# Why

- It's a bit harder to set env vars and users will want this either
always on or always off.
- Exp

chore(cli): switch `EXPO_USE_PATH_ALIASES` to `expo.experiments.tsconfigPaths`. (#21897)

# Why

- It's a bit harder to set env vars and users will want this either
always on or always off.
- Expo Config makes it easier to deprecate values on a per-version
basis. https://github.com/expo/universe/pull/11872
- Comment out references to the path aliases feature until we're closer
to launch. Users are getting confused when they see the feature
documented.

---------

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

show more ...

[docs] Remove classic build references in app config schema & sync changes to docs (#21230)

[docs] Update Hermes guide to state that Hermes is the new default engine (#21047)

# Why

Follow up of https://github.com/expo/expo/pull/21001
Closes [ENG-7163](https://linear.app/expo/issue/ENG-

[docs] Update Hermes guide to state that Hermes is the new default engine (#21047)

# Why

Follow up of https://github.com/expo/expo/pull/21001
Closes [ENG-7163](https://linear.app/expo/issue/ENG-7163)

# How

Update `Using Hermes Engine` guide to state that Hermes is the new
default engine, aligns `ExpoConfig` types and app-config schema with the
server

```sh
# inside packages/@expo/config-types/
yarn generate --path
/../../../../../../universe/server/www/xdl-schemas/UNVERSIONED-schema.json
# inside docs/
yarn run schema-sync unversioned
```

# Test Plan

N / A

# 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).
- [ ] 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: Aman Mittal <[email protected]>

show more ...

refactor: remove deprecated facebook types and plugins (#21018)

# Why

Fixes ENG-7363

# How

Removed all plugins and types for `expo-facebook` and
`expo-ads-facebook`.

# Test Plan

Make

refactor: remove deprecated facebook types and plugins (#21018)

# Why

Fixes ENG-7363

# How

Removed all plugins and types for `expo-facebook` and
`expo-ads-facebook`.

# Test Plan

Make sure CI passes, everything should be buildable and all tests should
pass.

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

feat(config)!: Remove support for `expo.entryPoint` (#20891)

# Why

- Follow up https://github.com/expo/universe/pull/11265
- `entryPoint` (and `package.json` `main`) do not work.

Co-authored-

feat(config)!: Remove support for `expo.entryPoint` (#20891)

# Why

- Follow up https://github.com/expo/universe/pull/11265
- `entryPoint` (and `package.json` `main`) do not work.

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

show more ...

[config-plugins][config-types] align with server schema (#20895)

# Why

Follow up of https://github.com/expo/universe/pull/11245

Closes ENG-4613

# How

This PR Aligns `ExpoConfig` types an

[config-plugins][config-types] align with server schema (#20895)

# Why

Follow up of https://github.com/expo/universe/pull/11245

Closes ENG-4613

# How

This PR Aligns `ExpoConfig` types and app-config schema with the server

```sh
# inside packages/@expo/config-types/
yarn generate --path
/../../../../../../universe/server/www/xdl-schemas/UNVERSIONED-schema.json
# inside docs/
yarn run schema-sync unversioned
```

# Test Plan

Tests should pass

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

[config-plugins][config-types] align with server schema and fix errors (#20378)

# Why

- Align with schema changes
- Make corresponding changes in `config-plugins`

# How

```
cd packages/\@

[config-plugins][config-types] align with server schema and fix errors (#20378)

# Why

- Align with schema changes
- Make corresponding changes in `config-plugins`

# How

```
cd packages/\@expo/config-types
yarn generate --path ../../../../../easProjects/universe/server/www/xdl-schemas/UNVERSIONED-schema.json
npx prettier --write src/ExpoConfig.ts
```

Then fix outdated tests in `config-plugins`.

# Test Plan

Tests should pass

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

[config-types] Restore missing requestHeader property (#20373)

# Why

Fix breakages from #20287

# How

- Restore the `requestHeaders` property from the `updates` section of
config-types
-

[config-types] Restore missing requestHeader property (#20373)

# Why

Fix breakages from #20287

# How

- Restore the `requestHeaders` property from the `updates` section of
config-types
- Restore `googleSignIn` temporarily until `@expo/config-plugins` is
fixed to remove a remaining dependency on this property

# Test Plan

Execute

```
cd packages/\@expo/config-plugins
yarn build
```
and no errors relating to these properties should appear.

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

chore(config-types): update (#20287)

```
config-types �� yarn generate --path ../../../../universe/server/www/xdl-schemas/UNVERSIONED-schema.json
```

Add Support For monochrome Android Adaptive Icons (#20074)

# Why

In Android 13, Android added the ability to include a monochrome
adaptive icon that will be themed to the OS theme color.

# Ho

Add Support For monochrome Android Adaptive Icons (#20074)

# Why

In Android 13, Android added the ability to include a monochrome
adaptive icon that will be themed to the OS theme color.

# How

I added this to the already-included Adaptive Icon config, as Android
includes it in their [Adaptive Icon
docs](https://developer.android.com/develop/ui/views/launch/icon_design_adaptive#design-adaptive-icons).

# Test Plan

Tests written (mostly copied from other image tests).

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

# Notes

I am unsure why the rest of the files changed when I built again. I only
changed two source files.

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

show more ...

Add requestHeaders option in app.js to avoid issues with expo prebuild when using release channels outside EAS build (#18737)

# Why

On the documentation
[https://docs.expo.dev/bare/updating-your

Add requestHeaders option in app.js to avoid issues with expo prebuild when using release channels outside EAS build (#18737)

# Why

On the documentation
[https://docs.expo.dev/bare/updating-your-app/](https://docs.expo.dev/bare/updating-your-app/)
is stated that you can configura the release channel manually by adding
`expo.modules.updates.UPDATES_CONFIGURATION_REQUEST_HEADERS_KEY` or
`EXUpdatesRequestHeaders` in their respective places.

However, `expo prebuild` does not consider this option resulting in
missing or removed release channel configuration.

The proposed solution introduces a new configuration option in app.json
updates section called `requestHeaders` that allows to handle this
configuration automatically, just like `codeSigningMetadata`.

# How

I followed precisely how `codeSigningMetadata` option is implemented
(styles, names, etc) and modified:

`packages/@expo/config-types/src/ExpoConfig.ts`
Added `requestHeaders` option under updates in order to update the
schema

`packages/@expo/config-plugins`
I updated iOS and Android Updates.ts and added the relative helpers and
tests, closely follwing how `codeSigningMetadata` was implemented

It is possible now to add the updates request headers directly in
`app.json` and have `expo prebuild` handle this configuration
automatically.

# Test Plan

I have included the relative tests following the behavior of
`codeSigningMetadata` option.
I have also tested on a real project by copying the builds of
config-plugins in the node_modules folder.



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

NOTE: I have updated the relevant documentation page
`docs/pages/bare/updating-your-app.md` but not the `app.json /
app.config.js` as I thought adding instructions to add release channel
information in app.js may confuse managed expo users.

Co-authored-by: Will Schurman <[email protected]>
Co-authored-by: Douglas Lowder <[email protected]>
Co-authored-by: Bartosz Kaszubowski <[email protected]>
Co-authored-by: Douglas Lowder <[email protected]>

show more ...

feat(config-plugins): add `appVersion` runtime policy (#18398)

[config-types] Update for SDK 46 [skip ci]

chore: migrate config, config-plugins, config-types, prebuild-config (#17958)