[expo-updates] fix reloadAsync() when isUsingExpoDevelopmentClient=true (#24588)

# Why

Fix a regression created in #21253 . After that change, `reloadAsync()`
would throw if called from a dev cl

[expo-updates] fix reloadAsync() when isUsingExpoDevelopmentClient=true (#24588)

# Why

Fix a regression created in #21253 . After that change, `reloadAsync()`
would throw if called from a dev client build.

Once this is merged, it should be cherry picked to sdk-49 branch.

# How

Fix the regression. See discussion at
https://github.com/expo/expo/pull/21253#discussion_r1329961204

# Test Plan

- CI should pass
- Customers report that this change fixes the issue

# 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 missing export in checkForUpdateAsync result (#24503)

# Why

In testing with the launch week demo app (UpdatesAPIDemo), found that
the new "reason" enum was not exported in `Up

[expo-updates] Add missing export in checkForUpdateAsync result (#24503)

# Why

In testing with the launch week demo app (UpdatesAPIDemo), found that
the new "reason" enum was not exported in `Updates.types.ts`.

# How

- Added the export
- Regenerated API docs

# Test Plan

- New enum is accessible from demo app code
- Check generated docs in local server

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

---------

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

show more ...

[expo-updates] Prevent failed updates in checkForUpdateAsync() (#24112)

# Why

If an update has a launch failure, our startup code detects the problem
and launches the previous update or the embe

[expo-updates] Prevent failed updates in checkForUpdateAsync() (#24112)

# Why

If an update has a launch failure, our startup code detects the problem
and launches the previous update or the embedded bundle instead. On
future restarts of the app, the failed update will be ignored.

However, the JS API (checkForUpdateAsync()) does not do the same check,
as it is not running the full startup flow that includes an attempt at
launch.

# How

If a new update is detected in checkForUpdateAsync(), we now search for
it in the DB to see if it is already there, and if so, execute
`shouldLaunchNewUpdate()` against that. Launch failures will cause this
method to return false, and the update will be ignored as expected.

In order for developers to know when this occurs, this PR includes a
change to the `UpdateCheckResult` type returned by
`checkForUpdateAsync()`. A new optional `reason` property is now
included in the result, so that this and other possible conditions are
surfaced to the calling JS application code. At the moment, we are not
adding the message to the state machine context, but only in
`UpdateCheckResult`.

# Test Plan

- Manual testing with the JS API

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

---------

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

show more ...

[expo-updates] Remove @expo/use-updates (#24113)

# Why

This module is being replaced by the new `useUpdates()` JS API in
`expo-updates` for SDK 50.

# How

Remove the module and all referenc

[expo-updates] Remove @expo/use-updates (#24113)

# Why

This module is being replaced by the new `useUpdates()` JS API in
`expo-updates` for SDK 50.

# How

Remove the module and all references to it.

# 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 rollback support to useUpdates() (#24071)

- New UpdateInfoType for rollbacks
- Support for rollbacks in state machine

# Test Plan

- Unit tests and E2E test coverage added

[expo-updates] Add rollback support to useUpdates() (#24071)

- New UpdateInfoType for rollbacks
- Support for rollbacks in state machine

# Test Plan

- Unit tests and E2E test coverage added

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

---------

Co-authored-by: Will Schurman <[email protected]>

show more ...

[expo-manifests] Remove classic manifest types (#24053)

[expo-constants] Change source of truth for constants types (#24049)

[expo-updates][docs] Add a note about using `fetchUpdateAsync` without `reloadAsync` (#24038)

[expo-updates] Remove mention of EAS from documentation in extra params methods (#24006)

[lint] Upgrade to Prettier v3, typescript-eslint to v6 (#23544)

Why
---
Prettier 3 is out. Add support for it with this linter config.

**Note for reviewer:** the first commit is the one with th

[lint] Upgrade to Prettier v3, typescript-eslint to v6 (#23544)

Why
---
Prettier 3 is out. Add support for it with this linter config.

**Note for reviewer:** the first commit is the one with the actual
changes. The rest of this PR are changes to get the linter passing
(mostly autofix).

How
---
Update eslint-config-prettier and eslint-plugin-prettier. To address
deprecation warnings, also update typescript-eslint/parser and
typescript-eslint/eslint-plugin.
Because of an update to typescript-eslint/parser, we need to suppress
deprecation warnings (documented in a comment).

Regenerated test snapshots. Due to the upgraded dependencies, typecasts
and optional chaining are now auto-fixable by lint. This converts
warnings into autofixes.

Test Plan
---
`yarn test` in the linter config. Run `expotools check --all --fix-lint
--no-build --no-test --no-uniformity-check` to try this config on the
whole repo.

---------

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

show more ...