Note: What I've done so far to try to reproduce this locally.

I'm recording what I've done so far. As commented below, there are at least 1-2 major differences between my test setup and the setup in the reported issue.

Possible difference 0: Device and Joplin locale is English (USA), tests were done on a Linux computer (Fedora 40).

  1. Started test Joplin Server instance.
    • Possible difference 1: I'm testing with Joplin Server. My main account is a Joplin Server account and will differ somewhat from a Joplin Cloud Teams user.
  2. Created a secondary account (can share with other users).
    • Email: self2@localhost.
    • Possible difference 2: Number of users shared with at a time?
    • Possible difference 3: Secondary account type?
  3. Attempted to share a notebook with self2@localhost containing 2054 notes and one subnotebook, though not many resources (and all smaller than a few megabytes).
    • Possible difference 4: Maximum resource size?
  4. Switched back to the secondary account and enabled encryption.
    • I was previously shown an error similar to "self2@localhost must enable encryption".
  5. Switched back to the primary account and completed the share.
  6. While waiting for sync, added 1-2 resources to a note.
  7. Verified that sync completed successfully.
  8. Created 5 more test accounts. (share-user-1@localhost, ...)
  9. Enabled encryption for each account.
  10. Switched back to the main account.
  11. Shared with share-user-1@localhost.
  12. Stopped Joplin Server.
  13. Tried to share with share-user-2@localhost (this failed)
  14. Started Joplin Server.
  15. Shared with share-user-2@localhost, share-user-3@localhost, share-user-4@localhost, and share-user-5@localhost.
  16. Changed a note in the subfolder of the shared folder.
  17. Synced.
  18. Switched to share-user-2@localhost's profile.
  19. Synced.
  20. Verified that there are no decryption errors.
  21. Attached a 244 MB attachment to a new note.
  22. Synced.
  23. Got an "Uploading items larger than 250 MB is currently disabled" error.
  24. Synced again.
  25. Deleted the attachment.
  26. Clicked cancel.
  27. Waited for "Cancelling..." to go away.

Next, I plan to try reducing the differences documented above. If I'm still unable to reproduce the issue, logs (which may contain a more detailed error message) may help.

1 Like