search

Absolucy / xenon-ios

The public source and documentation for Xenon iOS tweak.
https://chariz.com/buy/xenon
7 stars 0 forks source link

Immediate error after every connection attempt #13

Closed joekenda404 closed 3 years ago

joekenda404 commented 3 years ago

Describe the bug

This applies to the current version and the previous 2 versions of the client and server - never had a successful connection. Log reflects web server starting, latest version check, "successful connection" and "bringing up webserver" - followed by:

[ERROR] thread 'tokio-runtime-worker' panicked at 'error binding to 127.0.0.1:4200: error creating server listener: Can't assign requested address (os error 49)': /Users/aspen/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.14.4/src/server/server.rs:67

To Reproduce

Steps to reproduce the behavior:

  1. Go to Settings > Xenon
  2. Click on Pair Computer
  3. Scan QR code
  4. See error above

Expected behavior

Connect to/browse device

Setup (please complete the following information):

Absolucy commented 3 years ago

Is anything else listening on port 4200?

joekenda404 commented 3 years ago

Nope, checked using netstat and lsof

Absolucy commented 3 years ago

did you try changing the port in the config.toml?

This is the first time i've seen that happen, weird.

joekenda404 commented 3 years ago

Just tried changing config.toml to various ports, restarting the server each time. Same error with both devices (?)

joekenda404 commented 3 years ago

Also tried flushing routing table (on mac), regenerating keys (on iPhone) and copy/pasting manual configuration. Same error.

joekenda404 commented 3 years ago

Also, I can ping Mac from phone and phone from mac using the ports from the config.toml - but still get same behavior/error.

Absolucy commented 3 years ago

If you're curious, this is the line of code that panics: https://github.com/hyperium/hyper/blob/master/src/server/server.rs#L65-L70

I'm still clueless as to what's causing it tho. Maybe this just means that I should skip the scuffed WebDAV proxy and go full FUSE?

joekenda404 commented 3 years ago

Thanks, I'm going to try it with another Mac tonight and see if the same thing happens.

joekenda404 commented 3 years ago

It works with my M1 Mac Mini (running Big Sur). The difference seems to be that, while installing the Xenon client on that Mac, I am prompted to allow permission for the client to control Finder. After granting permission, Xenon appears under System Preferences > Security and Privacy > Automation > Finder.

On my MacBook Pro running Mojave, this permission request is never made while installing the client and cannot be added manually (it must be requested by the app).

Is there any reason why the client might not request this permission when installing on Mojave?

Thanks.

Absolucy commented 3 years ago

No clue. It runs an embedded AppleScript file, which is what asks for permission. It does the same thing as Go -> Connect To Server, but automatic.

joekenda404 commented 3 years ago

That IS weird, then. I'm stumped.

stale[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. The issue will, until proven otherwise, assumed to be user error or not an issue at all.