starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-25 13:55:59 +03:00

[GH-ISSUE #1957] Completed Documents after signing not allowed to print or use previous versions to modify. #559

New issue

Closed

opened 2026-02-26 18:47:35 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 18:47:35 +03:00

Owner

Originally created by @Pravpraskumar on GitHub (Aug 11, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/1957

Issue Description

Once the Document signing is completed using documenso, it is observed that the printing is not working as expected and throwing an error while printing.

Steps to Reproduce

Complete a document in Documenso.
Download it to your local computer
Try printing the document either Adobe PDF editor / a normal printer
Observe the error is throwing when continued.

Expected Behavior

No response

Current Behavior

No response

Screenshots (optional)

No response

Operating System [e.g., Windows 10]

No response

Browser [e.g., Chrome, Firefox]

No response

Version [e.g., 2.0.1]

No response

Please check the boxes that apply to this issue report.

I have searched the existing issues to make sure this is not a duplicate.
I have provided steps to reproduce the issue.
I have included relevant environment information.
I have included any relevant screenshots.
I understand that this is a voluntary contribution and that there is no guarantee of resolution.
I want to work on creating a PR for this issue if approved

Originally created by @Pravpraskumar on GitHub (Aug 11, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/1957 ### Issue Description Once the Document signing is completed using documenso, it is observed that the printing is not working as expected and throwing an error while printing. ### Steps to Reproduce 1. Complete a document in Documenso. 2. Download it to your local computer 3. Try printing the document either Adobe PDF editor / a normal printer 4. Observe the error is throwing when continued. ### Expected Behavior _No response_ ### Current Behavior _No response_ ### Screenshots (optional) _No response_ ### Operating System [e.g., Windows 10] _No response_ ### Browser [e.g., Chrome, Firefox] _No response_ ### Version [e.g., 2.0.1] _No response_ ### Please check the boxes that apply to this issue report. - [x] I have searched the existing issues to make sure this is not a duplicate. - [x] I have provided steps to reproduce the issue. - [ ] I have included relevant environment information. - [ ] I have included any relevant screenshots. - [x] I understand that this is a voluntary contribution and that there is no guarantee of resolution. - [ ] I want to work on creating a PR for this issue if approved

kerem

2026-02-26 18:47:35 +03:00

closed this issue
added the
status: triage
label

kerem commented

2026-02-26 18:47:36 +03:00

Author

Owner

@Pravpraskumar commented on GitHub (Aug 12, 2025):

It is a Problem with the Adobe Reader and they have given the fix with the latest update.

@Pravpraskumar commented on GitHub (Aug 12, 2025): It is a Problem with the Adobe Reader and they have given the fix with the latest update.

kerem commented

2026-02-26 18:47:36 +03:00

Author

Owner

@SDMI-Developers commented on GitHub (Aug 27, 2025):

I am still running into this issue, where I cannot print, with latest version of documenso and adobe.

If I download the unsigned version, I can print fine. The signed version throws an error when printing.

This does not happen on files before I upgraded Documenso.

In Adobe Acrobat, I used the "Use print production" tool -> "Preflight" and ran the "Report PDF syntax issues" tool.

On the unsigned one I get "No problems found"

On the signed one I download I get:

In the mean time, I've run this code on the PDF file using pdf-lib to strip Anots.

const pdfDoc = await PDFDocument.load(pdfBytes, {
    ignoreEncryption: true,
  });

  // Surgically remove the /Annots array from every page
  // This directly deletes the source of the "Incorrect value type" error.
  const pages = pdfDoc.getPages();
  pages.forEach((page) => {
    page.node.delete(PDFName.of('Annots'));
  });
  return await pdfDoc.save();

@SDMI-Developers commented on GitHub (Aug 27, 2025): I am still running into this issue, where I cannot print, with latest version of documenso and adobe. If I download the unsigned version, I can print fine. The signed version throws an error when printing. This does not happen on files before I upgraded Documenso. In Adobe Acrobat, I used the "Use print production" tool -> "Preflight" and ran the "Report PDF syntax issues" tool. On the unsigned one I get "No problems found" <img width="275" height="85" alt="Image" src="https://github.com/user-attachments/assets/1d4ac919-8887-4e98-8a30-8bb6ed696f63" /> On the signed one I download I get: <img width="357" height="431" alt="Image" src="https://github.com/user-attachments/assets/4b8295c8-86d7-4052-b0c1-b9a6cfbe718c" /> In the mean time, I've run this code on the PDF file using pdf-lib to strip Anots. ``` const pdfDoc = await PDFDocument.load(pdfBytes, { ignoreEncryption: true, }); // Surgically remove the /Annots array from every page // This directly deletes the source of the "Incorrect value type" error. const pages = pdfDoc.getPages(); pages.forEach((page) => { page.node.delete(PDFName.of('Annots')); }); return await pdfDoc.save(); ```

kerem referenced this issue

2026-02-26 19:31:36 +03:00

[PR #559] [MERGED] fix: UI fixes and improvements #1045

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/documenso#559

No description provided.

Rows
Columns