[android] [application] migrate to sweet API (#24568)

# Why

Improved version of https://github.com/expo/expo/pull/22585.

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

chore(expo-network): remove deprecated getMacAddressAsync (#24505)

# Why

- `getMacAddressAsync` has been deprecated for years.
- Add support for running the module in server environments.

---

chore(expo-network): remove deprecated getMacAddressAsync (#24505)

# Why

- `getMacAddressAsync` has been deprecated for years.
- Add support for running the module in server environments.

---------

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

show more ...

[expo-contacts][docs] Fix broken link for app config doc (#24477)

[expo-device][docs] Fix broken link for app config doc (#24418)

[expo-gl][docs] Fix link and update verbiage (#24405)

[notifications][docs]: Fix broken internal links (#24401)

[web-browser][docs] Fix broken link for AppState (#24400)

[image] tweaks and fixes for types JSDoc (#22289)

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

chore(linking)!: update linking module (#24300)

# Why

- Remove deprecated `makeUrl` function.
- Add web-specific version of parsing to reduce bundle size on web.
- Fix bug on web where parsing

chore(linking)!: update linking module (#24300)

# Why

- Remove deprecated `makeUrl` function.
- Add web-specific version of parsing to reduce bundle size on web.
- Fix bug on web where parsing a URL with a `+` in the pathname is
curtailed.

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

- Extensive tests should continue passing.

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

---------

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

show more ...

[secure-store][android] Secure store audit (#23804)

# Why
ENG-6327
Secure-store was using the old modules API. We wanted to add synchronous
functions to the API, so it's possible to use SecureSto

[secure-store][android] Secure store audit (#23804)

# Why
ENG-6327
Secure-store was using the old modules API. We wanted to add synchronous
functions to the API, so it's possible to use SecureStore in the global
JS scope. During the migration I've also found some bugs/unexpected
behaviours which were corrected

# How

- Migrated `secure-store` to Kotlin and the new modules API
- Changed callback-based authentication prompt to Kotlin coroutines
- Added `getItemSync` and `setItemSync` functions
- Both functions call the same functions as Async versions, but on the
main thread
- It is now possible to save values which require authentication and
ones that don't under one keychain on the JS side. This is archived by
creating two separate keys on the native side.
- Before it wasn't possible to save a no-authentication value under a
keychain, which was initialised with a require-auth value (an exception
was thrown). It was possible to save a value which requires
authentication into a keychain which was already initialised as no-auth,
but it wasn't really encrypted with the necessity of auth and could've
been decrypted without authentication (although `secure-store` always
asked for biometrics correctly)
- It is now possible to save values under different keychains but the
same key. `Secure-store` can now differentiate between them. Before
saving `value1` under `key1` and `keychain1` and `value2` under `key1`
and `keychain2` would overwrite the `value1` under `key1` with a new
value. Now they are separate. This archived by saving the items in
shared preferences under a key which includes the keychain eq.
`keychain1-key1` and `keychain2-key1`. This emulates the `ios`
`secure-store` behavior
- Backwards compatibility with the current naming scheme of keystore
aliases has been kept
- Improved invalidated key exception handling. When removing a key from
the key store all values under that key will be removed from shared
preferences in order to avoid exceptions caused by decryption fails.
This doesn't apply to values stored with previous versions of
`expo-secure-store` as it is not possible to determine if value was
stored with a keychain without making an decryption attempt.
- Updated the docs
- Removed SDK20 read support

# Test Plan

Tested in Bare Expo and Expo Go on a physical android 13 and 7 devices
(forced api < 23 functions on android 7 only for testing since we don't
have such an old device)

---------

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

show more ...

[localization] Add default temperature unit to the locale (#24059)

# Why

We want to add a temperature unit field which will return the
temperature unit used in the region
ENG-6859

# How

O

[localization] Add default temperature unit to the locale (#24059)

# Why

We want to add a temperature unit field which will return the
temperature unit used in the region
ENG-6859

# How

On iOS the unit is based on the current settings in the region tab of
the settings app (note: settings values are ignored in iOS simulator so
any testing in the future should be done on a physical device)
On Android and web a list of regions which use fahrenheit is used and
compared with the current device region.

# Test Plan

Tested in Bare Expo on Android 13, iOS 16 and web

---------

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

show more ...

[expo-media-library][docs] Add info about passing `endCursor` when using `after` property (#24047)

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

[contacts][android] Fix `addContactAsync` failing when e-mail id is provided (#23877)

# Why

ENG-9682, fixes https://github.com/expo/expo/issues/23828

`addContactAsync` would fail when adding

[contacts][android] Fix `addContactAsync` failing when e-mail id is provided (#23877)

# Why

ENG-9682, fixes https://github.com/expo/expo/issues/23828

`addContactAsync` would fail when adding a contact with an e-mail of
phone with a specified id.

# How

The ids shouldn't be provided by the user, they are generated by the OS
on creation of the contact (on both iOS and Android). Fixed this by
ignoring the id when adding a contact on the JS side. Updated the docs

# Test Plan

Tested on Android 13 Pixel 6 and iOS 16 iPhone 11

---------

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

show more ...