mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-25 16:15:55 +03:00
[GH-ISSUE #1124] After hitting clear, the first network call made shows up twice #1118
Labels
No labels
Discussion
Feature request
In Progress...
Plugins
Waiting response
Windows
Windows
bug
duplicate
enhancement
feature
good first issue
iOS
macOS 10.11
question
wontfix
✅ Done
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Proxyman#1118
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ColtonIdle on GitHub (Jan 26, 2022).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1124
Originally assigned to: @NghiaTranUIT on GitHub.
Proxyman version?
Version 3.0.0 (30000)
macOS Version?
m1 mac 12.1 (21C52)
Issue
I noticed the issue because I have a refresh button in my android app. every time I hit the refresh button I would watch proxyman for the network log. After a while I clear the list, then hit the button in my app again and... TWO requests show up. Clear again + button in my app = 2 requests! If you see the video... if I wait 5+ seconds after hitting "clear" then I get only get ONE request. I hope this helps you fix this. thank you
https://user-images.githubusercontent.com/31751141/151103248-8345abf1-3ceb-437a-b167-0d73d624240b.mp4
@NghiaTranUIT commented on GitHub (Jan 26, 2022):
Thanks. Your video is super useful for me to reproduce the bug 😄
It's a bug. I assume that when the connection is stopped (Click on the Clear button), it's accidentally added to the main table view. It's incorrect behavior.
@ColtonIdle commented on GitHub (Jan 26, 2022):
Thanks @NghiaTranUIT !
@NghiaTranUIT commented on GitHub (Apr 8, 2022):
@ColtonIdle I tried to reproduce your issue on the latest build 3.3.0, but I'm not able to reproduce it.
It seems that this issue is fixed 👍
@ColtonIdle commented on GitHub (Apr 15, 2022):
Awesome. Thank you @NghiaTranUIT !!!