NPM RUN DEV - tunnel starts running but TIMED OUT ERROR before receiving APP URL

[JKump]

Issue summary

Please, please help! I have searched for two days now and no one seems to have this issue! Having followed the guide to create a new app from Shopify, stuck on the step when running npm run dev, received success message that tunnel is now running, but not receiving any more terminal output but after a few seconds just an ERROR - TIMED OUT output in the terminal. Could not find this error anywhere else. When trying to go the old way by using Shopify app create with Node and then Shopify app serve, it worked and the tunnel was created and I could install the app. Does not work with this new way with the integrated Shopify CLI.

Expected behavior

After running npm run dev, I should receive terminal output about the App URL generated by ngrok and when clicking on it to be able to install the app.

Actual behavior

after running npm run dev and the success message ✅ Success! The tunnel is running and you can now view your app. after a few seconds just an ━━━━━━ Error ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ timed out

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ output in the terminal.

Steps to reproduce the problem

1. 1. 1. Just follow the 'Create an app' tutorial using Node.js (https://shopify.dev/apps/getting-started/create)

Specifications

• Browser: Chrome 103 (newest version)
• Device: iMac 2020
• Operating System: MacOC Monterey
• Node.js
• Package Manager: npm
• ngrok signed up
• partner account signed up
• dev store signed up

[RMartires]

Hey i've been getting some issues due to ngrok timing out as well, i found a quick work-around https://github.com/Shopify/shopify-app-template-node/issues/994

[rahul138]

i am also facing same issue, update here if someone finds permanent solution

[github-actions[bot]]

This issue is stale because it has been open for 60 days with no activity. It will be closed if no further action occurs in 14 days.

[github-actions[bot]]

We are closing this issue because it has been inactive for a few months. This probably means that it is not reproducible or it has been fixed in a newer version. If it’s an enhancement and hasn’t been taken on since it was submitted, then it seems other issues have taken priority.

If you still encounter this issue with the latest stable version, please reopen using the issue template. You can also contribute directly by submitting a pull request– see the CONTRIBUTING.md file for guidelines

Thank you!