-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can`t verify generated images #64
Comments
@StarodubtsevDV We’ve identified an issue where verification is failing with some of our recent images in Wasm/WebCrypto and we are currently looking into it. We are hoping to have a fix deployed to our JS-SDK and Verify site later this week. |
@StarodubtsevDV sorry for the delay here - we just deployed an update to Verify that should resolve this. Can you please check on your end and confirm it is as you expect? |
We have checked ours generated images (that was in issue), they were verified properly. Thank you so much! We didn't recompile library to test it's generated images yet. We will notify you when it will be done. |
@StarodubtsevDV Glad to hear it works! I will close this issue for now - please open another issue if you come across anything else that looks like it is not working properly and we will investigate - thanks! |
Hello!
I tried to verify test image (attached to issue) generated by your`s library on this verification site. But it failed in case of unavailable image content credentials (screenshot attached bellow).
But image verified by c2pa-tool (v 0.2.0, from this project) successfully.
Could you say what side is getting wrong: verification site or this project?
The text was updated successfully, but these errors were encountered: