UXP plugin validation failed: manifest version not supported
0 reputation · 17 Nov 2023, 07:03 UTC
0 reputation · 17 Nov 2023, 07:03 UTC
Goal: Verify that a minimal UXP panel can be loaded in Premiere Pro 2024 (version 24.x) using only developer‑mode flags, without any Adobe I/O credentials, to confirm local‑only functionality before pursuing a signed release.
Constraint: The panel fails with the console error "UXP plugin validation failed: manifest version not supported" when the manifest version declared in the plugin does not match the runtime’s supported range, and it is unclear which manifest version (v6, v7, or a future v8) guarantees compatibility across the 23.x‑24.x line while still allowing access to the limited Premiere Pro UXP API subset that does not require cloud credentials.
For Premiere Pro 24.x, the minimum accepted manifest version for unsigned UXP panels is v6. To resolve the validation error, update your manifest.json file to specify "manifestVersion": 6.
The "manifest version not supported" error occurs when the manifestVersion integer falls outside the range accepted by the UXP runtime embedded in the host application. While developer-mode flags bypass the requirement for a digital signature (allowing local-only functionality without Adobe I/O credentials), they do not relax the manifest version check. The runtime still requires a supported version to determine which API surface and security permissions to apply to the plugin.
Follow these steps to verify local-only functionality:
manifest.json:
{
"manifestVersion": 6,
"id": "your.plugin.id",
"version": "1.0.0",
...
}
Preferences > Plugins, or launch Premiere Pro with the -DeveloperMode flag.Diagnostic Note: If the error persists after updating to v6, please specify if you are using a Beta build of Premiere Pro, as Beta runtimes may shift the supported version range upward.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.