The loader manifest is not trusted.

Add-in Express™ Support Service
That's what is more important than anything else

The loader manifest is not trusted.
 
Kevin Du




Posts: 10
Joined: 2017-07-08
If the issue doesn't occur when you register a new empty add-in project, then you can compare your actual project with the new project.

I create a new empty project, and create a test certificate first, sign the addin and debug, it works normally.
After that I disable the signing, re-register the addin and Debug again, then the error comes, like my actual project, "Hash verification failed" comes.
And I have already checked that the manifest file is new generated without hashcode. Are there some places else where the hashcode is stored?

Besides,It seems that once I enable code signing, it will work all the time, no matter I enable it or not.
Posted 11 Jul, 2017 12:07:37 Top
Kevin Du




Posts: 10
Joined: 2017-07-08
Finally I get this problem solved.
I replace the loaders of my actual project with the loaders of the new-created project. Then Everything goes fine.
I don't know why, but it works.
Thank you, Andrei.
Posted 11 Jul, 2017 13:30:22 Top
Andrei Smolin


Add-in Express team


Posts: 14094
Joined: 2006-05-11
Hello Kevin,

If you change these settings, you should rebuild the add-in, not build. Also, check the Output window: the signing process produces informational messages.

Regards from Belarus (GMT+3),

Andrei Smolin
Add-in Express Team Leader
Posted 12 Jul, 2017 02:19:01 Top