Installation Issue - bad CPU type in executable: sshnp

TylerTrott commented 3 months ago

Describe the bug

When installing client side np, installation occurs as expected, however, when running sshnp -f @sys_client -t @ufw_pi_device -h @rv_am -d ufw_pi -i <~/.ssh/id_ed25519 -s it outputs: zsh: bad CPU type in executable: sshnp

Steps to reproduce

First run curl installation
Then run chmod u+x universal.sh and ./universal.sh
And then run sshnp

Expected behavior

Connect to configured sshnp device

Screenshots

Smartphones

Device: Mac
OS: MacOSx64

Were you using an atApplication when the bug was found?

No response

Additional context

No response

XavierChanth commented 3 months ago

Can you run the following and post the logs:

mkdir -p /tmp/testnoports
cd /tmp/testnoports
curl -L https://github.com/atsign-foundation/noports/releases/download/v5.3.0/sshnp-macos-x64.zip -o sshnp-macos-x64.zip
unzip sshnp-macos-x64.zip
sshnp/sshnp --help

To cleanup after:

rm sshnp-macos-x64.zip
rm -rf sshnp/

TylerTrott commented 3 months ago

Xlin123 commented 3 months ago

GitHub making a breaking change... https://github.com/atsign-foundation/noports/pull/1144

atsign-foundation / noports

Installation Issue - bad CPU type in executable: sshnp #1140