# Why
Adjusting a couple of things according to the feedback https://www.notion.so/expo/Interstitial-page-testing-c4ee6e71e936460c8df786410d33e3fe
# How
- Replaced the link in the warning with the new one.
- Detected the platform from the user-agent header if the get parameter wasn't provided
- `Development App` -> `Development Build`
- Update QR code to point to the interstitial page if needed.
- The deep links generated by the interstitial page aren't local anymore.
# Test Plan
Test scenarios:
- app without dev-client
- check if the expo go will be installed if not present
- check what happens if the development build isn't present
- check what happens if both development build and expo go isn't available
- test QR code
* Skip updates warning in bare projects when expo-updates isn't in the package.json
* Apply suggestions from code review
Co-authored-by: Brent Vatne <[email protected]>
Co-authored-by: Brent Vatne <[email protected]>
# Why
Close ENG-2211.
# How
Before opening a deep link to the interstitial page, we need to check if everything is installed. So I've added a logic that will install the `Expo Go` and check if the development build is available. If not we will fall back to the expo go.
# Test Plan
Test scenarios:
- app without dev-client
- check if the expo go will be installed if not present
- check what happens if the development build isn't present
- check what happens if both development build and expo go isn't available
# Why
Pretty straightforward PR - just adding more information about application to interstitial page.
# How
Added information like:
- app name
- runtime version
- path
# Test Plan
Go to `localhost:19000/_expo/loading?platform=<android | ios>` and check if everything is render correctly.
# Why
Support https://github.com/expo/expo/pull/15655
# How
when the target installation is sdk 44 or above, insert `expo_patch_react_imports!(installer)` inside the `post_integrate do |installer|` block. if there's no existing post_integrate hook, append one right after `use_expo_modules!`
# Test Plan
# Unit Test
```
PASS install-expo-modules src/plugins/ios/__tests__/withIosModulesPodfile-test.ts
updatePodfile
✓ should support classic rn podfile (14 ms)
✓ minimum support for existing post_integrate hook (1 ms)
withIosModulesPodfile sdkVersion snapshots
✓ sdkVersion 43.0.0 (1 ms)
✓ sdkVersion 44.0.0
```
Yarn CLI has a lot of issues installing modules globally. This PR removes the prompt to globally install tools with `yarn global add` and instead just always uses `npm i -g`.
# Why
the version `expo-modules-autolinking@~0.4.0` is for sdk 44 beta only. since `expo-splash-screen` depends on `@expo/prebuild-config`
this will cause multiple `expo-modules-autolinking` issue.
may to fix https://forums.expo.dev/t/expo-updates-breaking-ios-build-on-sdk-44-with-yarn-2/60238
```
$ yarn why expo-modules-autolinking
├─ @expo/prebuild-config@npm:3.0.14
│ └─ expo-modules-autolinking@npm:0.4.0 (via npm:~0.4.0)
│
└─ expo@npm:44.0.0
└─ expo-modules-autolinking@npm:0.5.1 (via npm:0.5.1)
```
which break especially on yarn 2 where `[email protected]` be hoisted to node_modules.
# How
`yarn add expo-modules-autolinking@~0.5.1` which is sdk 44 official version.