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

Apple TV support 1: podspec and code changes for commonly used modules (#24329)

# Why

First of a series of PRs to add Apple TV support for many (but not all)
Expo SDK modules.

This PR makes A

Apple TV support 1: podspec and code changes for commonly used modules (#24329)

# Why

First of a series of PRs to add Apple TV support for many (but not all)
Expo SDK modules.

This PR makes Apple TV able to compile for apps using
`[email protected]` and ONLY the following modules:

- expo
- expo-application
- expo-constants
- expo-eas-client
- expo-file-system
- expo-font
- expo-json-utils
- expo-keep-awake
- expo-manifests
- expo-modules-core
- expo-splash-screen
- expo-structured-headers
- expo-updates-interface
- expo-updates

# How

- Add tvOS to podspecs
- Native code changes wrapped in `#if TARGET_OS_TV` (for Objective C) or
`#if os(tvOS)` (for Swift)
- Import source for the `ASN1Decoder` Swift framework used by
`expo-updates`, as the public podspec for that framework does not yet
support tvOS

# Test Plan

- Manual testing with a template still in development
- Existing CI for iOS should pass (nothing should be 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 `npx expo prebuild` & EAS Build
(eg: updated a module plugin).

show more ...

[tools] Switch expo home publishing to EAS update (#24216)

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