Ios Signing Troubleshooting

Community

milisp

ios-signing-troubleshooting

Diagnose iOS code signing, provisioning profile, entitlement and certificate errors from Xcode or xcodebuild. Use when a build, archive or export fails with signing errors, "No profiles found", "Provisioning profile doesn't include", or keychain problems.

Overview

Publisher	milisp
Repository	`mcp-linker`
Skill name	`ios-signing-troubleshooting`
Stars	345
Forks	42
Bundled files	Instructions only
License	AGPL-3.0
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by milisp on GitHub. Read the source before you install it.

Installation

Install the Ios Signing Troubleshooting AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/milisp/mcp-linker/tree/main/plugins/ios/skills/ios-signing-troubleshooting
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/milisp/mcp-linker/tree/main/plugins/ios/skills/ios-signing-troubleshooting

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/milisp/mcp-linker.git /tmp/mcp-linker
mkdir -p .claude/skills
cp -r /tmp/mcp-linker/plugins/ios/skills/ios-signing-troubleshooting .claude/skills/ios-signing-troubleshooting

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ios Signing Troubleshooting in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ios Signing Troubleshooting on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ios Signing Troubleshooting is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

iOS signing troubleshooting

Work from evidence: capture the exact error text, then match it to a cause below.

Inspect the current state

Identities: security find-identity -v -p codesigning
Installed profiles: ls ~/Library/Developer/Xcode/UserData/Provisioning\ Profiles/ (older Xcode: ~/Library/MobileDevice/Provisioning Profiles/)
Decode a profile: security cms -D -i file.mobileprovision (check TeamIdentifier, application-identifier, ExpirationDate, ProvisionedDevices, entitlements)
Signature of a built app: codesign -dvv --entitlements - App.app
Project settings: xcodebuild -showBuildSettings -scheme App | grep -E "CODE_SIGN|PROVISIONING|DEVELOPMENT_TEAM|PRODUCT_BUNDLE_IDENTIFIER"

Common errors

Symptom	Likely cause and fix
"No profiles for 'com.x.y' were found"	Bundle ID not registered, or automatic signing is off. Enable automatic signing with the right team, or create the bundle ID and profile.
"Provisioning profile doesn't include signing certificate"	Profile was made with a different certificate. Regenerate it, or install the matching certificate with its private key.
"doesn't include the currently selected device"	Development profile lacks the device UDID. Register the device and regenerate.
"Entitlements not permitted" / capability mismatch	A capability in the entitlements file is not enabled on the App ID. Enable it, then regenerate the profile.
"No signing certificate found"	Missing identity or private key in the keychain. Import the `.p12` or create a new certificate.
`errSecInternalComponent` in CI	Keychain is locked. Run `security unlock-keychain`, then `security set-key-partition-list -S apple-tool:,apple: -s -k <pw> <keychain>`.
Expired certificate or profile	Check dates; renew and regenerate.

Fix with asc (optional)

asc bundle-ids, asc certificates, asc profiles and asc devices manage signing assets through the App Store Connect API (see --help; the asc skill pack has a signing-setup recipe).

Rules

Prefer Xcode automatic signing for development; use manual signing only for CI or when required.
Never print or commit private keys, .p12 files or passwords. Confirm before revoking certificates, which breaks other machines.

Frequently asked questions

What does the Ios Signing Troubleshooting AI skill do?

Why use Ios Signing Troubleshooting on TypingMind?

Because you install it once and use it with any model. Ios Signing Troubleshooting is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ios Signing Troubleshooting in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/milisp/mcp-linker/tree/main/plugins/ios/skills/ios-signing-troubleshooting. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Ios Signing Troubleshooting?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ios Signing Troubleshooting?

As many as you like. As long as a model supports skills, you can use Ios Signing Troubleshooting with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ios Signing Troubleshooting AI skill free?

Yes. It is published on GitHub by milisp under the AGPL-3.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Openclaw Test Performance

openclaw

OrganizationPopular

Benchmark, diagnose, and optimize OpenClaw test and plugin-suite runtime, import hotspots, CPU/RSS, heap growth, and slow coverage paths.

Openclaw Testing

Choose proportional OpenClaw tests and checks, diagnose failures, and route environment-sensitive or release proof to its owner.

Release Openclaw Ci

Run, watch, debug, and summarize OpenClaw full release CI, release checks, live provider gates, install/update proofs, and release-secret preflights.

Release Openclaw Mac

Run or recover OpenClaw macOS release signing, notarization, appcast, and asset promotion.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

iOS signing troubleshooting

Inspect the current state

Common errors

Fix with asc (optional)

Rules

Frequently asked questions

Related AI Skills

Set up your own AI workspace now