Skip to main content
APenNameAndThatA
APenNameAndThatA
Participating Frequently
May 5, 2023
Question

Report code 2007, of the Appearance Integrity Report, from electronic signature.

  • May 5, 2023
  • 1 reply
  • 7784 views

Hi

When I try to sign documents by visibly certifying them, I get a warning box called "Appearnace Integrity Report" and it says that the "Report code" is "2007" and the "Description" is "Page content may silently change." I wrote a word document from a template, sent it to the person who proof reads what I write, got it back, changed it a bit, and converted it to a PDF. The document was never a form, and no, I don't want to send it to Adobe so they can see what went wrong. What to do? Thanks. 

    This topic has been closed for replies.

    1 reply

    Amal.
    Community Manager
    Amal.Community Manager
    Community Manager
    May 5, 2023

    Hi @APenNameAndThatA 

     

    Hope you are doing well and Thanks for reaching out.

     

    Please go through the correct answer marked in the similar discussion https://answers.acrobatusers.com/APPEARANCE-INTEGRITY-REPORT-q204358.aspx and see if that helps.

     

    Regards

    Amal

    K
    kmpeterson
    Known Participant
    October 5, 2023

    I am also having this issue.  

    As with the original poster, this is not a form.  My initial discovery for this is also not something I can share, but I recreated it in a form that I can.

    It appears to occur with (some number of) images inserted in a file that is then exported to PDF.  In my case, this is macOS 14.0, and Acrobat 2023.006.20320.  The document I'm including was composed with Microsoft Word, but Apple Pages also causes this issue.  Also, the problem occurs with a file that is generated using the application's built-in "Save as PDF" functionality and also when the document is exported using the macOS Print dialog and then the save as PDF function in that utility.  Also exported the document as PostScript, ran it through the Acrobat Distiller - same issue.

     

    It seems really hard to believe that this warning is correct.  Especially passing explicitly through a PostScript phase, I seriously doubt that it's the case that there is anything "dynamic" is this document simply related to the insertion of a PNG image.

     

    K
    kmpeterson
    Known Participant
    October 24, 2023

    If you look at the details of the Appearance Integrity Report, you'll read "The document author has enabled image interpolation. No image interpolation is allowed."

     

    According to the PDF spec, image interpolation is an attempt to produce a smooth transition between adjacent sample values when rendering an image whose resolution is significantly lower than that of the output device. Setting the value of the Interpolate entry in an image dictionary to true, is a way for a PDF to declare to a PDF processor that a specific image might render better if interpolation is used for this particular image. However, this is only a hint, and a PDF processor may ignore it.

     

    Thus, different PDF viewers may or may not apply interpolation, resulting in different renderings. Furthermore, there are different interpolation algorithms and parametrizations thereof but the PDF specification does not prescribe an algorithm and parametrization to use. So even PDF viewers that do interpolate don't necessarily display the image identically.

     

    I would propose trying to configure the document creation not to use interpolation or replacing the image by vector graphics.


    Thanks for the note.  

    I think this is a bug, because if it's not possible to seal a document - which is to say, rewrite it in an immutable format - in the post-processing (rendering) stage, the application has a defect.  If one is attempting to certify a document (by hashing the content and then signing the result) it's reasonable to expect that an end user has decided that any interactivity should be eliminated in favor of a valid signature.  If not, the ability to specify an option to process the file this way as part of the signature process is the only alternative to simply indicating that a signature can't be trusted.

    To give credit where credit is due, though, because the artwork was created in Illustrator I am able to export the illustration as SVG - and the resulting PDF does not throw this warning and is thus valid.  This makes sense, and I appreciate your suggestion. 

    However, it makes sense to me because I understand the nature of the process.  I doubt it would make sense to the vast majority of end-users trying to understand why MS-Office creates documents that aren't "fixed".

    It would be really great to have someone from Adobe weigh in on this.  

    Thanks again!

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices