Ngrok CLI Installation Failed due to "Breaking Changes" in NgrokV3

======== "Breaking Changes" in NgrokV3 ========

Wappler Version : 6.8.0
Operating System : Windows 11
Server Model: Dev > Docker > Development Local
Database Type: none
Hosting Type: none

Expected behavior

Following the docs here: Sharing Local URLs with Ngrok I expected a successful install of the latest version of Ngrok

Actual behavior

Scoop ran and updated successfully however, Ngrok CLI installation failed due to Ngrok making "Breaking Changes" in Ngrok v3

How to reproduce

Follow the docs here: Sharing Local URLs with Ngrok

Terminal Output

  • Updating Scoop...
    Updating 'main' bucket...
    Checking repo... ok
    The main bucket was added successfully.
    Scoop was updated successfully!
    WARN Scoop uses 'aria2c' for multi-connection downloads.
    WARN Should it cause issues, run 'scoop config aria2-enabled false' to disable it.
    Installing 'ngrok' (3.18.4) [64bit]
    Starting download with aria2 ...
    Download: Download Results:
    Download: gid |stat|avg speed |path/URI
    Download: ======+====+===========+=======================================================
    Download: ed9faf|OK | 6.0MiB/s|C:/Users/UsersName/scoop/cache/ngrok#3.18.4#https_bin.equinox.io_a_4vvyKGoo1gc_ngrok-v3-3.18.4-windows-amd64.zip
    Download: Status Legend:
    Download: (OK):download completed.
    Checking hash of ngrok-v3-3.18.4-windows-amd64.zip ... ok.
    Extracting ngrok-v3-3.18.4-windows-amd64.zip ... done.
    Linking ~\scoop\apps\ngrok\current => ~\scoop\apps\ngrok\3.18.4
    Creating shim for 'ngrok'.
    'ngrok' (3.18.4) was installed successfully!
    Notes

There are breaking changes in v3 of ngrok. For details, see: ngrok documentation. To stay on v2, install versions/ngrok2
'xitcode"' is not recognized as an internal or external command,
operable program or batch file.
Ngrok CLI installation failed!

Please see screenshot:

Actually we are on Ngrok version 3 for a long time already, there are no breaking changes for us.

The real error here is different:
image

somehow a command "xitcode" gets called which does not exist. It is probably an error about checking the "exitcode" from the previous run command but the E is missing...

We couldn't find that error in our code is it is probably somewhere in the scoop or ngrok itself.

So maybe just do a system check again.

1 Like

Thank you for your always prompt reply. The System Check did the trick. Thanks again!

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.