mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-26 00:25:56 +03:00
[GH-ISSUE #1179] Installing simulator certificates twice #1172
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#1172
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 @CyberMew on GitHub (Mar 18, 2022).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1179
In order for it to work, I seemed to have to install and trust, reboot, install and trust, reboot. Twice at least, always.
Charles proxy does not do this dance at all, and is able to achieve this without any restart. Is it possible to do something similar, if not fix it to only do it once?
@NghiaTranUIT commented on GitHub (Mar 19, 2022):
Sorry but I could not reproduce it. I'm using Xcode 13.2.1 and I'm able to install the certificate on iOS 15.2 simulator once.
Actually, you don't need to restart your simulator because Proxyman is using
simctlcommand line.simctlmode in (Preference -> Tools -> Usesimctlfor iOS Simulator (It's a default option)).simctlonly works for booted and opened iOS Simulators.If you encounter your issue, please help me test this out:
@CyberMew commented on GitHub (Mar 20, 2022):
I tested it on a newly launched simulator that I did not launch before.
Step 4 does not show the certificate. Repeating step 2 does nothing.
This is my experience:
I have not yet check the simctl mode but I don't think I touched it before. I will check in a bit and report back.
@CyberMew commented on GitHub (Mar 21, 2022):
Yes can confirm it is already using simctl mode. Not sure if it is a fluke, but after a restart of the laptop and installing it on 15.x it works. But after a few times it stop working properly again - video shows install-reboot-install working but previous i had to do install-reboot-install-reboot. Charles did not have this kind of issue at all I think. Also, previously when I did the install-reboot-install-reboot action, the installed cert would have today's date. But in my recent tries just now, it is using some old cert (the day I installed Proxyman on this laptop maybe), not sure why. Another point to investigate why such bugs happen could be that I never close Proxyman and I can install the certs to multiple devices over a period of time on the same instance, maybe repeated actions of some sort breaks it? Hope it helps.
https://user-images.githubusercontent.com/4715911/159200815-5ea90390-485b-4ac3-aa72-017f82df09fe.mov
@NghiaTranUIT commented on GitHub (Mar 21, 2022):
Thanks for your video. It's hard to reproduce because Proxyman just simply executes the following code:
It might depend on the Xcode version are you using too. It seems the bug was from Xcode or
simctltool.Can you verify which Xcode Command-Line you're using? (Find in Xcode Preference -> Location -> Command-Line Tool)
@CyberMew commented on GitHub (Mar 22, 2022):
It is using 13.2.1

I am also on macOS 11.6.x if that matters.. Perhaps it is indeed some bug, but still weird it doesn't perform reliably. Thought it was my issue until I tried it with Charles which didn't have the issue (or maybe it was on a bug free simulator), but anyway not a blocked issue for now, hope a solution is found in future.
I am more worried about the cert, because it is using an old one instead of one that is generated that day. In my previous experiences (before recording this video), it installed a new cert dated on the same day.
@NghiaTranUIT commented on GitHub (Mar 22, 2022):
Thanks for your insight. If you've still encountered this issue, please try help me to quit the iOS Simulator -> Open it again -> Check whether or not you can see the certificate.
I assume that the Setting app might properly not reload the certificate until we close the Setting app or re-open the Simulator.