You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
validation_state is lost with the verify call #149
And when I run it through the Python SDK too, the file is also reported as valid. And that validation is properly reported and present in the manifests, both when extracted using c2patool and the Python SDK.
The Verify site does not use the Python SDK. So I think the bug here is somewhere else.
Hi @ttbuffey, thank you for opening this issue. This is actually a UI bug on the Verify site that I'm in the process of fixing as we speak. The image will show as "untrusted," rather than the "invalid" state it has now.
Activity
tmathern commentedon Aug 28, 2025
The file you link is a valid file. You can also check it out at https://contentauthenticity.adobe.com/inspect, or using c2patool.
From https://contentauthenticity.adobe.com/inspect:

This is what c2patool reports (please use latest version from here):
And when I run it through the Python SDK too, the file is also reported as valid. And that validation is properly reported and present in the manifests, both when extracted using c2patool and the Python SDK.
The Verify site does not use the Python SDK. So I think the bug here is somewhere else.
ps. Note the informational validation status:
This may be causing the difference in behavior between the tools.
emensch commentedon Aug 28, 2025
Hi @ttbuffey, thank you for opening this issue. This is actually a UI bug on the Verify site that I'm in the process of fixing as we speak. The image will show as "untrusted," rather than the "invalid" state it has now.
emensch commentedon Aug 28, 2025
This is fixed now. Verify shows the image as "untrusted," as it should: https://contentcredentials.org/verify?source=https://spec.c2pa.org/public-testfiles/image/jpeg/adobe-20220124-CAI.jpg
ttbuffey commentedon Aug 29, 2025
@tmathern Thanks for the quick fix. This helps a lot. Thanks
ttbuffey commentedon Aug 29, 2025
@emensch Thanks for the quick fix on the UI.