fix(cli): improve ngrok error message format (#19822)

* fix(cli): improve ngrok error message format

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

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

* Update packages/@expo/cli/src/start/server/AsyncNgrok.ts

Co-authored-by: Brent Vatne <brentvatne@gmail.com>

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

packages/@expo/cli/CHANGELOG.md

@@ -12,6 +12,8 @@
 
 ### 💡 Others
 
+- Fix ngrok error message format. ([#19822](https://github.com/expo/expo/pull/19822) by [@EvanBacon](https://github.com/EvanBacon))
+
 ## 0.4.6 — 2022-11-02
 
 ### 🎉 New features

packages/@expo/cli/src/start/server/AsyncNgrok.ts

@@ -1,3 +1,4 @@
+import chalk from 'chalk';
 import crypto from 'crypto';
 import * as path from 'path';
 import slugify from 'slugify';
@@ -165,10 +166,9 @@ export class AsyncNgrok {
         onStatusChange(status) {
           if (status === 'closed') {
             Log.error(
-              'We noticed your tunnel is having issues. ' +
-                'This may be due to intermittent problems with ngrok. ' +
-                'If you have trouble connecting to your app, try to restart the project, ' +
-                'or switch the host to `lan`.'
+              chalk.red(
+                'Tunnel connection has been closed. This is often related to intermittent connection problems with the Ngrok servers. Restart the dev server to try connecting to Ngrok again.'
+              )
             );
           } else if (status === 'connected') {
             Log.log('Tunnel connected.');