# Why
close ENG-4618
# How
- install expo sdk based on target project's react-native version
- will try to install `expo@^45.0.0` first and fallback to install `expo@>=45.0.0-0 <46.0.0` for prerelease version
- add react-native 0.68 template support
# Test Plan
#### Unit Test
```
PASS install-expo-modules src/utils/__tests__/expoVersionMappings-test.ts
getDefaultSdkVersion
✓ should resolve as sdk 45 from react-native 0.68 project (16 ms)
✓ should resolve as sdk 45 from react-native 0.65 project (1 ms)
✓ should resolve as sdk 44 from react-native 0.64 project
PASS install-expo-modules src/plugins/android/__tests__/withAndroidModulesMainApplication-test.ts
setModulesMainApplication
✓ should able to update from react-native@>=0.68.0 template (2 ms)
PASS install-expo-modules src/plugins/android/__tests__/withAndroidModulesMainActivity-test.ts
setModulesMainActivity
✓ should add ReactActivityDelegateWrapper for react-native@>=0.68.0 - java (1 ms)
✓ should add ReactActivityDelegateWrapper for react-native@>=0.68.0 - kotlin (1 ms)
```
#### Integration Test
```sh
$ npx react-native init RN068 --version 0.68
$ npx install-expo-modules
$ expo run:android
$ expo run:ios
$ export ORG_GRADLE_PROJECT_newArchEnabled=true ; expo run:android
$ cd ios; rm -rf Pods build; RCT_NEW_ARCH_ENABLED=1 pod install
$ expo run:ios
```
# Why
to support more customized native build properties, like android `compileSdkVersion` and `targetSdkVersion`. we need an extensible way for what we did in the `jsEngine` property (reading a value from source config and merge it into properties file).
close ENG-4021
# How
refactor original dedicated `JsEngine` plugin to generic `BuildProperties` plugin. it is rule based and easy for extension.
the source config can be either from expo config or from other custom config passing through config-plugin props.
Co-authored-by: Evan Bacon <[email protected]>
* fix: pick correct scheme for open android app
Expo CLI should pick the scheme with the empty host
or it's much exactly matched to `expo-development-client`
* fix: replace schemes with data
* fix: update unittests
* fix: cleanup
* fix: fixed lint
* fix: update expo-cli for get correct scheme
* fix: filter items without scheme
* fix: documentation and proper handling of passing unparsed options to install
* fix: properly pass parameters to package manager
* fix: add default parameter value for consistency
* docs: changelog
* fix: also pass parameters to `npm install`
* test: added test coverage for new functionality
# Why
Fixes that QR code on web UI pointed to the `Expo Go` directly instead of to the interstitial page.
Fallback to the SDK version if the runtime version wasn't defined.
# How
- Extended the dev graphQL server to serve Interstitial page URL if available.
# Test Plan
- runs the local version of the CLI and confirms that the web QR code points to the correct place.
- checks if the SDK version was detected when the runtime version isn't available.
# Why
Currently, if someone scans the QR code, we can't detect if the device can handle a deep link to `Expo Go` or `Development Build`. So we're trying to detect if the redirection was successful. If not we display a message.
# How
When the user clicks, we trigger a timeout. After some time, we check if the document became inactive (if so, we know that the redirection was successful). This flow gets more complicated on iOS because the user will see a modal. In that case, we need to fire the timeout after the document will be focused.
# Test Plan
- manual tests with Android device and iOS simulator.