-
Notifications
You must be signed in to change notification settings - Fork 197
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
Incomplete request list on license expiration #1686
Comments
The expired license doesn't relate to how Proxyman captures the traffic. Just wondering: Do these requests call from the Apple Simulator to Apple Server or from your app to your server? |
@NghiaTranUIT I mean there's nothing else had happened except this two things with this machine. |
Does it happen with the iOS Physical device? |
@NghiaTranUIT I've checked it with an |
It started working again after phot laptop restart, still have no clue what happened with it back there, but I guess the issue could be closed now. |
There is an bug from Apple iOS Simulator, we have some users, has confirmed the same issue: #1696 (comment) If you use iOS 14, everything is working fine. |
Description
Proxyman doesn't shows any errored connection after (?) license expiration.
Steps to Reproduce
I have no idea whether it relevant or not, but that's the only guess I've got.
My license had expired just yet, and now there's some lost requests with proxyman that comes from within iOS Simulator.
I mean, i'm using internal logger and Little snitch, both shows me those requests (whether they're succeeded or not), but not proxyman. There's just nothing appears at that time.
In addition to that I can not say that it failed to handle Simulator requests completely. I mean it do show some of the requests to a server within the same app simulator session, even more — to the exact same gateway, but to a different url path.
Current Behavior
Like here's the Proxyman log:
So by other logs I see that this log should be followed with the
https://hidden/path3
API call, but it doesn't get appeared in Proxyman.Expected Behavior
Environment
The text was updated successfully, but these errors were encountered: