[permissions] Remove permissions package (#24081)

# Why

Removes `expo-permissions` package. That package was deprecated for a long time but never removed. I think we can do it now.

# ToDo

[permissions] Remove permissions package (#24081)

# Why

Removes `expo-permissions` package. That package was deprecated for a long time but never removed. I think we can do it now.

# ToDo

- [ ] publish new home app - will be done in a separate PR

# Test Plan

- bare-expo ✅
- expo-go ✅

show more ...

[iOS] Experimental new Video component (#24428)

[blur] Support more blur effects (#24392)

[sensors][iOS] Migrate to Expo Modules API (#24133)

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

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

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