Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Reopening popup with connected to adb and click android scan mode #575

Open
1 task done
RaSan147 opened this issue Apr 5, 2024 · 2 comments
Open
1 task done
Labels
bug Something isn't working

Comments

@RaSan147
Copy link

RaSan147 commented Apr 5, 2024

Has this been reported before?

  • I have checked for existing reports of this issue

Repro steps

  1. Connect with adb
  2. click on the wifi mode/scan mode for android
  3. this popup shows up (closing it reopens)

image

How often does this bug happen?

Once

The desktop OS you're using

Win 11 22H2

Details of other apps/devices

No response

Error screenshot

image

Any other info?

Additional issue, used force end from task manager (was not closing normally). and now whenever i try to open it, the port is still locked and app not opening.

@RaSan147 RaSan147 added the bug Something isn't working label Apr 5, 2024
@pimterry
Copy link
Member

pimterry commented Apr 5, 2024

Hmm, this probably means that your server has broken somehow, and so the UI is failing to control the proxy over and over again. This isn't related to that button at all (that button doesn't really do anything, it just shows an extra bit of UI) I think that's a red herring.

Can you share your logs from C:\Users\<username>\AppData\Roaming\httptoolkit\logs\last-run.log? That might have some more info about what failed here.

If the port is in still use then there's probably a node.exe process somewhere for HTTP Toolkit server that's still running. If you kill that then you'll be able to restart the app. Alternatively you can manually check which process is blocking the port with netstat -ano | findStr "45456".

@RaSan147
Copy link
Author

RaSan147 commented Apr 5, 2024

last-run.log

idk if it will help coz i re-ran the app after re-booting.
Ah dang, i forgot about checking node...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants