starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-24 21:36:01 +03:00

[GH-ISSUE #2531] Mobile Signing Crashes on iOS When Documents Contain Too Many Pages #704

New issue

Open

opened 2026-02-26 18:48:07 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 18:48:07 +03:00

Owner

Originally created by @NDCallahan on GitHub (Feb 23, 2026).
Original GitHub issue: https://github.com/documenso/documenso/issues/2531

Issue Description

Signing links consistently crash on iOS devices when opening large documents that contain signature fields duplicated across many pages. The signing page loads, refreshes twice, and then the browser crashes. This issue does not occur on desktop browsers and does not produce any console errors.

The problem appears tied to:

High page count (e.g., 71 pages) Pages 1-69 have no issues. Anthing 70 and above does
Signature fields duplicated across all pages
Possibly the total number of interactive fields rendered on mobile

If a document contains only a single signature field on one page, the issue does not occur. If a new document is created with only initials and signatures (no duplication across pages), the issue does not occur. The behavior is reproducible in both self‑hosted and cloud versions.

This is currently blocking applicants from completing required housing documents.

Steps to Reproduce

Create a multi‑page document (e.g., ~70 pages).
Add a signature field to one page.
Duplicate that signature field across all pages.
Publish the document and open the signing link on an iOS device.
Observe the page load, refresh twice, and then crash.

Expected Behavior

The signing interface should load normally on iOS.
All signature fields should render without causing refresh loops or browser crashes.
Users should be able to complete the signing process on mobile devices.

Current Behavior

On iOS devices, the signing page loads, refreshes twice, and then crashes.
No console errors are produced.
Desktop browsers do not exhibit the issue.
Reducing the number of duplicated signature fields or limiting them to a single page prevents the crash.

Screenshots (optional)

No response

Operating System [e.g., Windows 10]

Applie IOS

Browser [e.g., Chrome, Firefox]

Chrome & Safari

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 @NDCallahan on GitHub (Feb 23, 2026). Original GitHub issue: https://github.com/documenso/documenso/issues/2531 ### Issue Description Signing links consistently crash on **iOS devices** when opening large documents that contain signature fields duplicated across many pages. The signing page loads, refreshes twice, and then the browser crashes. This issue does **not** occur on desktop browsers and does not produce any console errors. The problem appears tied to: - High page count (e.g., 71 pages) Pages 1-69 have no issues. Anthing 70 and above does - Signature fields duplicated across all pages - Possibly the total number of interactive fields rendered on mobile If a document contains only a single signature field on one page, the issue does not occur. If a new document is created with only initials and signatures (no duplication across pages), the issue does not occur. The behavior is reproducible in both self‑hosted and cloud versions. This is currently blocking applicants from completing required housing documents. --- ### Steps to Reproduce 1. Create a multi‑page document (e.g., ~70 pages). 2. Add a signature field to one page. 3. Duplicate that signature field across all pages. 4. Publish the document and open the signing link on an **iOS device**. 5. Observe the page load, refresh twice, and then crash. ### Expected Behavior - The signing interface should load normally on iOS. - All signature fields should render without causing refresh loops or browser crashes. - Users should be able to complete the signing process on mobile devices. --- ### Current Behavior - On iOS devices, the signing page loads, refreshes twice, and then crashes. - No console errors are produced. - Desktop browsers do not exhibit the issue. - Reducing the number of duplicated signature fields or limiting them to a single page prevents the crash. ### Screenshots (optional) _No response_ ### Operating System [e.g., Windows 10] Applie IOS ### Browser [e.g., Chrome, Firefox] Chrome & Safari _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. - [x] I have included relevant environment information. - [x] 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 added the

status: triage

label

2026-02-26 18:48:07 +03:00

kerem commented

2026-02-26 18:48:08 +03:00

Author

Owner

@ElTimuro commented on GitHub (Feb 24, 2026):

Adding this to internal review since it does not look trivial

@ElTimuro commented on GitHub (Feb 24, 2026): Adding this to internal review since it does not look trivial

kerem commented

2026-02-26 18:48:08 +03:00

Author

Owner

@NDCallahan commented on GitHub (Feb 24, 2026):

Thanks. We can work around it but it's extremely inconvenient. Lol. Something the document into two signs instead of a single one seems to work

@NDCallahan commented on GitHub (Feb 24, 2026): Thanks. We can work around it but it's extremely inconvenient. Lol. Something the document into two signs instead of a single one seems to work

kerem referenced this issue

2026-02-26 19:32:00 +03:00

[PR #723] [CLOSED] feat : Document Thumbnails #1139

kerem referenced this issue

2026-02-26 19:32:00 +03:00

[PR #722] [CLOSED] feat: document thumbnails #1140

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#704

No description provided.

Rows
Columns