Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(cli): fix Expo Go downloading indicator #19817

Merged
merged 3 commits into from Nov 4, 2022

Conversation

EvanBacon
Copy link
Contributor

Why

A number of issues were preventing the loading indicator from showing when Expo Go was downloading. When network conditions are bad (e.g. in my house) the CLI will appear to stall for ~5 minutes.

How

  • Ensure wrappers don't export async functions.
  • Wrap node-fetch with progress bar support before wrapping with cache support.
  • Add initial spinner for fetch request to Expo Go.
  • Add debug logs for diagnosis.

Test Plan

  • Uninstall Expo Go and run yarn expo start with EXPO_NO_CACHE. Loading bar should show up for entire duration of the download.

Checklist

@expo-bot expo-bot added the bot: suggestions ExpoBot has some suggestions label Nov 2, 2022
Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com>
@expo-bot expo-bot added bot: passed checks ExpoBot has nothing to complain about and removed bot: suggestions ExpoBot has some suggestions labels Nov 2, 2022
@EvanBacon EvanBacon merged commit 82f3de7 into main Nov 4, 2022
@EvanBacon EvanBacon deleted the @evanbacon/cli/fix-download-indicator branch November 4, 2022 21:02
brentvatne pushed a commit that referenced this pull request Nov 7, 2022
* fix(cli): fix Expo Go downloading indicator

* Update packages/@expo/cli/CHANGELOG.md

Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com>

Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bot: passed checks ExpoBot has nothing to complain about
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants