[android][file-system] Migrate to new modules API (#22728)

[android][file-system] Migrate to new modules API (#22728)

[Android] Remove SDK 46 (#22755)

Remove Amplitude from Expo Go (#22523)

[expo-updates][expo-go] Support new SDK version field in new manifests (#22356)

[android][screen-capture] Migrate to Expo Modules API (#22208)

Revert "Fix screen orientation module import (#22215)" and implement the change in correct file. (#22217)

Fix brightness module import (#22213)

[go] integrate firebase crashlytics on android (#22036)

# Why

to have more information about the crashes than just from google play store. this pr tries to integrate firebase crashlytics with mor

[go] integrate firebase crashlytics on android (#22036)

# Why

to have more information about the crashes than just from google play store. this pr tries to integrate firebase crashlytics with more powerful features like ndk integration and custom logging.
close ENG-1380

# How

- integrate crashlytics with ndk support
- log the loading experience manifest url
- [tools] we need a further step `./gradlew :app:uploadCrashlyticsSymbolFileUnversionedRelease` for uploading ndk native symbols to crashlytics. we also integrate this into fastlane and expotools. this step may take longer time to process. from my environment, it takes about 30mins.

# Test Plan

manually triggering crash and see the crashlytics dashboard

show more ...

[go] Disable Remote JS debugger on SDK 49+ (#22027)

# Why

As part of https://github.com/facebook/react-native/pull/36754, we
should remove the ability to use remote JS debugging from the DevMenu

[go] Disable Remote JS debugger on SDK 49+ (#22027)

# Why

As part of https://github.com/facebook/react-native/pull/36754, we
should remove the ability to use remote JS debugging from the DevMenu.
This change is motivated by the fact that generally speaking, this
feature does not work with the new architecture and most of the popular
modules these days.

Follow up of https://github.com/expo/expo/pull/22010
Closes ENG-8088

# How

This PR removes the `Remote JS debugger` option from Expo Go menu when
using SDK 49 or above

# Test Plan


Run Expo Go locally

<table>
<tr><th>iOS</th><th>Android</th></tr>
<tr>
<td>
<img
src="https://user-images.githubusercontent.com/11707729/230474710-28b0a90a-9f49-48c1-baaf-8883fdad8178.png"
height="700px" />
</td>
<td>
<img
src="https://user-images.githubusercontent.com/11707729/230473058-e06831e6-96d9-4a17-8da1-d884d9c9678f.png"
height="700px" />
</td>
</tr>
</table>


# 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 `expo prebuild` & EAS Build (eg:
updated a module plugin).

show more ...

[go][android] Fix requestPermissions NullPointerException (#21912)

# Why

Closes https://github.com/expo/expo/issues/21544

# How

When launching the camera through ExpoImagePicker we check fo

[go][android] Fix requestPermissions NullPointerException (#21912)

# Why

Closes https://github.com/expo/expo/issues/21544

# How

When launching the camera through ExpoImagePicker we check for device
permissions, but on an Android 13 device
the resolution of `Manifest.permission.WRITE_EXTERNAL_STORAGE.takeIf {
Build.VERSION.SDK_INT < Build.VERSION_CODES.TIRAMISU }` returns `null`.
While this isn't a problem for apps using the default
`requestPermissions` Activity function, it causes a crash on Expo Go
because we have custom logic for permissions using the
ScopedPermissionsRequester class.

To resolve this issue, we have two options:

- Ensure that all `askForPermissions` calls always use `*listOfNotNull`
https://github.com/expo/expo/pull/21907)
- Update `ScopedPermissionsRequester` `requestPermissions` to ignore
`null` values

In my opinion, the section option is more robust and ensures that there
is no discrepancy between apps running on Expo Go and dev-client/EAS
builds

# Test Plan

Run unversioned Expo Go and test launching the camera using
`launchCameraAsync`

# Checklist


- [ ] 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 `expo prebuild` & EAS Build (eg:
updated a module plugin).

show more ...