When adding a custom cert that doesn't meet Apple's standards, outline violations...

Open
#2,559 4 comments 0 reactions 1 assignee View on GitHub

@NghiaTranUIT is already working on this.

Since Dec 18, 2025.

Assessment

This issue has not been assessed yet.

Description

✅ Done enhancement

Description

When adding a custom root cert, I get a "Missing Extend Service" warning. (Is that supposed to be "Missing Extended Service"?) However, it doesn't actually say why, or what part of the ATS standard the cert violates.

Why this feature/change is important?

Without a clear failure state, we can attempt to use a cert that will fail ATS in particular circumstances. For instance, we had a cert that failed when attempting to pin in the iOS app's Info.plist, but worked fine for unpinned requests. Once we updated it to have a limited expiration time, all requests worked, even pinned. But we still have the service warning, but there's no way to tell what the issue actually is.

Dominant language
No language data
Stars
7k
Forks
237
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ProxymanApp/Proxyman

All issues in ProxymanApp/Proxyman

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.