This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(64, 83%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDW%3C/text%3E%3C/svg%3E)
We're running into an issue with the MIP File SDK where certain PDF files that are not signed are failing to apply labels with CommitAsync. The specific error is "file_commit_async Failed with: [NotSupportedError: 'The file is protected by signature, CorrelationId=6679cd55-6695-43ea-b27b-d3a6e3ed34e3, CorrelationId.Description=FileHandler'".
We noticed this after updating from 1.13.161 to 1.14.108. I've attached a sample file here that can be used to reproduce the issue.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(201.6, 18%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGG%3C/text%3E%3C/svg%3E)
Hi @Dan Walsh
Thanks for the question and using MS Q&A platform.
The error message you are encountering, "file_commit_async Failed with: [NotSupportedError: 'The file is protected by signature...'", suggests that the PDF file you are trying to label is digitally signed. According to the context, the MIP SDK does not support labeling signed PDF files, which could be the reason for the failure after your update to version 1.14.108.
Please check the below image for reference:
To resolve this issue, you may want to check if the PDF files are indeed signed or if there are any other protections applied to them. If they are not signed, you might need to ensure that the MIP SDK is correctly configured and that you are using the appropriate methods for labeling.
Reference: New support for PDF encryption with Microsoft Information Protection
Hope this helps. Do let us know if you have any further queries.
Hi Ganesh,
Thanks for your reply. The files we're seeing this issue with are not signed, if you open the attached pdf from my initial message in a PDF reader application it will not show any signatures.
I did notice that entry in the release notes for 1.14.108, I assume that is the reason for the changes in how the library is detecting signed files but I don't see any way that this behavior can be configured so that we can continue to work with the files that were able to be labelled in 1.13.161.
@Dan Walsh - Apologies for the inconvenience caused. The PDF you shared appears to be empty, and I couldn't find any content in it. Could you please resend it?
@Ganesh Gurram The PDF contains no content but the MIP File SDK will detect it as being a signed PDF and fail to apply labels.