Skip to content
This repository has been archived by the owner on Jan 18, 2024. It is now read-only.

Show more human-readable errors when computer cannot connect to AWS/GCP #806

Closed
Changdao opened this issue Jul 3, 2019 · 7 comments
Closed
Labels
enhancement New feature or request

Comments

@Changdao
Copy link

Changdao commented Jul 3, 2019

image

@Changdao
Copy link
Author

Changdao commented Jul 3, 2019

YOU, EXPO, SERVICE heavily depends on Cloud service, but has no fail-over/high-available design.
In fact, I investigate into your script, which is trivial and wasting time.
image
can not be connected, which seems unstable.
And there is no retrying method and other easy to recover methods to solve the environment problem.
I list my suggestions here:

  1. if there is remote service unavailable, please implicitly tell the developer which service is not reachable.
  2. Add more documents and notices to tell the developer, expo is not easy working in "detach" mode.
  3. Provide intuitive tool to help developer organize the "detach" process.
  4. Provide effective method to import native Android/iOS component into expo instead of "detach"

That's all, thank you.

@Changdao
Copy link
Author

Changdao commented Jul 3, 2019

Please understand a CHINSE developer's SPECIAL concern.

@Changdao
Copy link
Author

Changdao commented Jul 5, 2019

image
Hang here, why don't you give more detail about the network activity?

@Changdao Changdao changed the title Expo: little convenience, more trouble. Suggestion: little change can solve big trouble. Jul 8, 2019
@AdamJNavarro AdamJNavarro added the enhancement New feature or request label Jul 8, 2019
@ide ide changed the title Suggestion: little change can solve big trouble. Show more human-readable errors when computer cannot connect to AWS/GCP Jul 9, 2019
@ide
Copy link
Member

ide commented Jul 9, 2019

We rely on AWS CloudFront, which is already responsible for being highly available and having its own failover at the DNS level. If there is an issue with your network connection preventing you from connecting to one of the largest / the largest CDN on the planet, that is out of the scope of our infrastructure at the moment.

I agree we could make the error message clearer and more human-readable and have changed the title of this issue appropriately.

@Changdao
Copy link
Author

image

@Changdao
Copy link
Author

Please refer to the above message?
What did we get from it? Just nothing.
It's strong recommend that expo could provide more useful information

@EvanBacon
Copy link
Contributor

I recently took a pass at upgrading the error messages for asset uploading in #2517 if you run into any more confusing error messages please feel free to open a new issue!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants