Troubleshooting
Patch Extend is in Beta
Patch Extend is currently in beta and available for testing. We're actively refining the feature and building out comprehensive documentation. We recommend evaluating it in a test environment before deploying to production, and we welcome your feedback as we continue to improve!
| Symptom | What to check |
|---|---|
| App id not found / not resolved | Computer-level profile for com.alectrona.patch? PatchExtendFeeds present in managed prefs? Feed URI reachable? |
| Profile installed but Patch ignores Extend feeds | Double-clicked .mobileconfig installs a user profile—deploy as MDM/Jamf computer policy instead (sudo patch / Patch Agent do not use that user profile the same way) |
| Failed to decode PrivateCatalogFeeds | The PatchExtendFeeds preference failed to decode (not the feed JSON file)—see Invalid feed configuration below |
| Feed file errors | Absolute path matches profile URI; file readable by root (644 or similar); JSON is valid |
| App ignored / refused from feed | Append-only collisions with builtin catalog: same id, bundle identifier, or effective install path (installDirectory + fileName) |
| Builtin title used instead of your feed | Same id as a catalog app → builtin always wins |
| Feed HTTPS 401/403 | Feed-level Authentication (bearer/header) token and header name |
| Package download 403 / fails | Package url (expired Azure SAS?), or network |
| Wrong installer behavior | installMethod matches the media (appInDmg, pkg, appInZip, …) |
| Install runs but version cannot be verified / always looks out of date | Provide either checks.versionComparisonKey or checks.commandToGetLocalVersion (the schema requires one of them) |
Invalid feed configuration​
If the profile’s PatchExtendFeeds array cannot be decoded, Patch logs an error and loads no Extend feeds. Example:
ERROR: Failed to decode PrivateCatalogFeeds: The data couldn’t be read because it is missing.
That message refers to the managed preference / profile payload (feed configuration), not validation of the feed JSON document at URI.
Common causes:
- Missing or mistyped required keys such as
TypeorURI - Wrong value types (for example a string where a boolean is required)
- Missing
RequireSignature(must be present; usefalsefor unsigned feeds)
Fix the profile (see Configuring Patch Extend or the quick-start .mobileconfig), redeploy, and retry.
Confirm the profile​
- System Settings → General → Device Management (or Profiles): your Patch Extend profile is listed as a computer / device profile, not only under the logged-in user.
- Jamf: computer inventory shows the profile; scope is the test Mac; level is computer (not user).
- If you only double-clicked the
.mobileconfig, redeploy via MDM—see Getting Started.
Confirm the feed JSON​
Validate the file at your feed URI against the published schema (several CLI options): Feed schema.