[GH-ISSUE #603] Document Sharing Link Redirects to Homepage #163

Open
opened 2026-02-26 18:45:40 +03:00 by kerem · 7 comments
Owner

Originally created by @daallgeier on GitHub (Oct 28, 2023).
Original GitHub issue: https://github.com/documenso/documenso/issues/603

Originally assigned to: @daallgeier, @luckyklyist on GitHub.

Issue Description

Opening a sharing link to a document throws a console error and redirects to documenso.com (example my pledge: https://app.documenso.com/share/sdwlb8c7t1pkvu)

8593596e-8fa50b0cbb75b2d0.js:9 Uncaught Error: Minified React error #419; visit https://reactjs.org/docs/error-decoder.html?invariant=419 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at 8593596e-8fa50b0cbb75b2d0.js:9:63944
    at Qh (8593596e-8fa50b0cbb75b2d0.js:9:64832)
    at rx (8593596e-8fa50b0cbb75b2d0.js:9:120339)
    at Lk (8593596e-8fa50b0cbb75b2d0.js:9:94328)
    at 8593596e-8fa50b0cbb75b2d0.js:9:94150
    at bf (8593596e-8fa50b0cbb75b2d0.js:9:94157)
    at mf (8593596e-8fa50b0cbb75b2d0.js:9:90680)
    at MessagePort.P (499-e5ab349bd0ad5c7b.js:25:1665)
(anonymous) @ 8593596e-8fa50b0cbb75b2d0.js:9
Qh @ 8593596e-8fa50b0cbb75b2d0.js:9
rx @ 8593596e-8fa50b0cbb75b2d0.js:9
Lk @ 8593596e-8fa50b0cbb75b2d0.js:9
(anonymous) @ 8593596e-8fa50b0cbb75b2d0.js:9
bf @ 8593596e-8fa50b0cbb75b2d0.js:9
mf @ 8593596e-8fa50b0cbb75b2d0.js:9
P @ 499-e5ab349bd0ad5c7b.js:25

Steps to Reproduce

  1. go to /documents
  2. Click the "share" button (wait for wayyy too long for it to be copied into clipboard)
  3. Paste into new (incognito) tab
  4. Get redirected to documenso.com

Expected Behavior

I expected to see my signed supporter pledge

Current Behavior

I am seeing the homepage

Screenshots (optional)

Environment

  • OS: macOS Sonoma
  • Browser: Chrome
  • Version: 118

Checklist

  • 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.
Originally created by @daallgeier on GitHub (Oct 28, 2023). Original GitHub issue: https://github.com/documenso/documenso/issues/603 Originally assigned to: @daallgeier, @luckyklyist on GitHub. <!--- Please provide a general summary of the issue in the Title above --> ## Issue Description Opening a sharing link to a document throws a console error and redirects to documenso.com (example my pledge: https://app.documenso.com/share/sdwlb8c7t1pkvu) ``` 8593596e-8fa50b0cbb75b2d0.js:9 Uncaught Error: Minified React error #419; visit https://reactjs.org/docs/error-decoder.html?invariant=419 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at 8593596e-8fa50b0cbb75b2d0.js:9:63944 at Qh (8593596e-8fa50b0cbb75b2d0.js:9:64832) at rx (8593596e-8fa50b0cbb75b2d0.js:9:120339) at Lk (8593596e-8fa50b0cbb75b2d0.js:9:94328) at 8593596e-8fa50b0cbb75b2d0.js:9:94150 at bf (8593596e-8fa50b0cbb75b2d0.js:9:94157) at mf (8593596e-8fa50b0cbb75b2d0.js:9:90680) at MessagePort.P (499-e5ab349bd0ad5c7b.js:25:1665) (anonymous) @ 8593596e-8fa50b0cbb75b2d0.js:9 Qh @ 8593596e-8fa50b0cbb75b2d0.js:9 rx @ 8593596e-8fa50b0cbb75b2d0.js:9 Lk @ 8593596e-8fa50b0cbb75b2d0.js:9 (anonymous) @ 8593596e-8fa50b0cbb75b2d0.js:9 bf @ 8593596e-8fa50b0cbb75b2d0.js:9 mf @ 8593596e-8fa50b0cbb75b2d0.js:9 P @ 499-e5ab349bd0ad5c7b.js:25 ``` <!--- Please provide a clear and concise description of the problem. --> ## Steps to Reproduce <!--- Please provide step-by-step instructions to reproduce the issue. --> <!--- Include code snippets, error messages, and any other relevant information. --> 1. go to /documents 2. Click the "share" button (wait for wayyy too long for it to be copied into clipboard) 3. Paste into new (incognito) tab 4. Get redirected to documenso.com ## Expected Behavior <!--- Describe what you expected to happen. --> I expected to see my signed supporter pledge ## Current Behavior <!--- Describe what is currently happening. --> I am seeing the homepage ## Screenshots (optional) <!--- If applicable, add screenshots to help explain the issue. --> ## Environment <!--- Please provide information about your environment, such as operating system, browser, version, etc. --> - OS: macOS Sonoma - Browser: Chrome - Version: 118 ## Checklist <!--- Please check the boxes that apply to this issue report. --> <!--- You can add or remove items as needed. --> - [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.
Author
Owner

@mittalsam98 commented on GitHub (Oct 29, 2023):

I would like to pick this up

<!-- gh-comment-id:1783987649 --> @mittalsam98 commented on GitHub (Oct 29, 2023): I would like to pick this up
Author
Owner

@Mythie commented on GitHub (Oct 30, 2023):

G'day, this one while not a bug does pose the question about phrasing.

Sharing is intended to be used for some minor virality, the intention is that people that have enjoyed the signing experience can share that by receiving a link that'll show that they've signed with Documenso with their signature or name displayed.

image

Problem is in the document dashboard this isn't inherently obvious:

image

One might assume that sharing could be used to invite a recipient to sign a document which isn't the case, to improve upon this we should use the same sharing dialog that we have elsewhere in the app:

image

One way to do this would be to allow the document share button to take in an optional children prop which will override the dialog trigger if provided.

<!-- gh-comment-id:1784463523 --> @Mythie commented on GitHub (Oct 30, 2023): G'day, this one while not a bug does pose the question about phrasing. Sharing is intended to be used for some minor virality, the intention is that people that have enjoyed the signing experience can share that by receiving a link that'll show that they've signed with Documenso with their signature or name displayed. <img width="599" alt="image" src="https://github.com/documenso/documenso/assets/13398220/f5a04bee-11cf-434f-bebd-c263a336ea58"> Problem is in the document dashboard this isn't inherently obvious: <img width="1219" alt="image" src="https://github.com/documenso/documenso/assets/13398220/32c0fe90-5070-4c7c-ac4e-1885f4025b04"> One might assume that sharing could be used to invite a recipient to sign a document which isn't the case, to improve upon this we should use the same sharing dialog that we have elsewhere in the app: <img width="648" alt="image" src="https://github.com/documenso/documenso/assets/13398220/cb8b66bf-1d13-4786-a1b5-cdcdf7b09311"> One way to do this would be to allow the document share button to take in an optional children prop which will override the dialog trigger if provided.
Author
Owner

@Mythie commented on GitHub (Oct 30, 2023):

@mittalsam98 If you're confident you can make these changes I'm happy to assign it to you 🙌

<!-- gh-comment-id:1784463832 --> @Mythie commented on GitHub (Oct 30, 2023): @mittalsam98 If you're confident you can make these changes I'm happy to assign it to you 🙌
Author
Owner

@daallgeier commented on GitHub (Oct 30, 2023):

the "it" in the suggested tweet seems to refer to the document tho. Could that be rewritten too?

I just signed a document with @documenso.  Check them out!

[url]

Oh and it could be referral link to maybe get one more free document this month.

<!-- gh-comment-id:1785148127 --> @daallgeier commented on GitHub (Oct 30, 2023): the "it" in the suggested tweet seems to refer to the document tho. Could that be rewritten too? ``` I just signed a document with @documenso. Check them out! [url] ``` Oh and it could be referral link to maybe get one more free document this month.
Author
Owner

@luckyklyist commented on GitHub (Oct 30, 2023):

@mittalsam98 If you're confident you can make these changes I'm happy to assign it to you 🙌

I will liked to look into this issue .

<!-- gh-comment-id:1785209634 --> @luckyklyist commented on GitHub (Oct 30, 2023): > @mittalsam98 If you're confident you can make these changes I'm happy to assign it to you 🙌 I will liked to look into this issue .
Author
Owner

@Mythie commented on GitHub (Oct 31, 2023):

@mittalsam98 giving this to @luckyklyist apologies!

<!-- gh-comment-id:1786397254 --> @Mythie commented on GitHub (Oct 31, 2023): @mittalsam98 giving this to @luckyklyist apologies!
Author
Owner

@github-actions[bot] commented on GitHub (Dec 8, 2023):

This issue has not seen activity for a while. It will be closed in 30 days unless further activity is detected

<!-- gh-comment-id:1846728959 --> @github-actions[bot] commented on GitHub (Dec 8, 2023): This issue has not seen activity for a while. It will be closed in 30 days unless further activity is detected
Sign in to join this conversation.
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#163
No description provided.