Sometimes Proxyman stops displaying requests that flow through it

[ACATTAN]

Description

Sometimes Proxyman stops displaying and analyzing requests/responses even though they keep flowing through it.
I have an iPhone configured to send all its requests to Proxyman (proxy configuration on the iPhone), and all works fine. At some point - not sure if it's related to deleting all requests on Proxyman or not - suddenly I stop seeing any requests/response on Proxyman, but browsing the internet on the iPhone still works! At this point - restarting Proxyman fixes the problem - which proves that the iPhone was still connected to the proxy (it rules out the option that the iPhone for some reason stopped sending requests to the proxy).

Steps to Reproduce

Unfortunately I don't have steps to make it happen. It just happens every once it a while. Not just to me - it happens to other colleagues in the office too.

Environment

• App version: e.g Proxyman 5.9.0
• macOS version: e.g macOS Sonoma 14.6.1

[NghiaTranUIT]

when it happens on your app, may you try:

• Open the Safari app on iOS -> Visit www.google.com -> Verify if you can see new requests from Safari?
• If it's one your app, try to Clear Session, and verify if it's fixed? 🤔

[ACATTAN]

• When it happened I did open Safari and browsed and it worked, but I couldn't see any request on Proxyman. That's what I was trying to say - the messages seem to continue to flow through Proxyman, but it doesn't display nor analyze them. Once restarted - the problem gets fixed.
• Clearing session doesn't fix it. The opposite - I am suspecting that perhaps clearing the session on Proxyman actually triggers this bug, meaning that it starts happening after I clear the session, but I'm not sure.

[ErkanGorgulu]

I am having the same issue. Proxyman works fine on almost all requests, fetching a list, refresh a token etc. but I can't see my complete purchase request that I send to the backend. I can see it on my terminal because I am logging them. I see that it is fired and sent. Like @ACATTAN mentioned, clearing the session could be triggering this.

[NghiaTranUIT]

@ErkanGorgulu I suppose that it's cached on your client, so the real requests didn't call to your Server.

Can you try to enable the Tools menu -> No Caching, and see if this issue still occurs ?

[ErkanGorgulu]

Sorry for misleading. I have found the issue why that happened. It's not because of Proxyman. I accidentally forgot to put Content-Type header to my request. Take care 👋