* 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.
# 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