ProxymanApp / ProxymanApp/Proxyman
Proxyman doesn’t show traffic from a specific macOS app (Dart/Flutter, from App Store) while Wireshark sees it
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 7k
- Forks
- 237
- PR merge metrics
- No merged PRs in 30d
Description
Summary
On a Mac (ARM), Proxyman does not display any network requests from one specific App Store app. Wireshark shows network activity during login and other actions, but Proxyman stays empty. Other apps on the same Mac are captured fine. The app is built with Dart/Flutter and talks to Cloudflare.
Expected behavior
Proxyman intercepts and displays the app’s HTTP(S) requests like it does for other apps on this machine.
Actual behavior
No requests from this app appear in Proxyman, despite visible traffic in Wireshark at the same time.
Environment
macOS: (insert version, e.g., 26.0.1)
Mac: Apple Silicon (ARM)
Proxyman: (5.25.0)
App source: macOS App Store
App tech: Dart / Flutter
Targets: API application use cloudflare.
Steps to reproduce
Launch Proxyman on macOS with system proxy enabled.
Launch the App Store app (Dart/Flutter).
Perform networked actions (e.g., login).
Observe Proxyman — no requests appear from this app.
Open Wireshark — packets are visible during those actions.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files, tests, or entry points are named. Start by reproducing the App Store app's login traffic with Proxyman and Wireshark on Apple Silicon, then investigate why the observed traffic is absent from Proxyman; done means the app's HTTP(S) requests appear in Proxyman.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter, macos
- Domain
- desktop-dev, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100