[android][tools] fix expo go versioning issues on android (#22950)

# Why

fix expo-go android versioning for sdk 49
close ENG-8955

# How

- [tools] fix for react-native monorepo changes
- [

[android][tools] fix expo go versioning issues on android (#22950)

# Why

fix expo-go android versioning for sdk 49
close ENG-8955

# How

- [tools] fix for react-native monorepo changes
- [tools] update manifest-merger because the original one doesn't support java 17. since the new manifest-merger has kotlin runtime and the jar takes about 35MB. rather than committing a prebuilt jar, now we build manifest-merger from source.
- [tools] since #22609 we don't have `package` in libraries' AndroidManifest.xml, the manifest-merger still requires the `package`, so we have to temporarily put the `package` back during manifest merging. (the `package` name is generated from `namespace` in build.gradle)
- [tools] the original jarjar uses outdated [ASM](https://asm.ow2.io/) and it doesn't support bytecode generated by kotlin. react-native now has some kotlin code, and the original jarjar cannot transform package name from those kotlin classes. i've tried to rebuild a jarjar from [this revision](https://github.com/google/jarjar/commit/e11d5636aa45664271c8f1603067527b2520f591). this requires some manual steps like updating ASM libs and install ant builder. so i still commit the prebuilt jarjar in this pr.
- [updates] force casting for `UpdateEntity` to deal with kotlin smart casting from versioned to unversioned kernel class. (i'll leave inline comment for this)
- [expo-modules-core's `android-annotation`] the project stays in a place that does not support versioning yet. in this pr i just keep it as an unversionable project. cc @lukmccall

# Test Plan

`et add-sdk -p android -s 49.0.0` + android versioned expo-go + sdk 49 NCL smoke test

show more ...

[android][tools] fix android versioning (#20889)

# Why

fix android versioning after react-native 0.71 upgrade

# How

mostly fixing transforms

# Test Plan

1. `et add-sdk -p android -s 4

[android][tools] fix android versioning (#20889)

# Why

fix android versioning after react-native 0.71 upgrade

# How

mostly fixing transforms

# Test Plan

1. `et add-sdk -p android -s 48.0.0`
2. `cd android ; ./gradlew :app:assembleVersionedDebug`
3. versioned android expo go + sdk 48 ncl smoke test

show more ...

[tools] Update android versioning script for sdk 47 (#19518)

# Why

update android versioning script for sdk 47

# How

- [android] update gradle wrapper version to 7.5.1, which aligned with r

[tools] Update android versioning script for sdk 47 (#19518)

# Why

update android versioning script for sdk 47

# How

- [android] update gradle wrapper version to 7.5.1, which aligned with react-native 0.70
- [localization] fix compileSdkVersion 33 build error
- [tools] update versioning script
- remove `renameHermesEngine` which is deprecated patchelf based hermes versioning
- replace duplicated runReactNativeCodegenAndroidAsync with `Codegen.runReactNativeCodegenAsync`
- update versioning script to support building in-place from react-native-lab
- update for react-native 0.70
- update versionCxx for expo-modules-core
- support other new style vendoring modules
- @react-native-community/slider
- react-native-gesture-handler (with cxx files but they're only for new architecture)
- react-native-screens (with cxx files but they're only for new architecture)
- react-native-svg
- react-native-reanimated (with cxx files)
- remove old reanimated versioning scripts

# Test Plan

```
$ et add-sdk -p android -s 47.0.0
$ cd android && ./gradlew :app:installVersionedDebug
# smoke test on sdk 47 NCL
```

show more ...

[versioning][android] Support react-native 69 (#18032)

* [skip ci] suppoort rn69

* version expo-modules-core

* review feedback + small cleanup

[tools] add and hook up lint setup, remove `module-scripts` (#16974)

[android][ios] Upgrade expo go to react-native 0.68 (#16752)

# Why

upgrade for sdk 45

# How

- upgrade our react-native fork to 0.68 based: https://github.com/expo/react-native/tree/sdk-45

[android][ios] Upgrade expo go to react-native 0.68 (#16752)

# Why

upgrade for sdk 45

# How

- upgrade our react-native fork to 0.68 based: https://github.com/expo/react-native/tree/sdk-45
- migrate android/ios projects to 0.68
- [android] bump `targetSdkVersion` and `compileSdkVersion` to 31 (aligned with react-native 0.68)
- [tools] update codegen customization in `update-rn` script
- [tools] update versioning scripts
- [android] replace our customized `NDK_ABI_FILTERS` with official supported `reactNativeArchitectures` gradle property
- [android] use jdk 11

that is a huge pr because of changes from `et update-rn`. recommend to review this pr by commits.

most `add-sdk` problems on 0.68 are fixed. there are still an issue on android. i'll address in another pr.

- expo-av CMakeLists.txt versioning

# Test Plan

- unversoned android expo-go + ncl
- unversoned ios expo-go + ncl
- `et add-sdk -p ios -s 45.0.0` + versioned ios sdk 45 expo-go + ncl
- `et add-sdk -p android -s 45.0.0` + versioned android sdk 45 expo-go + ncl (should commented out expo-av in `ExperiencePackagePicker.kt`

show more ...

[android][ios] Fix versioning for expo go after react-native 0.67.2 upgrade (#16401)

# Why

for sdk45 and based on #16400

# How

- [tools] Fix versioning tools for react-native 0.67.2 upgrade

[android][ios] Fix versioning for expo go after react-native 0.67.2 upgrade (#16401)

# Why

for sdk45 and based on #16400

# How

- [tools] Fix versioning tools for react-native 0.67.2 upgrade
- [expo-modules-core][ios] Fix missing `EX` prefix to some objective-c files for versioning support
- [autolinking] Apply our cocoapods fix for `React-Core` swift support to versioned code
- [expo-updates] fix an incompatible `ReactInstanceManager` in UpdatesPackage where UpdateController is unversioned but UpdatePackage is versioned.
- [expo-file-system] okhttp/okio code for new versioned code build successfully. this is done in #16446

# Test Plan

- `et add-sdk -p android -s 45.0.0` and build/launch sdk 45 expo go with sdk 45 ncl
- `et add-sdk -p ios -s 45.0.0` and build/launch sdk 45 expo go with sdk 45 ncl

show more ...

[tools] Fix android versioning after rn 0.64 upgrade (#14013)

# Why

android versioning tool breaks after react-native 0.64 upgrade

# How

1. support codegen and the strategy aligned with ios

[tools] Fix android versioning after rn 0.64 upgrade (#14013)

# Why

android versioning tool breaks after react-native 0.64 upgrade

# How

1. support codegen and the strategy aligned with ios versioning in #13972:
run codegen before versioning and disable react-native's build time codegen.
2. support `Android-prebuilt.mk` versioning and update some new libraries to be included in versioning.
3. fix some expo-module error.
4. remove broken `expo-payments-stripe` transformation which expectedly to be remove from sdk43.

# Test Plan

`et add-sdk -p android -s 43.0.0` without errors.
after that i also testing the expo-go building which the errors are from some expo-modules updates, will not cover this in this pr.

show more ...

[android] pickFirst for only necessary libraries (#13140)

# Why

pickFirst is risky that we will never know which libraries will be picked if duplicated files are from different versions.
in this

[android] pickFirst for only necessary libraries (#13140)

# Why

pickFirst is risky that we will never know which libraries will be picked if duplicated files are from different versions.
in this pr, we try to pick the libraries we really need:

- libfbjni.so
prebuilt library from gradle dependency `extractJNI("com.facebook.fbjni:fbjni:0.0.2")`
- libhermes-inspector.so
- libfolly_futures.so
libraries we didn't rename during sdk publishment before.

fortunately, sdk 39-41 are all based on react native 0.63, so it should not have problems in the meantime.

in the future, only libfbjni.so is needed for pickFirst.
that might still be a risk once we upgrade react native 0.65+ who use the fbjni version.
(somehow we might need to build fbjni ourselves from source or patch old react-native to unify fbjni version)

# How

1. pickFirst for only necessary libraries.
2. add libhermes-inspector.so and libfolly_futures.so to auto renaming list.
3. add sanity check if there are any libraries we didn't rename from versioning.

# Test Plan

1. client-android build pass
2. `et add-sdk -p android` will not show errors

Co-authored-by: Charlie Cruzan <[email protected]>

show more ...

[tools] Move tools/expotools one folder up (#11410)