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

[expo-camera][ios][android] Support additional EXIF tags when taking photos (#18469)

# Why

Due to system limitations, the photos taken from the Camera api do not have certain EXIF tags, such as G

[expo-camera][ios][android] Support additional EXIF tags when taking photos (#18469)

# Why

Due to system limitations, the photos taken from the Camera api do not have certain EXIF tags, such as GPS coordinates. For simplicity and privacy purposes, we do not want to get the user's location at the background each time a photo is taken. However, some enterprise apps do have a legal requirement to attach GPS coordinates to the photos taken from the app. This is used for compliance purpose to check that the photos are taken at certain locations. Similar requirements are found in [#12077](https://github.com/expo/expo/issues/12077) and [#6399](https://github.com/expo/expo/issues/6399).

# How

Similar to the approach in another plugin react-native-camera [PR#1](https://github.com/react-native-camera/react-native-camera/pull/2402) and [PR#2](https://github.com/react-native-camera/react-native-camera/pull/2577), I've added a new parameter `additionalExif` for the method `takePictureAsync()` alongside the existing `exif` parameter. The `additionalExif` can contain key value pairs of additional exif tags to be written to the image. It will only be written when the `exif` parameter is also set to `true`. There is some special handling of GPS coordinates data to ensure that it meets the standard format.

The current implementation only supports iOS and Android platform.

Example usage:

```typescript
await takePictureAsync({
exif: true,
additionalExif: {
GPSLatitude: 30.82123,
GPSLongitude: 150.25582,
GPSAltitude: 80.808,
}
});
```

# Test Plan

I've added a test case in the test-suite to cover this new parameter. I've also tested the change locally using an iPad Mini 6 for iOS and Galaxy Tab A7 Lite for Android. I've taken the photo with each device, and then use the exif viewer to read the EXIF tags of the photos taken. I've hard-coded a dummy GPS coordinates in the EXIF tags as shown in the example usage above in my testing code, and below are the photos. You can download them and view the GPS coordinates in an EXIF viewer.

show more ...

[test-suite] Fix expo-camera tests and use the new microphone permission requester (#17125)

[test-suite] lint files, add lint check to CI (#15772)

[camera][ios] add video codec option to expo camera (#12772)

[test-suite] Use permission requesters from modules instead of expo-permissions (#12199)

[test-suite] make green on Android (#8642)

[android] update base64 decoding options (#7841)

* [android] [camera] use .NO_WRAP to encode base64 output

* [android] [image-manipulator] use .NO_WRAP to encode base64 output

* [android] [ima

[android] update base64 decoding options (#7841)

* [android] [camera] use .NO_WRAP to encode base64 output

* [android] [image-manipulator] use .NO_WRAP to encode base64 output

* [android] [image-picker] use .NO_WRAP to encode base64 output

* [android] [print] use .NO_WRAP to encode base64 output

* [android] [secure-store] use .NO_WRAP to encode base64 output

Co-authored-by: Bartłomiej Bukowski <[email protected]>
Co-authored-by: Łukasz Kosmaty <[email protected]>

show more ...

[ncl][test-suite] Change imports to SDK 33 syntax with the codemod (#4219)

* [ncl][test-suite] Change imports to SDK 33 syntax with the codemod

* [ncl][test-suite] Add new imported packages to de

[ncl][test-suite] Change imports to SDK 33 syntax with the codemod (#4219)

* [ncl][test-suite] Change imports to SDK 33 syntax with the codemod

* [ncl][test-suite] Add new imported packages to dependencies

show more ...

Move test-suite into the Expo repo under apps

This moves test-suite into the Expo repo, setting things up so that CI can verify changes to modules using test-suite.

Tested by loading and running te

Move test-suite into the Expo repo under apps

This moves test-suite into the Expo repo, setting things up so that CI can verify changes to modules using test-suite.

Tested by loading and running test-suite with `expu start` for now. Also will check that our CI passes since there are some dependencies on test-suite (e.g. publishing it). Before merging, the shipit bot needs to be redeployed as well and may need some manual repo editing inside its container.

fbshipit-source-id: 144e1bd

show more ...